From: David Jander <david.jander@protonic.nl>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Stable Linux kernel 2.6 for MPC8XX
Date: Fri, 10 Mar 2006 08:22:42 +0100 [thread overview]
Message-ID: <200603100822.42764.david.jander@protonic.nl> (raw)
In-Reply-To: <1CFEB358338412458B21FAA0D78FE86D02CABEE3@rennsmail02.eu.thmulti.com>
On Wednesday 08 March 2006 15:29, Fillod Stephane wrote:
> >I would want to use a linux kernel 2.6 on a custom MPC8xx board.
> >Which stable kernel release must or can I use ?
>
> http://www.denx.de/wiki/bin/view/Know/Linux24vs26
I believe most of those observations and measurements are not valid anymore.
Kernel 2.6 for 8xx has come a long way since this article was written. It
might have been true back then, but it surely isn't anymore.
Kernel 2.6 is bigger than 2.4, that's a fact, but application performance is
actually slightly higher with 2.6.14 than it is with 2.4.25.
The overall robustness and "niceness" of the code is also a totally different
story now. 2.6 software architecture is definitely better, and many drivers
are much more stable. Implementing board support and drivers in 2.6 is also
much easier and cleaner than in 2.4.
Greetings,
--
David Jander
Protonic Holland.
next prev parent reply other threads:[~2006-03-10 7:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 14:29 Stable Linux kernel 2.6 for MPC8XX Fillod Stephane
2006-03-10 7:22 ` David Jander [this message]
2006-03-10 13:16 ` Dan Malek
2006-03-10 15:33 ` Wolfgang Denk
2006-03-14 7:50 ` David Jander
2006-03-14 11:56 ` Carlos Mitidieri
2006-03-14 14:01 ` Dan Malek
2006-03-14 14:58 ` David Jander
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 8:34 Wolfgang Grandegger
2006-03-14 14:46 ` David Jander
2006-02-28 8:50 Minor bug in file irq.h Laurent Lagrange
2006-03-08 14:32 ` Stable Linux kernel 2.6 for MPC8XX Laurent Lagrange
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=200603100822.42764.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).