linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Rainer Kloud <rainer.kloud@siemens.at>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8260 FCC Ethernet driver
Date: Fri, 15 Sep 2000 11:43:17 -0400	[thread overview]
Message-ID: <39C24395.756E3252@mvista.com> (raw)
In-Reply-To: 39C1DE70.F1D90668@siemens.at


Rainer Kloud wrote:

> So my question is: Does anyone have a Ethernet Driver
> for the FCC?


Ummmm.....arch/ppc/8260_io/fcc_enet.c should do the trick......

I am constantly making updates to the sources for 8260, and recently
updated the driver (there is another major update coming).  You should
probably get used to using the BitKeeper tree from FSM Labs...
	www.fsmlabs.com/linuxppcbk/html


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-09-15 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-15  8:31 8260 FCC Ethernet driver Rainer Kloud
2000-09-15 15:43 ` Dan Malek [this message]
2000-09-15 16:12   ` Dan Malek
2000-09-20 14:11   ` 8260 FCC Ethernet driver, cpm_8260.h Rainer Kloud
2000-09-20 16:26     ` 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=39C24395.756E3252@mvista.com \
    --to=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rainer.kloud@siemens.at \
    /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).