I was thinking about what to do as a driver *writer* rather than as a driver *user*. include <linux/if_vlan.h> and allocating buffers of (dev->mtu + VLAN_ETH_HLEN) bytes. Some chips, such as the Tuli
e it can handle vlan frames? Is it enought to be prepared to handle frames of size dev->mtu+4? How do I know 4 bytes will be enough tomorrow when someone intr
[cut] What does a network device driver need to do to ensure VLAN compatibility? Is it as simple as allocating buffer space for MTU + 4 bytes or is there more to it than that? -- Regards, Rask Ingema
hello, as far as i know, currently there is no native vlan support in network device drivers. I mean, always need patching MTU.. add 4 bytes.. is there any problems to include full vlans support? And
Native VLAN support has been in the kernel for a while. A few drivers still need patching, and unfortunately the VLAN driver patches floating around all need cleaning up. Jeff
Do you mean "native" as in hardware acceleration offloading? If that's the case than the 8021q vlan module handshakes with the device driver to check for support and that's it. No need to do any sett
Hen, Shmulik wrote: Do you mean "native" as in hardware acceleration offloading? If that's the case than the 8021q vlan module handshakes with the device driver to check for support and that's it. No
is there any problems to include full vlans support? Intel's e100 driver (and all NICs supported by it) support vlans fine, as do most of the GigE NICs. Tulip does not, last I hear, though a work-aro
on vanilla linux kernel, eepro doesn't work, and with 1496 mtu, 8139too works with any mtu (and 1500). which is recommended to use, e100 or eepro100? Andrius.
Andrius Kasparavicius wrote: on vanilla linux kernel, eepro doesn't work, and with 1496 mtu, 8139too works with any mtu (and 1500). which is recommended to use, e100 or eepro100? As I mentioned, the
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 chang
Jeff Garzik wrote: 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,
I was thinking about what to do as a driver *writer* rather than as a driver *user*. include <linux/if_vlan.h> and allocating buffers of (dev->mtu + VLAN_ETH_HLEN) bytes. Some chips, such as the Tuli
What does a driver need to do to make sure it can handle vlan frames? Is it enought to be prepared to handle frames of size dev->mtu+4? How do I know 4 bytes will be enough tomorrow when someone intr
hello, as far as i know, currently there is no native vlan support in network device drivers. I mean, always need patching MTU.. add 4 bytes.. is there any problems to include full vlans support? Na
[cut] What does a network device driver need to do to ensure VLAN compatibility? Is it as simple as allocating buffer space for MTU + 4 bytes or is there more to it than that? -- Regards, Rask Ingema
Author: Andrius Kasparavicius <andrius@xxxxxxxxxxx>
Date: Wed, 9 Jul 2003 18:19:51 +0300 (GMT-3)
hello, as far as i know, currently there is no native vlan support in network device drivers. I mean, always need patching MTU.. add 4 bytes.. is there any problems to include full vlans support? And
Native VLAN support has been in the kernel for a while. A few drivers still need patching, and unfortunately the VLAN driver patches floating around all need cleaning up. Jeff