| 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: <20080122201346.6bb36ca2@osprey.hogchain.net> Date: Tue, 22 Jan 2008 20:13:46 -0600 From: Jay Cliburn <jacliburn@...lsouth.net> To: Jeff Garzik <jeff@...zik.org> Cc: csnook@...hat.com, linux-kernel@...r.kernel.org, atl1-devel@...ts.sourceforge.net, netdev@...r.kernel.org Subject: Re: [PATCH 06/26] atl1: update initialization parameters On Tue, 22 Jan 2008 04:56:11 -0500 Jeff Garzik <jeff@...zik.org> wrote: > jacliburn@...lsouth.net wrote: > > From: Jay Cliburn <jacliburn@...lsouth.net> > > > > Update initialization parameters to match the current vendor driver > > version 1.2.40.2. [...] > ACK without any better knowledge... but is any addition insight > available at all? No, sorry Jeff. I simply took the vendor's current driver and matched his initialization settings. I can only assume he discovered these values through lab testing. For this and the other "conform to vendor driver" patches in this set, I thought it important to have the in-tree driver match the vendor driver as closely as possible. The primary motivations are (1) my belief that he's in a better position to test the NIC, and (2) to be able to go to him for assistance occasionally and not be rejected because of significant differences between his and our drivers. Jay -- 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