From: Jay Cliburn <jacliburn@bellsouth.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: csnook@redhat.com, linux-kernel@vger.kernel.org,
atl1-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH 06/26] atl1: update initialization parameters
Date: Tue, 22 Jan 2008 20:13:46 -0600 [thread overview]
Message-ID: <20080122201346.6bb36ca2@osprey.hogchain.net> (raw)
In-Reply-To: <4795BDBB.10904@garzik.org>
On Tue, 22 Jan 2008 04:56:11 -0500
Jeff Garzik <jeff@garzik.org> wrote:
> jacliburn@bellsouth.net wrote:
> > From: Jay Cliburn <jacliburn@bellsouth.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
next prev parent reply other threads:[~2008-01-23 2:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1199152804-3889-1-git-send-email-jacliburn@bellsouth.net>
[not found] ` <1199152804-3889-26-git-send-email-jacliburn@bellsouth.net>
2008-01-01 18:15 ` [PATCH 25/26] [REVISED] atl1: add NAPI support Jay Cliburn
2008-01-02 2:56 ` Joonwoo Park
2008-01-02 3:07 ` David Miller
[not found] ` <1199152804-3889-10-git-send-email-jacliburn@bellsouth.net>
[not found] ` <4795BE39.6000505@garzik.org>
2008-01-23 0:31 ` [PATCH 09/26] atl1: refactor tx processing Jay Cliburn
2008-01-25 1:00 ` Jay Cliburn
2008-01-25 1:08 ` Chris Snook
2008-01-25 3:01 ` Jeff Garzik
[not found] ` <1199152804-3889-7-git-send-email-jacliburn@bellsouth.net>
[not found] ` <4795BDBB.10904@garzik.org>
2008-01-23 2:13 ` Jay Cliburn [this message]
2008-01-23 2:19 ` [PATCH 06/26] atl1: update initialization parameters Jeff Garzik
2008-01-23 2:30 ` Chris Snook
2008-01-01 2:22 [PATCH 00/26] atl1: divide and modernize Jay Cliburn
2008-01-01 2:22 ` [PATCH 06/26] atl1: update initialization parameters Jay Cliburn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080122201346.6bb36ca2@osprey.hogchain.net \
--to=jacliburn@bellsouth.net \
--cc=atl1-devel@lists.sourceforge.net \
--cc=csnook@redhat.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).