From: Jeff Garzik <jgarzik@pobox.com>
To: Claudio Lanconelli <lanconelli.claudio@eptar.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] add driver for enc28j60 ethernet chip
Date: Mon, 17 Dec 2007 18:49:14 -0500 [thread overview]
Message-ID: <47670AFA.1000608@pobox.com> (raw)
In-Reply-To: <475EA546.7030202@eptar.com>
Claudio Lanconelli wrote:
> These patches add support for Microchip enc28j60 ethernet chip
> controlled via SPI.
> I tested it on my custom board (S162) with ARM9 s3c2442 SoC.
> Any comments are welcome.
>
> Signed-off-by: Claudio Lanconelli <lanconelli.claudio@eptar.com>
comments:
* overall: a clean driver that looks mostly acceptable, good work
* use stats in net_device rather than defining your own
* use ethtool rather than 'full_duplex' variable to select duplex
* [suggestion but not requirement] kernel prefers "u8" and "u32" types
to the C99 types uint8_t or uint32_t
* remove the 'inline' markers from functions, and let the compiler make
the decision
* udelay() in enc28j60_phy_write() -- and any similar code pattern --
may not actually delay for the specified amount of time, when you
consider that writes may be posted. normally a read will flush a write.
* Why do interrupt work in a kernel thread? Your comment says you
cannot, but does not explain.
* should use NAPI
* should be able to program multicast list while everything is active
next prev parent reply other threads:[~2007-12-17 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 14:57 [PATCH 1/2] add driver for enc28j60 ethernet chip Claudio Lanconelli
2007-12-11 17:06 ` Stephen Hemminger
2007-12-14 9:21 ` Claudio Lanconelli
2007-12-14 18:56 ` Stephen Hemminger
2007-12-17 23:49 ` Jeff Garzik [this message]
2007-12-20 11:47 ` Claudio Lanconelli
2007-12-17 23:49 ` Jeff Garzik
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=47670AFA.1000608@pobox.com \
--to=jgarzik@pobox.com \
--cc=lanconelli.claudio@eptar.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).