| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <8bd0f97a0901081134gc5b6eb9h7f20dea146fc6cd0@mail.gmail.com> Date: Thu, 8 Jan 2009 14:34:43 -0500 From: "Mike Frysinger" <vapier.adi@...il.com> To: "David Miller" <davem@...emloft.net> Cc: cooloney@...nel.org, jeff@...zik.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, graf.yang@...log.com Subject: Re: [PATCH 2/2] netdev: bfin_mac: enable VLAN support in Blackfin MAC driver On Thu, Jan 8, 2009 at 14:30, David Miller wrote: > From: "Mike Frysinger" <vapier >> On Thu, Jan 8, 2009 at 14:01, Mike Frysinger wrote: >> > On Thu, Jan 8, 2009 at 13:55, David Miller wrote: >> >> We can get VLAN packets received and sent, using AF_PACKET >> >> sockets, for example. The chip should still respect those >> >> even if VLAN proper is not being utilized. >> > >> > any tips on doing that ? >> >> or rather, is there a driver or you two you can point out that is >> doing this correctly ? the ones i looked at seemed to be doing it >> like the patch we posted ... > > And I disagree with how those drivers are doing it :-) > > At least the programming of the chip to accept all packet > types properly, VLAN or not, regardless of kernel config, > is definitely IMHO the way to go. i know on our side we all agree with you, we just didnt (dont) know any better ;) -mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists