From: Hans Ulli Kroll <ulli.kroll@googlemail.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: Hans Ulli Kroll <ulli.kroll@googlemail.com>,
gemini-board-dev@lists.berlios.de, netdev@vger.kernel.org,
Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
Subject: Re: [RFC PATCH v2] Gemini: Gigabit ethernet driver
Date: Mon, 27 Dec 2010 20:21:44 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1012271956260.8215@localhost> (raw)
In-Reply-To: <20101227103247.8D2E813909@rere.qmqm.pl>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1213 bytes --]
On Mon, 27 Dec 2010, Michał Mirosław wrote:
> Driver for SL351x (Gemini) SoC ethernet peripheral. Based in part
> on work by Paulius Zaleckas and GPLd code from Raidsonic and other
> NAS vendors.
>
> Tested on Raidsonic IcyBox 4220-B (dual SATA NAS).
>
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
>
> ---
>
> Hans, please drop previous mail from the gemini-board-dev queue -
> it had broken headers.
mail is already out.
> + .dis_tx = 1,
> + .dis_rx = 1,
> + .max_len = 2, /* magic; 512 << max_len? */
> + .ipv4_rx_chksum = 1,
> + .ipv6_rx_chksum = 1,
This is what I found in some netbsd code for maxlen
#define CONFIG0_MAXLEN_MASK __BITS(8,10)
#define CONFIG0_MAXLEN_GET(x) (((x) >> 8) &
CONFIG0_MAXLEN_MASK)
#define CONFIG0_MAXLEN(x) (((x) &
CONFIG0_MAXLEN_MASK) << 8)
#define CONFIG0_MAXLEN_1536 0
#define CONFIG0_MAXLEN_1518 1
#define CONFIG0_MAXLEN_1522 2
#define CONFIG0_MAXLEN_1548 3
#define CONFIG0_MAXLEN_JUMBO 4
spec. for the SL3616 says jumbo is 9k frames, but i didn't proved this.
BTW:
Why u64_stats ?
I see only a few driver are using u64_stats.
vlan, br_device and some intel driver
no gigabit driver for marvell devices uses u64_stats
Ulli
next prev parent reply other threads:[~2010-12-27 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 10:32 [RFC PATCH v2] Gemini: Gigabit ethernet driver Michał Mirosław
2010-12-27 19:21 ` Hans Ulli Kroll [this message]
2010-12-28 4:37 ` Ben Hutchings
2010-12-28 5:12 ` Stephen Hemminger
2010-12-29 16:56 ` Hans Ulli Kroll
2010-12-29 18:30 ` Eric Dumazet
2010-12-29 19:28 ` Stephen Hemminger
2010-12-29 19:52 ` Eric Dumazet
2010-12-29 19:57 ` Stephen Hemminger
2010-12-29 21:42 ` Ben Hutchings
2010-12-28 11:45 ` Michał Mirosław
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=alpine.LNX.2.00.1012271956260.8215@localhost \
--to=ulli.kroll@googlemail.com \
--cc=gemini-board-dev@lists.berlios.de \
--cc=linux-kernel.bfrz@manchmal.in-ulm.de \
--cc=mirq-linux@rere.qmqm.pl \
--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).