![]() | ||||||||||
Messages in this thread |
On Monday 24 October 2005 01:19, Alejandro Bonilla Beeche wrote: > >>>>With CONFIG_IPW2200=y I get: > >>>> > >>>>ipw2200: ipw-2.2-boot.fw load failed: Reason -2 > >>>>ipw2200: Unable to load firmware: 0xFFFFFFFE > >>>> > >>>>but with CONFIG_IPW2200=m it works fine. If it doesn't work when built > >>>>into the kernel, why even give people the option? because we want allyesconfig to compile. > I have seen this before with users using FC or RH. They end up > increasing the timeout of the hotplug event and then it all works. But > then again, it only occurs for what I have seen with FC users. Dunno Why. Firmware-loaded-by-hotplug is a necessary compromise in non-GPL world. Ideally, firmware can be GPLed too and be included in the module (u32 firmware_image[NNN]). With closed firmwares, you should use modules (or wait until kernel will have usable hotplug before root fs is mounted). -- vda - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-10-24 04:26 [W:0.284 / U:0.520 seconds] ©2003-2008 Jasper Spaans | ||||||||||