linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Song Sam <samlinuxppc@yahoo.com.cn>,
	"Robert P. J. Day" <rpjday@mindspring.com>,
	Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 2.4 versus 2.6 patches
Date: Mon, 26 Jul 2004 09:30:54 -0700	[thread overview]
Message-ID: <20040726163054.GA8872@gate.ebshome.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0407261021120.6190@localhost.localdomain>


On Mon, Jul 26, 2004 at 10:27:52AM -0400, David Woodhouse wrote:
> Because nobody's really that interested in it. For what it's worth, I've
> abandoned all pretence of continuing to support 2.4 in the MTD/JFFS2 CVS
> tree.

This is quite sad, but not all maintainers do the same. IIRC networking fixes
are still backported to 2.4.

Hopefully, I can maintain this stuff myself and backport fixes (what I already
did for some MTD stuff, btw).

> > > I would not consider deploying anything on 2.6
> > > today. IMHO it's not mature
> > > enough to be used in production environment.
> >
> > I do agree with the view.I guess it is most embedded
> > developers's opinion.
>
> Out of interest, how many platforms are you using 2.6 on and how does
> your experience with these platforms support your stated view?

How the number of platforms is relevant for this discussion? It should work on
one I use, it's quite academic for me if it works fine on another. Could you
point me to _any_ distribution which is shipping_2.6 PPC 4xx based kernel with
working preemption? Last time I tried this on Ebony it wasn't quite stable.

A little history, IMO we get something we can call "production quality" 2.4
PPC 4xx only in the end of 2003. It took me almost 1.5 years to get 2.4 stable
on platforms I use (fixing some nasty bugs on the way, even MTD ones :P). After
that I'm quite reluctant to switch to 2.6 right now, just because some
maintainers lost interest in 2.4.

--
Eugene

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-07-26 16:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 14:57 2.4 versus 2.6 patches Robert P. J. Day
2004-07-24 15:20 ` David Woodhouse
2004-07-26  2:50   ` Song Sam
2004-07-26  4:13     ` David Woodhouse
2004-07-26  4:40       ` Eugene Surovegin
2004-07-26 13:48         ` Song Sam
2004-07-26 14:27           ` David Woodhouse
2004-07-26 15:08             ` Mark Chambers
2004-07-26 15:53               ` Robert P. J. Day
2004-07-26 16:30             ` Eugene Surovegin [this message]
2004-07-26 23:17               ` Thomas Gleixner
2004-07-26 23:49                 ` Eugene Surovegin
2004-07-27  0:25                   ` Thomas Gleixner
2004-07-29 19:30                     ` David Woodhouse
2004-07-26 17:16             ` Wolfgang Denk
2004-08-09 15:03               ` Marcelo Tosatti
2004-07-27  3:13             ` Song Sam
2004-08-09 13:28           ` Marcelo Tosatti
2004-08-10  5:58             ` Song Sam
2004-08-10 11:54               ` Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2004-07-26 16:48 Demke, Torsten

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=20040726163054.GA8872@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=dwmw2@infradead.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rpjday@mindspring.com \
    --cc=samlinuxppc@yahoo.com.cn \
    /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).