On Mon, Jan 16, 2012 at 1:16 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Mon, 2012-01-16 at 13:05 +0100, Kay Sievers wrote: > >> > What I'm was asking then is this: Can udev know that it is running from >> > initramfs (presumably that can't be too hard) and simply not reply to >> > async requests it doesn't have firmware for? Then once the real root is >> > mounted it could satisfy (or not) firmware requests from the real root. >> >> We can surely change it to not cancel the firmware request. >> >> Either by making it aware that we run from initramfs, or by never >> cancelling any firmware request and just leave it hanging around for >> forever? Never say 6 months is a long time to reply. :) Fedora uses systemd in the initramfs now, which made it trivial to implement this, and to leave the firmware requests hanging around until we reach in the real rootfs and know if the firmware file is available: http://cgit.freedesktop.org/systemd/systemd/commit/?id=39177382a4f92a834b568d6ae5d750eb2a5a86f9 The logic to tell udev that it runs in the initramfs could easily be implemented by other initramfs tools than dracut, but they usually do not really follow what we do here, so this might for now only work on recent systems using dracut. Cheers, Kay -- 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
