On Fri, Mar 4, 2016 at 3:49 PM, Kalle Valo <kvalo@xxxxxxxxxxxxxx> wrote:
[...]
>> +struct brcmfmac_platform_data {
>> + void (*power_on)(void);
>> + void (*power_off)(void);
>> + char *fw_alternative_path;
>> + int device_count;
>> + struct brcmfmac_pd_device devices[0];
>> +};
>
> If I understood correctly this undocumented, and not mentioned in the
> commit log, fw_alternative_path is a new feature in platform data. I
> guess it provides a different firmware image name for the device so that
> devices can have different firmware images on the same system?
Actually, fw_alternative_path was a module parameter, but now it can
also be specified in platform_data. It causes the firmware names in
request_firmware api to be absolute paths thus overriding the path
prefixes tried in firmware_class.
> It's not pretty but I guess okayish. Opinions?
>
> --
> Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
