From: Tom Rini <trini@kernel.crashing.org>
To: Murray Jensen <Murray.Jensen@cmst.csiro.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linuxppc_2_5 source tree (and others)
Date: Thu, 10 May 2001 09:10:31 -0700 [thread overview]
Message-ID: <20010510091031.A27558@opus.bloom.county> (raw)
In-Reply-To: <21780.989483882@msa.cmst.csiro.au>; from Murray.Jensen@cmst.csiro.au on Thu, May 10, 2001 at 06:38:02PM +1000
On Thu, May 10, 2001 at 06:38:02PM +1000, Murray Jensen wrote:
> Hi, I see that the linuxppc_2_5 bk tree has disappeared from fsmlabs, and
> has been replaced with a linuxppc_2_4_devel tree. Could someone in the
> know please post a quick update what this means, and perhaps what the
> future holds wrt 2.4/2.5 linuxppc (embedded)?
I was hoping Cort would mention this here, but 2_5 has been 'dead' for a
while and is finally gone too. There's still mirrors of it however.
It will exist again, but when 2.5.0 appears and will be based off the
linux_2_4 tree or so. Right now 2_4_devel isn't up to date wrt 8xx/4xx, and
some new boards 2_5 had. I'm working on it. :)
> I guess I should actually ask about what I want :-) The linuxppc_2_5 tree
> had a "drivers/i2c/i2c-algo-8xx.c" file which has disappeared from 2_4_devel.
> I need an i2c driver for linuxppc for the 8260 and figured this would be a
> good place to start. So the question really is what has happened to the 8xx
> i2c driver in the fsmlabs linuxppc_2_5, and has anyone ported this to (or done
> one independently for) the 8260?
These are in 2_4_devel as of last night. I'm also trying to get ahold of the
i2c maintainers so that it can be in linus' tree eventually.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-10 16:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 8:38 linuxppc_2_5 source tree (and others) Murray Jensen
2001-05-10 16:10 ` Tom Rini [this message]
2001-05-10 16:24 ` Dan Malek
2001-05-10 19:33 ` Cort Dougan
-- strict thread matches above, loose matches on Subject: below --
2001-05-10 18:40 Albert D. Cahalan
2001-05-10 18:49 ` Tom Rini
2001-05-10 19:46 ` Albert D. Cahalan
2001-05-10 19:57 ` Cort Dougan
2001-05-10 21:24 ` Albert D. Cahalan
2001-05-10 23:11 ` Cort Dougan
2001-05-11 2:31 ` Murray Jensen
2001-05-11 3:14 ` Cort Dougan
2001-05-11 5:43 ` Murray Jensen
2001-05-10 21:44 ` Tom Rini
2001-05-13 19:33 ` Ira Weiny
2001-05-15 1:40 ` Cort Dougan
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=20010510091031.A27558@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=Murray.Jensen@cmst.csiro.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.