netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cesar Eduardo Barros <cesarb@cesarb.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] 2.6 driver for Silan SC92031
Date: Sat, 02 Dec 2006 22:23:05 -0200	[thread overview]
Message-ID: <457218E9.7070902@cesarb.net> (raw)
In-Reply-To: <4571FDE7.9060203@pobox.com>

Jeff Garzik escreveu:
> Cesar Eduardo Barros wrote:
>> From: Cesar Eduardo Barros <cesarb@cesarb.net>
>>
>> This is a driver for the Silan SC92031/Rsltek 8139D NIC chip. It's a
>> rewrite of the vendor 2.4 driver for 2.6, and has been lightly tested
>> on a 2.6.17 x86-64 kernel with the Ubuntu patches (as a out-of-tree
>> module only).
>>
> 
> Seems like it would be best to modify the existing 8139 driver...

I'm not sure it would help. Either the hardware differences are too 
large (for instance, the MII/link part, where the way the vendor driver 
did things implies the MII has only the two basic registers plus two 
vendor registers, meaning I simply cannot use the generic mii code) or 
the code is already modified from the 8139 driver (the vendor driver 
seems to be based on an old version of either pci-skeleton.c or 
8139too.c, and I based my rewrite on the vendor driver).

Of course, one thing I probably will copy from 8139too.c later is the 
NAPI code; I wanted to avoid the extra locking complexity in this first 
version (the fact that the interrupt status register is cleared on 
reading only makes things more complex). If you can suggest other things 
to copy, it would be good, since the copied code is less likely to be wrong.

-- 
Cesar Eduardo Barros
cesarb@cesarb.net
cesar.barros@gmail.com

      reply	other threads:[~2006-12-03  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 22:20 [PATCH] 2.6 driver for Silan SC92031 Cesar Eduardo Barros
2006-12-02 22:27 ` Jeff Garzik
2006-12-03  0:23   ` Cesar Eduardo Barros [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=457218E9.7070902@cesarb.net \
    --to=cesarb@cesarb.net \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.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).