From: Jeff Garzik <jgarzik@pobox.com>
To: linux-kernel@vger.kernel.org, Florian Lohoff <flo@rfc822.org>
Cc: netdev@oss.sgi.com
Subject: Re: eepro100 - 802.1q - mtu size
Date: Fri, 17 Jan 2003 11:28:18 -0500 [thread overview]
Message-ID: <20030117162818.GA1074@gtf.org> (raw)
In-Reply-To: <20030117160840.GR12676@stingr.net>
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
next parent reply other threads:[~2003-01-17 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030117145357.GA1139@paradigm.rfc822.org>
[not found] ` <20030117160840.GR12676@stingr.net>
2003-01-17 16:28 ` Jeff Garzik [this message]
2003-01-17 17:27 ` eepro100 - 802.1q - mtu size Dave Jones
2003-01-17 17:49 ` cs89x0 in 2.5 (was Re: eepro100 - 802.1q - mtu size) Jeff Garzik
2003-01-21 2:17 ` Alan
2003-01-21 23:39 ` Jeff Garzik
2003-01-17 17:48 ` eepro100 - 802.1q - mtu size Ducrot Bruno
2003-01-17 19:25 ` 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=20030117162818.GA1074@gtf.org \
--to=jgarzik@pobox.com \
--cc=flo@rfc822.org \
--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;
as well as URLs for NNTP newsgroup(s).