Johannes Berg wrote: > On Fri, 2006-11-10 at 20:06 +0100, Michael Buesch wrote: > >> Only to repeat it. This is _not_ a bcm43xx bug. >> These buttons require a seperate driver, which simply does not exist, >> if someone who owns such a button does not write it. > > Depends on the button. Some buttons are to be queried through the 802.11 > core as documented, others are external (ACPI or such?)
Isn't it possible, by a clever use of the GPIO backplane and 802.11 core masks, to allow a mode where the bcm43xx exports PA and AirlineMode to sysfs and just lets userland decide what to do? This is not going to be the most efficient to deal with the RF kill switches out there, but it should go a long way towards helping those with recalcitrant laptops and/or bioses and/or DSDT... (in my very limited understanding of the things, if we can let the 802.11 core see arbitrary values in lieu of the miniPCI gpio 9 and 13, we should be pretty close to set. Doesn't the section "Disabling BTC" from http://bcm-v4.sipsolutions.net/802.11/Bluetooth_Coexistance hint at such a thing?) -- Cyrille _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
