Zitat von Michael Buesch <[EMAIL PROTECTED]>: > This is wrong. Please do something like the following:
It maybe annoying that some people don't get that but.... Reading the documentation of RFKILL_INPUT, is it impossible to have a userspace program doing this? In that case, the warning would be plain wrong. HS > Index: wireless-testing/drivers/net/wireless/b43/rfkill.c > =================================================================== > --- wireless-testing.orig/drivers/net/wireless/b43/rfkill.c > +++ wireless-testing/drivers/net/wireless/b43/rfkill.c > @@ -186,6 +186,9 @@ void b43_rfkill_init(struct b43_wldev *d > if (err) > b43warn(wl, "Failed to load the rfkill-input module. " > "The built-in radio LED will not work.\n"); > #endif /* CONFIG_RFKILL_INPUT */ > + > +#if !defined(CONFIG_RFKILL_INPUT) && !defined(CONFIG_RFKILL_INPUT_MODULE) > + b43warn(wl, "The rfkill-input subsystem is not available. " > + "The built-in radio LED will not work.\n"); > +#endif > > err = input_register_polled_device(rfk->poll_dev); _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
