From: Dan Malek <dan@embeddededge.com>
To: Jaap-Jan Boor <jjboor@aimsys.nl>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: MPC8272 Fast Ethernet Controller drver
Date: Mon, 01 Mar 2004 08:20:08 -0500 [thread overview]
Message-ID: <40433888.5050202@embeddededge.com> (raw)
In-Reply-To: 1078145848.12061.11.camel@linpc003.aimsys.nl
Jaap-Jan Boor wrote:
> I did a 'bk clone bk://ppc.bkbits.net/linuxppc-2.4' but
> can't find a reference to fcc microcode. Is it not in yet?
Read what I wrote.....Take a look at MPC8272 configurations.
All of the necessary modifications are present.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-01 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 12:57 MPC8272 Fast Ethernet Controller drver Jaap-Jan Boor
2004-03-01 13:20 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-21 15:08 alexv
2005-11-23 6:48 ` Kumar Gala
2004-02-26 13:55 challaharikumar
2004-02-26 15:10 ` Dan Malek
2004-02-26 15:21 ` Kumar Gala
2004-02-27 7:04 ` challaharikumar
2004-02-27 13:37 ` Dan Malek
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=40433888.5050202@embeddededge.com \
--to=dan@embeddededge.com \
--cc=jjboor@aimsys.nl \
--cc=linuxppc-dev@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).