Messages in this thread | | | Date | Tue, 27 Jun 2017 11:59:15 -0700 | From | Bjorn Andersson <> | Subject | Re: [PATCH] firmware: wake all waiters |
| |
On Tue 27 Jun 11:03 PDT 2017, Luis R. Rodriguez wrote: [..] > Let's consider a crazy case where the uevent gets triggered, and userspace goes > and signals Elon Musk somehow to transmit the needed firmware from Mars through > a serial satellite link to earth, and somehow someday the device is finally > ready to upload firmware from userspace. Once Elon's firmware lands home, we > know all needed firmware has arrived so anything missing we can acknowledge now > as missing, so we upload what we can and kick firmward into final-mode to tell > the kernel we know we're really ready and any pending things will have to be > given up. > > This would prove the custom fallback crap was also never needed. >
Are you saying that each kernel driver should be written so that it will either do direct loading or use firmwared?
From the previous discussion Linus made it very clear that he expect this driver to be compiled as a kernel module and Elon to issue a modprobe once he lands. But IMHO, Elon's decision of using modprobe vs firmwared should be his to make and not mine as a kernel developer.
Regards, Bjorn
| |