linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>,
	Dan Malek <dan@embeddededge.com>, Wolfgang Denk <wd@denx.de>,
	Joakim Tjernlund <joakim.tjernlund@lumentis.se>,
	sanjeevr@myw.ltindia.com
Subject: [PATCH] Driver for FECs on motorola DUET (87x/88x)
Date: Thu, 13 May 2004 17:42:48 +0300	[thread overview]
Message-ID: <40A38968.6060701@intracom.gr> (raw)

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

Hello

The attached patch is a driver for both the FECs on the new
motorola 87x/88x processors.

I first tried to modified the old FEC driver but due to hardware
peculiarities and the large modification needed I decided to
create a new driver based on the old one.

The main features of the driver are:

o Supports correctly both FECs.
o Easier way to add new boards.
o MII ethtool support.
o NAPI support.
o Support polling mode of link changes even with
  generic phys.
o No fixed receive ethernet buffers zero copy receive,
  based on the work of Joakim Tjernlund.
o Copy small received frames to reduce memory consumption.
o I think it will be easier to port to 2.6. Haven't yet a
  chance to try it though.

The major changes were:

o Moved location to drivers/net
o It is now a whole subdirectory instead of just one file.
o MII no longer interrupt driven.

Note that the board which uses it is not in the tree
since it depends on other patches that were rejected for 2.4.
However it is trivial to add more boards.

Please take a look and comment.

Regards

Pantelis


[-- Attachment #2: duet-fec2.diff.bz2 --]
[-- Type: application/x-bzip2, Size: 13872 bytes --]

             reply	other threads:[~2004-05-13 14:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 14:42 Pantelis Antoniou [this message]
     [not found] ` <40A4C04A.8060508@intracom.gr>
2004-05-14 14:22   ` [PATCH] Driver for FECs on motorola DUET (87x/88x) Joakim Tjernlund
2004-05-14 14:14     ` Pantelis Antoniou
2004-05-14 14:48   ` Pantelis Antoniou
2004-05-14 15:23     ` Joakim Tjernlund
2004-05-14 15:18       ` Pantelis Antoniou
2004-05-14 15:32       ` Tom Rini
2004-05-14 21:52   ` Dan Malek
2004-05-24 13:40     ` Pantelis Antoniou
2004-05-24 17:18       ` Dan Malek
2004-05-24 19:11         ` Joakim Tjernlund
2004-05-25  1:10         ` Paul Mackerras
2004-05-25  9:49           ` Joakim Tjernlund
2004-05-25 10:24             ` Paul Mackerras
     [not found]         ` <40B327EF.2090903@intracom.gr>
2004-05-25 14:01           ` 2.6 on 8xx (was [PATCH] Driver for FECs on motorola DUET (87x/88x)) Robert P. J. Day
2004-05-25 14:08             ` Pantelis Antoniou
2004-05-25 15:06               ` Robert P. J. Day
     [not found] <D50B7204-AE3C-11D8-B485-003065F9B7DC@embeddededge.com>
2004-05-25 12:29 ` [PATCH] Driver for FECs on motorola DUET (87x/88x) Joakim Tjernlund

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=40A38968.6060701@intracom.gr \
    --to=panto@intracom.gr \
    --cc=dan@embeddededge.com \
    --cc=joakim.tjernlund@lumentis.se \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=sanjeevr@myw.ltindia.com \
    --cc=wd@denx.de \
    /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).