All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Andrius Kasparavicius <andrius@andrius.org>, netdev@oss.sgi.com
Subject: Re: network interface cards native vlans support in linux kernel?
Date: Fri, 11 Jul 2003 13:18:58 -0400	[thread overview]
Message-ID: <20030711171858.GI2210@gtf.org> (raw)
In-Reply-To: <3F0EEFDD.8050300@candelatech.com>

On Fri, Jul 11, 2003 at 10:11:57AM -0700, Ben Greear wrote:
> eepro100 does not seem to be updated in the kernel anymore, though if you 
> go figure
> out how to install Becker's drivers, he may have it working with vlans
> by now.

I won't say for sure, but I'm fairly certain he does.  Most of his
drivers got a "slightly larger than normal MTU" pass-over a while ago.

I objected to the eepro100 patch, because all it did was change one
magic number to another, in the configuration data.  I had absolutely no
basis for evaluation other than "I hope it works", so it was rejected.

If someone wants to look at his eepro100 and merge in new changes (vlan
or otherwise), that'd be great.  His tulip MTU (aka vlan) changes also
want pulling into mainline kernel, since his changes are _much_ better
than the tulip vlan patch floating around.

	Jeff

  reply	other threads:[~2003-07-11 17:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 15:19 network interface cards native vlans support in linux kernel? Andrius Kasparavicius
2003-07-09 15:28 ` Jeff Garzik
2003-09-11 14:57   ` Rask Ingemann Lambertsen
2003-10-22 12:06   ` Rask Ingemann Lambertsen
2003-10-22 17:01     ` Ben Greear
2003-11-12 19:48       ` Rask Ingemann Lambertsen
2003-07-09 17:15 ` Ben Greear
2003-07-09 19:12   ` Andrius Kasparavicius
2003-07-11 14:59   ` Andrius Kasparavicius
2003-07-11 17:11     ` Ben Greear
2003-07-11 17:18       ` Jeff Garzik [this message]
2003-07-11 17:25         ` Ben Greear
2003-07-09 15:33 Hen, Shmulik
2003-07-09 17:13 ` Ben Greear

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=20030711171858.GI2210@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=andrius@andrius.org \
    --cc=greearb@candelatech.com \
    --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 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.