From: Ducrot Bruno <poup@poupinou.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: eepro100 - 802.1q - mtu size
Date: Fri, 17 Jan 2003 18:48:34 +0100 [thread overview]
Message-ID: <20030117174834.GF12522@poup.poupinou.org> (raw)
In-Reply-To: <20030117162818.GA1074@gtf.org>
Hi Jeff,
On Fri, Jan 17, 2003 at 11:28:18AM -0500, Jeff Garzik wrote:
> On Fri, Jan 17, 2003 at 07:08:40PM +0300, Paul P Komkoff Jr wrote:
> > Replying to Florian Lohoff:
> > > Why is this patch not integerated yet ?
> >
> > Because newer and better e100 driver, which accepts tagged frames and
> > handles it properly, already in the tree
>
> Regardless, people still use eepro100, so I would still like to get
> eepro100 doing VLAN.
>
> The reason why the patch was not accepted is that it changes one magic
> number to another magic number, and without chipset docs, I had no idea
> what either magic number really meant.
>
> Now that Intel has released chipset docs, this is an excellent time to
> re-evaluate those eepro100 VLAN changes. I still refuse to accept a
> "change the magic numbers" patch... any change will need to define
> a constant that describes the bits we wish to set/clear.
>
> Download the e100 documentation from the e1000 sourceforge site:
> http://sourceforge.net/projects/e1000
> ["8255x Developer Manual"]
>
> Jeff
BTW, it look like i82557_config_cmd is never used...
--- linux-2.4/drivers/net/eepro100.c 2003/01/17 17:33:41 1.1
+++ linux-2.4/drivers/net/eepro100.c 2003/01/17 17:34:32
@@ -499,11 +499,13 @@
/* The parameters for a CmdConfigure operation.
There are so many options that it would be difficult to document each bit.
We mostly use the default or recommended settings. */
+#if 0
static const char i82557_config_cmd[CONFIG_DATA_SIZE] = {
22, 0x08, 0, 0, 0, 0, 0x32, 0x03, 1, /* 1=Use MII 0=Use AUI */
0, 0x2E, 0, 0x60, 0,
0xf2, 0x48, 0, 0x40, 0xf2, 0x80, /* 0x40=Force full-duplex */
0x3f, 0x05, };
+#endif
static const char i82558_config_cmd[CONFIG_DATA_SIZE] = {
22, 0x08, 0, 1, 0, 0, 0x22, 0x03, 1, /* 1=Use MII 0=Use AUI */
0, 0x2E, 0, 0x60, 0x08, 0x88,
--
Ducrot Bruno
http://www.poupinou.org Page profaissionelle
http://toto.tu-me-saoules.com Haume page
next prev parent reply other threads:[~2003-01-17 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 14:53 Florian Lohoff
2003-01-17 16:08 ` Paul P Komkoff Jr
2003-01-17 16:28 ` Jeff Garzik
2003-01-17 17:27 ` Dave Jones
2003-01-17 17:49 ` cs89x0 in 2.5 (was Re: eepro100 - 802.1q - mtu size) Jeff Garzik
2003-01-17 20:14 ` Paul P Komkoff Jr
2003-01-21 2:17 ` Alan
2003-01-21 23:39 ` Jeff Garzik
2003-01-17 17:48 ` Ducrot Bruno [this message]
2003-01-17 19:25 ` eepro100 - 802.1q - mtu size Florian Lohoff
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=20030117174834.GF12522@poup.poupinou.org \
--to=poup@poupinou.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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
all inboxes | Powered by JetHome®