On 03-08-16 17:35, Dmitry Torokhov wrote: >> In my opinion the kernel should provide functionality to user-space and >> > user-space providing functionality to the kernel should be avoided. > Why? We have bunch of stuff running in userspace for the kernel. Fuse > for example. I am sure there are more. To me "running in user-space" is not the same as providing functionality, but I see your point given below. >> > >>> > > If we solve waiting for rootfs (or something else that may contain >>> > > firmware) then these cases will not need to use usermode helper. >> > >> > If firmware (or whatever) API could get notification of mount syscall it >> > could be used to retry firmware loading instead of periodic polling. >> > That leaves the question raised by you about when to stop trying. The >> > initlevel stuff is probably a user-space only concept, right? So no >> > ideas how the kernel itself could decide except for a "long" timeout. > The kernel really does not know, it can only guess. The firmware may get > delivered by motorized carrier pidgeons. But distribution does know how > they set up, so they are in position to tell the kernel "go" or "give > up". What distro employs pidgeons. Like to give it a spin ;-) Maybe the latest idea from Luis is a viable option. Regards, Arend -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
