linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddedalley.com>
To: "dibacco\@inwind\.it" <dibacco@inwind.it>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: MPC875 porting
Date: Sun, 29 Jan 2006 16:47:51 -0500	[thread overview]
Message-ID: <53035e2c9b2c98da1fa34788a7079697@embeddedalley.com> (raw)
In-Reply-To: <ITVFT5$D7FAA0BB780EC8B8F02A50A5AB92E2E0@libero.it>


On Jan 29, 2006, at 3:34 PM, dibacco@@inwind..it wrote:

> I have a custom board with a MPC875 and two ethernet ports. I think I 
> need to modify the enet.c to have two ethernet ports working.

Please read the archives and use the new drivers/net/fs_net
driver and the new serial port drivers.  This has all been updated
and should just work for you.

Thanks.

	-- Dan

  reply	other threads:[~2006-01-29 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-29 20:34 MPC875 porting dibacco
2006-01-29 21:47 ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-29 20:36 dibacco

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=53035e2c9b2c98da1fa34788a7079697@embeddedalley.com \
    --to=dan@embeddedalley.com \
    --cc=dibacco@inwind.it \
    --cc=linuxppc-embedded@ozlabs.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).