From: Matt Porter <mporter@kernel.crashing.org>
To: linuxppc-embedded@lists.linuxppc.org
Subject: linux-2.5-ocp, 2.6, 4xx, and others
Date: Wed, 7 Apr 2004 10:46:25 -0700 [thread overview]
Message-ID: <20040407104625.A14212@home.com> (raw)
Hello,
The linux-2.5-ocp tree (bk://source.mvista.com/linux-2.5-ocp) has
been updated to 2.6.5 and has a number of enhancements/fixes:
* New OCP infrastructure from 2.4
* A number of ibm_ocp (4xx) updates (some helpers)
* 4xx IIC and EMAC drivers no longer using bd_t to pass info
* All 4xx ports (that were in linux-2.5) build.
* ash, ebony, evb405ep, ocotea, redwood6, walnut tested.
Anybody doing 2.6 4xx work (new ports, forward ports) should be
using this tree and looking at the working examples. Same thing
for any other subarches that are starting to use OCP.
BenH is working on the PM support in OCP and at some time in the
future this should all be going into Linus' tree.
Any questions/suggestions/patches/flames to me.
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2004-04-07 17:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040407104625.A14212@home.com \
--to=mporter@kernel.crashing.org \
--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).