Messages in this thread | | | Date | Thu, 3 Sep 2015 10:33:51 -0700 | Subject | Re: Problems loading firmware using built-in drivers with kernels that use initramfs. | From | Dmitry Torokhov <> |
| |
On Thu, Sep 3, 2015 at 10:23 AM, Arend van Spriel <arend@broadcom.com> wrote: > On 09/03/2015 01:46 AM, Luis R. Rodriguez wrote: >> >> On Wed, Sep 2, 2015 at 4:29 PM, Dmitry Torokhov >> <dmitry.torokhov@gmail.com> wrote: >>> >>> On Wed, Sep 2, 2015 at 4:22 PM, Luis R. Rodriguez <mcgrof@suse.com> >>> wrote: >>>> IMHO its just as hacky as using -EPROBE_DEFER too, but its at least >>>> preemptively hacky. Sadly I can't think of clear and clever way for the >>>> kernel >>>> to know when firmware will be ready either... Would userspace know? >>>> Should the >>>> kernel learn this from userspace ? >>> >>> >>> Yes. Given only userspace knows when firmware is available (I could >>> have it on a separate device and mount it at some time). So maybe >>> userpsace should simply try and scan busses for unbound devices and >>> tell them to re-probe when it decides that firmware is finally >>> available. >> >> >> OK, the folks wanting this mechanism can implement it then. Short of >> that we only have hacks. > > > So what does "userspace knows when firmware is available" mean here. The > specific firmware file the driver wants or the collection of firmware files > which may or may not have the specific firmware file the driver wants. I > assume the latter and re-probe will fail as expected.
Right, the latter.
-- Dmitry
| |