From: Steve Wise <swise@opengridcomputing.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Divy Le Ray <divy@chelsio.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.23 0/2] cxgb3 - Fix dev->priv usage
Date: Tue, 04 Sep 2007 10:09:10 -0500 [thread overview]
Message-ID: <46DD7516.4090905@opengridcomputing.com> (raw)
In-Reply-To: <46D5B296.8020703@chelsio.com>
Roland,
We'll work on upgrading you to T3B2 boards as well.
Stay tuned.
Steve.
Divy Le Ray wrote:
> Roland Dreier wrote:
>>
>> Looks OK to me but I would just roll up the second patch into the
>> first patch and let Jeff merge it as one commit. There's no point in
>> creating an intermediate tree that doesn't build -- it just breaks git
>> bisect for no useful purpose.
>>
>
> Okay, Jeff agrees too, I'll do so.
>
>> Also as a side note, when trying to test this I got the message
>>
>> could not load TP SRAM: unable to load t3a_protocol_sram-1.0.44.bin
>>
>> and you guys seem to only have t3b protocol sram images on your web
>> site. Could you send me the t3a file (or swap out my T3A boards for
>> T3B boards ;)?
>>
> I'd rather fix the driver then:
> First, HW folks tell me that there is no need for engine
> microcode update for T3A.
> Moreover, there is a bug when the file name is constructed.
> We have T3B and T3B2 board revs, the driver looks for
> t3b_protocol_sram-1.0.44.bin for T3B2 boards and defaults to
> t3a_protocol_sram-1.0.44.bin even for T3B boards.
> I submitted a patch fixing this in netdev#upstream.
> I should propose the fix for 2.6.23 instead.
>
> Cheers,
> Divy
>
prev parent reply other threads:[~2007-09-04 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 4:08 Divy Le Ray
2007-08-29 5:35 ` Roland Dreier
2007-08-29 10:42 ` Jeff Garzik
2007-08-29 17:53 ` Divy Le Ray
2007-09-04 15:09 ` Steve Wise [this message]
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=46DD7516.4090905@opengridcomputing.com \
--to=swise@opengridcomputing.com \
--cc=divy@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
/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
Powered by JetHome