From: Matt Porter <mporter@kernel.crashing.org>
To: "Lawrence E. Bakst" <ml@iridescent.org>, linuxppc-embedded@ozlabs.org
Subject: Re: Is linux-2.5-ocp the current 2.6 4xx code base
Date: Wed, 20 Oct 2004 10:08:05 -0700 [thread overview]
Message-ID: <20041020100805.A14270@home.com> (raw)
In-Reply-To: <20041020161148.GA17445@gate.ebshome.net>; from ebs@ebshome.net on Wed, Oct 20, 2004 at 09:11:48AM -0700
On Wed, Oct 20, 2004 at 09:11:48AM -0700, Eugene Surovegin wrote:
> On Wed, Oct 20, 2004 at 01:02:21AM -0700, Lawrence E. Bakst wrote:
> > At 4:23 PM -0700 5/14/04, Matt Porter wrote:
> > >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.
> >
> > Is the linux-2.5-ocp tree still the right place to get 2.6 4xx code or has that code been moved upstream or someplace else?
>
> Linux-2.5-ocp is obsolete.
>
> > To be more specific which tree to a "bk clone" to get the latest stuff for 4xx.
>
> Use kernel.org's BK tree: bk://linux.bkbits.net/linux-2.5
Oh my, I really should have killed off the old tree.
--
Matt Porter
mporter@kernel.crashing.org
prev parent reply other threads:[~2004-10-20 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 8:02 Is linux-2.5-ocp the current 2.6 4xx code base Lawrence E. Bakst
2004-10-20 16:11 ` Eugene Surovegin
2004-10-20 17:08 ` 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=20041020100805.A14270@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=ml@iridescent.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).