Hi All, On Wed, Dec 18, 2013 at 8:49 AM, Sander Eikelenboom <li...@eikelenboom.it> wrote: > > Tuesday, December 17, 2013, 10:27:09 PM, you wrote: > >> On Tue, Dec 17, 2013 at 09:33:19PM +0100, Sander Eikelenboom wrote: >> Debian official kernels use modular drivers, and neither >> initramfs-tools nor dracut includes wireless drivers in the initramfs. >> If you build a custom kernel with built-in drivers then you most >> likely don't need an initramfs at all. > >> As maintainer of crda in Debian, I could add an initramfs hook that >> would include it in an initramfs. But I don't understand why it would >> be worth doing so. Why is it so useful to have wireless drivers >> built-in *and* an initramfs? If you think I should do this then open >> a bug (reportbug crda). > > Indeed, I looked for a crda hook for initramfs-tools but didn't find it, so > skipped that idea > for the moment. > > So if i combine the two .. it's essentially just a very bad idea to compile > the wireless stuff in. > It needs a access to a userland program at module load time, or it will block > forever.
>From looking at the code and files in the Debian package, the CRDA "calls" are actually events which are then handled by udev. So what happens to events passed to udev which aren't handled by any of it's (current) rules? Thanks, -- Julian Calaby Email: julian.cal...@gmail.com Profile: http://www.google.com/profiles/julian.calaby/ .Plan: http://sites.google.com/site/juliancalaby/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
