[linux-dvb] [OT] request_firmware()

[linux-dvb] [OT] request_firmware()

[Thomas Kaiser]

Hello

I know this is the wrong list to ask, but you use this function (see subject) 
and I think somebody can answer my question.

Why does request_firmware need a device as parameter?
int request_firmware(const struct firmware **fw, const char *name,
		     struct device *device);

I thought request_firmware just loads the firmware in the struct firmware?

Thanks,

Thomas


-- 
http://www.kaiser-linux.li

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] [OT] request_firmware()

[Michael Krufky]

On Thu, Feb 14, 2008 at 3:37 PM, Thomas Kaiser
<linux-dvb@kaiser-linux.li> wrote:
> Hello
>
>  I know this is the wrong list to ask, but you use this function (see subject)
>  and I think somebody can answer my question.
>
>  Why does request_firmware need a device as parameter?
>  int request_firmware(const struct firmware **fw, const char *name,
>                      struct device *device);
>
>  I thought request_firmware just loads the firmware in the struct firmware?


IIRC, when the device is destroyed, it is a signal for the memory used
to store the firmware to be freed if not done already.

-Mike

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] [OT] request_firmware()

[Thomas Kaiser]

Michael Krufky wrote:
> On Thu, Feb 14, 2008 at 3:37 PM, Thomas Kaiser
> <linux-dvb@kaiser-linux.li> wrote:
>> Hello
>>
>>  I know this is the wrong list to ask, but you use this function (see subject)
>>  and I think somebody can answer my question.
>>
>>  Why does request_firmware need a device as parameter?
>>  int request_firmware(const struct firmware **fw, const char *name,
>>                      struct device *device);
>>
>>  I thought request_firmware just loads the firmware in the struct firmware?
> 
> 
> IIRC, when the device is destroyed, it is a signal for the memory used
> to store the firmware to be freed if not done already.
> 
> -Mike

So, that means when the pointer to device gets null the memory which holds the 
firmware is freed?

Thanks,

Thomas


-- 
http://www.kaiser-linux.li

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb