On Sat, Sep 3, 2016 at 11:01 AM, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > On Sat, Sep 3, 2016 at 10:49 AM, Dmitry Torokhov > <dmitry.torokhov@xxxxxxxxx> wrote: >> >> Unfortunately module loading and availability of firmware is very >> loosely coupled. > > The whole "let's add a new magical proc entry to say that all > filesystems are mounted" is all about the user space coupling them. I will be first to say that the proposed *implementation* is nowhere near what should be accepted. I was thinking if we kernel could post "conditions" (maybe simple stings) that it waits for, and userspace could unlock these "conditions". One of them might be "firmware available". > > I'm just saying that if user space must know about when firmware is > ready to be loaded anyway, just do it rigth. Not with some hacky "you > can now do random things" flag. But by having user space actually say > "put this module together with this firmware". > > If you just put the two pieces together, then the module "will just work". > > And quite frankly, that sounds like a much better maintenance practice > anyway. If some module doesn't work without the firmware, then dammit, > the two *should* go together. Putting them in two different places > would be *INSANE*. Quite often it does until it does not. Most of the touch controllers work just fine until some event (abrupt cutting of power for example) where nvram gets corrupted and they come up in bootloader mode. It is just an example. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
