> Ok, in re-reading the firmware code, you are correct, it will still
> timeout in 10 seconds and call your callback.
>
> Which, in my opinion, is wrong. We should have some way to say "wait
> forever". Care to change the firmware_class.c code to support this?
Will give it a try. So far the request_firmware code calls
kobject_hotplug with action as KOBJ_ADD. It invokes a hotplug script
form user mode. I guess we need to have some reverse mechanism which is
invoked when a user writes to the file.
>
> I was assuming that this would wait forever, and is why I pointed you
in
> this direction. Sorry about the confusion here.
>
I guess the earlier method of request_firmware would work out as is with
the only disadvantage of the user having to depend on hotplug mechanism
and echoing firmware name.
Let me know if that is acceptable till we find a solution to wait for
ever without using hotplug stuff.
Thanks
Abhay
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
