From: Eugene Surovegin <ebs@ebshome.net>
To: llandre <r&d2@dave-tech.it>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Status of Linux 2.6 for 40x and 44x CPUs
Date: Wed, 6 Apr 2005 09:12:29 -0700 [thread overview]
Message-ID: <20050406161229.GA18166@gate.ebshome.net> (raw)
In-Reply-To: <6.0.1.1.0.20050406093338.01eb9d48@192.168.2.1>
On Wed, Apr 06, 2005 at 09:41:27AM +0200, llandre wrote:
> I found some messages about the status of 2.6 kernel for MPC8xx-based
> machines but
> I found nothing about 40x and 44x CPU.
So what? Absence of such messages doesn't mean 4xx doesn't work, I'd
say quite the opposite.
> Anybody can tell me something about
> it? Did it
> get production stable? If not, which are the areas that are under heavy
> development?
4xx is quite stable, although I'm not sure many people use 2.6 in
production.
--
Eugene
next prev parent reply other threads:[~2005-04-06 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 7:41 Status of Linux 2.6 for 40x and 44x CPUs llandre
2005-04-06 16:12 ` Eugene Surovegin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 16:33 Glenn Burkhardt
2005-04-27 22:29 ` Roger Larsson
2005-04-27 23:17 ` Wolfgang Denk
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=20050406161229.GA18166@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=r&d2@dave-tech.it \
/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).