linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Andriy Korud <a.korud@vector.com.pl>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Status of 2.6 kernel?
Date: Fri, 14 May 2004 16:23:27 -0700	[thread overview]
Message-ID: <20040514162327.B30155@home.com> (raw)
In-Reply-To: <80908CC5B2C9DB47AAF8C77892FCB44315F774@lion.vector.com.pl>; from a.korud@vector.com.pl on Fri, May 14, 2004 at 04:01:45PM +0200


On Fri, May 14, 2004 at 04:01:45PM +0200, Andriy Korud wrote:
>
> Hi, does anybody know status of 2.6.x kernels for PowerPC/embedded (405)? In kernel config there are corresponding options?

There is a tree, bk://source.mvista.com/linux-2.5-ocp, that has most
4xx boards working, but it's 2.6.5.  The core 4xx support is moving into
current 2.6, but it will be a little bit longer until important drivers
like EMAC and IIC are merged into the stock kernel.

-Matt

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

      reply	other threads:[~2004-05-14 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14 14:01 Status of 2.6 kernel? Andriy Korud
2004-05-14 23:23 ` Matt Porter [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=20040514162327.B30155@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=a.korud@vector.com.pl \
    --cc=linuxppc-embedded@lists.linuxppc.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).