On Tue, 2008-07-01 at 15:41 -0300, Henrique de Moraes Holschuh wrote: > On Tue, 01 Jul 2008, Johannes Berg wrote: > > > THIS is very interesting alright... and it is *extremely* important, so > > > let's triple verify it, shall we? > > > > > > Please hack the driver to try to transmit data with that bit set to high, and > > > also with that bit set to low. The best way to go about it is probably to > > > disable the rfkill support (so that it doesn't get in the way), hack the > > > check-the-bit function to just printk its state, and see if the radio can > > > effectively transmit and communicate no matter what state the input pin is > > > at. > > > > > > This is very important. It will caracterize that input pin as either an > > > hardware rfkill line, or as an input device (in which case I would be wrong > > > when I asked to remove the input support from b43, but one step at a time). > > > > Sorry, no, I think I got confused, it should be a hardware rfkill line. > > I'd like to have a certain response for this. Can you test, and assert > whether it is a rfkill line or not? > > And, if it IS a rfkill line, I still need to know if it is flip-flop-like or > not... I am not certain I got the right idea (I understood it was NOT > flip-flop-like). No, it's not flip-flop, there's definitely an on/off bit that always matches the button/hardware state. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
