| 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
| ||
|
Date: Sun, 08 Jul 2007 19:41:30 +0100 From: James Chapman <jchapman@...alix.com> To: "Kok, Auke" <auke-jan.h.kok@...el.com> CC: Jeff Garzik <jeff@...zik.org>, netdev@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Jason Lunz <lunz@...lexsecurity.com>, Mark McLoughlin <markmc@...hat.com>, e1000-devel@...ts.sourceforge.net, Arjan van de Ven <arjan@...ux.intel.com>, "Ronciak, John" <john.ronciak@...el.com> Subject: Re: RFR: New e1000 driver (e1000new), was: Re: e1000: backport ich9 support from 7.5.5 ? James Chapman wrote: > I envisage something like this:- > > e1000_core.c - common code used by all drivers of the e1000 family. > Exports functions used by actual drivers. Loadable > as a separate module when built as a module. > e1000_82541.c - driver for 82541 > e1000_82542.c - driver for 82542 > e1000_xxxxx.c - driver for xxxxx Please ignore the statement I made above. Having read the code and chip docs again, I realize I jumped to the wrong conclusions when I saw separate source files for each of the 7 chip variants in the new driver. Just wanted to nip it in the bud before it causes any wasted time discussing it. :) -- James Chapman Katalix Systems Ltd http://www.katalix.com Catalysts for your Embedded Linux software development - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists