Re: how do you try to get the firmware if not exist

Re: how do you try to get the firmware if not exist

[Darrick J. Wong]

On Thu, Jan 06, 2011 at 10:28:50AM +0800, DuanZhenzhong wrote:
> Hi James and djwong,
> 
> How to you try to get the firmware if not exist? thanks

Uh... are you asking how a driver responds when it asks for firmware and
receives nothing in response?  Or are you asking how to find firmware for a
specific driver?

[ccing linux-scsi given the references to aic94xx in the next message...]

--D

Re: how do you try to get the firmware if not exist

[DuanZhenzhong]

Sorry, just ignore this question, see joe's. thanks

-- 
Regards
zhenzhong


Darrick J. Wong 写道:
> On Thu, Jan 06, 2011 at 10:28:50AM +0800, DuanZhenzhong wrote:
>   
>> Hi James and djwong,
>>
>> How to you try to get the firmware if not exist? thanks
>>     
>
> Uh... are you asking how a driver responds when it asks for firmware and
> receives nothing in response?  Or are you asking how to find firmware for a
> specific driver?
>
> [ccing linux-scsi given the references to aic94xx in the next message...]
>
> --D
>   


--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: how do you try to get the firmware if not exist

[Darrick J. Wong]

On Thu, Jan 06, 2011 at 10:42:03AM +0800, Joe Jin wrote:
> Hi Jamas, Darrick,
> 
> We find upstream commit 45e6cdf41437c72ed79cee64dc69e7f740511e50 need 
> firmware "sas_addr", and it just used by aic94xx, the question is if
> this is a built-in firmware? if not, would you please help us to get it?

"sas_addr" is a (somewhat wonky) method to override the SAS controller's
address when the driver loads and discovers that the aic94xx controller doesn't
have an assigned SAS address.

(Or at least that's the way it was a few years ago...)

[cc linux-scsi]

--D