From: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@transmeta.com>,
VLAN Mailing List <vlan@Scry.WANfear.com>
Subject: Re: [PATCH] 802.1q-support for 3c59x.c
Date: Thu, 8 Nov 2001 21:53:19 +0100 [thread overview]
Message-ID: <20011108215319.G9684@devcon.net> (raw)
In-Reply-To: <20011107165318.A15577@devcon.net> <3BE95B6E.E4EB1B86@mandrakesoft.com>
In-Reply-To: <3BE95B6E.E4EB1B86@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, Nov 07, 2001 at 11:03:58AM -0500
On Wed, Nov 07, 2001 at 11:03:58AM -0500, Jeff Garzik wrote:
> >
> > +/* The Ethernet Type used for 802.1q tagged frames */
> > +#define VLAN_ETHER_TYPE 0x8100
> This needs to be ETH_P_8021Q from if_ether.h.
OK. An updated patch will follow in a few days, as Alan requested not
sending new patches for some days.
> Have you tested this?
Sure. I'm actually using it in production, and other people also
reported that it works well without any problems.
> I should think you would need a dev->change_mtu
> also.
No. The whole point of the patch is that you /don't/ have to change
the MTU on the physical interface for VLAN support.
Though with the registers I figured from the specs it will be only a
matter of a few lines to add a dev->change_mtu to the driver. I can
add it to the patch if someone wants it.
Another question, how do you feel about the #ifdefs in the patch? As
said before, always enabling will not pose any performance penalties
to those not using VLAN tagging, so I could equally well just remove
them if noone objects.
Andreas
--
Andreas Ferber - dev/consulting GmbH - Bielefeld, FRG
---------------------------------------------------------
+49 521 1365800 - af@devcon.net - www.devcon.net
prev parent reply other threads:[~2001-11-08 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 15:53 [PATCH] 802.1q-support for 3c59x.c Andreas Ferber
2001-11-07 16:03 ` Jeff Garzik
2001-11-07 18:15 ` Paul P Komkoff Jr
2001-11-07 18:26 ` Jeff Garzik
2001-11-08 20:53 ` Andreas Ferber [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=20011108215319.G9684@devcon.net \
--to=aferber@techfak.uni-bielefeld.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=vlan@Scry.WANfear.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.