[lkml]   [2015]   [Sep]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Problems loading firmware using built-in drivers with kernels that use initramfs.
On Thu, Sep 3, 2015 at 10:23 AM, Arend van Spriel <> wrote:
> On 09/03/2015 01:46 AM, Luis R. Rodriguez wrote:
>> On Wed, Sep 2, 2015 at 4:29 PM, Dmitry Torokhov
>> <> wrote:
>>> On Wed, Sep 2, 2015 at 4:22 PM, Luis R. Rodriguez <>
>>> 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.


 \ /
  Last update: 2015-09-03 20:01    [W:0.069 / U:4.900 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site