From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Dropping versatile kernel
Date: Mon, 13 Aug 2012 22:19:19 +0200 [thread overview]
Message-ID: <1344889159.19132.25.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <8a1edb29d124bdc47b8f4d6c704d4ba6@mail01.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
Okay done.
Commit:
http://git.ipfire.org/?p=ipfire-3.x.git;a=commit;h=5425c9c9792c144a3f8a38df170303d0a0d41ee0
Package:
https://pakfire.ipfire.org/build/dc29bced-812f-4b96-a711-8a356407f035
Michael
On Mon, 2012-08-13 at 08:50 +0000, Arne Fitzenreiter wrote:
> On Sun, 12 Aug 2012 20:40:37 +0200, Michael Tremer
> <michael.tremer(a)ipfire.org> wrote:
> > Hi Arne,
> >
> > you just dropped the Linux kernel which was compiled for ARM Versatile
> > from IPFire 2.x:
> >
> > http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=c94c1fa5574230d9edbefdfe6aea14874593ec31
> >
> > The reasons are that there is no use for it except virtual environments
> > with QEMU. However, these are very slow and pretty much unusable.
> >
> > Do you think there are any other reasons to keep the versatile kernel in
> > IPFire 3? I guess we could drop it, too.
> >
> > A benefit would be a massive increase in build time of the kernels for
> > ARMv5tel which is more than 8 hours on Pandaboard.
>
> I think we can drop this also for IPFire 3
> If someone really need this we can easily readd it later.
>
> Arne
>
prev parent reply other threads:[~2012-08-13 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 18:40 Michael Tremer
2012-08-13 8:50 ` Arne Fitzenreiter
2012-08-13 20:19 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1344889159.19132.25.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox