--OHFW44Kv8gQ39vd8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jan 29, 2005 at 05:42:00PM +0100, Jochen Kunz wrote:
> On Sat, 29 Jan 2005 14:52:39 +0100 (CET)
> jdolecek@NetBSD.org (Jaromir Dolecek) wrote:
>=20
> > How do other drivers deal with this? I don't see any special handling
> > in stge(4), bge(4) at least. Do the other drivers just accept all
> > vlan-tagged packets and let vlan_input() sort it out?
> When I wrote iee(4) (sys/dev/ic/i82596.c) all I had to do for vlan(4)
> support was:
> 	sc->sc_ethercom.ec_capabilities |=3D ETHERCAP_VLAN_MTU;
> Packets with a vlan(4) header get feed to if_input() as any other packet
> and the network stack sorts out the vlan(4) stuff automagicaly.

Yes, but that's because the iee device doesn't filter on vlan tag.

Here, Jaromir has a device that can select the vlan ids it will receive,
pretty much like a multicast filter.

I guess an API should be added to have vlan(4) notify the hardware
layer, again just like multicast filter.  AFAICT, no such exists at the
moment.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--OHFW44Kv8gQ39vd8
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iQEVAwUBQfv1RNgoQloHrPnoAQKTeQf/ZPeBVJXRb980Nx+3YpU+jiXN0ZhTs0ig
MvHYk7PMoJZcE/kjynldeykrtp/cBKgF7J6O3DJ6CAwOR26dt13wF47SReQ8Ft7g
3Q9KPy5NPf5Ju5kSC7FO6OexaNWzJ4Bwj32w7x41B0+TCaGS4wlaD3SZVeNoK0Df
i7mJS3oGoN8d4e8BacSWJNDZFfly0+96a1jE4iNGm9nr9nQiCmuQFqyk4HTUrnOE
0h3cgnFlVsJOJbORdF0rv75qyXZs6r5GwvpI2xjsuHrChitIPPZt3oAfUx69EHHp
kbw9nLkawA6YpjrPQi2Cu7/bBGlo1M9LqN6EjM/EBW+pdImOExQ0lQ==
=NFZt
-----END PGP SIGNATURE-----

--OHFW44Kv8gQ39vd8--