From: Kumar Gala <kumar.gala@freescale.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>,
Kumar Gala <kumar.gala@motorola.com>,
Yuji Nishimura <yujin@pp.iij4u.or.jp>,
Stefan Nickl <Stefan.Nickl@kontron.com>
Subject: Re: Stability of network/io on MPC8540ADS?
Date: Tue, 18 May 2004 08:39:36 -0500 [thread overview]
Message-ID: <CDE6C69C-A8D0-11D8-AE46-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <20040517221618.EBFB8C109F@atlas.denx.de>
No problem, just wanted to make people aware of the fact the patches
were required and available on the u-boot list.
- kumar
On May 17, 2004, at 5:16 PM, Wolfgang Denk wrote:
> In message <236747C3-A84B-11D8-A8A3-000393DBC2E8@freescale.com> you
> wrote:
>>
>> I've pushed the bug fix from Yuji and a number of other changes to the
>> linuxppc-2.4 bitkeeper tree. Please note that this change requires an
>> updated u-boot due to memory map changes. The patches exist on the
>> u-boot list from Jon Loeliger. I'm not sure if they have yet made it
>> into u-boot CVS for the MPC8540/60 ADS boards.
>
> Sorry, not yet. It's still sitting in my inbound queue.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> Software Engineering: Embedded and Realtime Systems, Embedded Linux
> Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
> What was sliced bread the greatest thing since?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-05-18 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 15:27 Stability of network/io on MPC8540ADS? Stefan Nickl
2004-05-13 22:55 ` Kumar Gala
2004-05-14 18:54 ` Yuji Nishimura
2004-05-14 18:52 ` Kumar Gala
2004-05-14 19:11 ` Yuji Nishimura
2004-05-17 6:48 ` Stefan Nickl
2004-05-17 21:42 ` Kumar Gala
2004-05-17 22:16 ` Wolfgang Denk
2004-05-17 23:24 ` Dan Malek
2004-05-18 13:39 ` Kumar Gala [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=CDE6C69C-A8D0-11D8-AE46-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=Stefan.Nickl@kontron.com \
--cc=kumar.gala@motorola.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
--cc=yujin@pp.iij4u.or.jp \
/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).