--- On Wed, 26/8/09, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote:
> On Wed, 2009-08-26 at 03:43 +0100,
> Hin-Tak Leung wrote:
>
> > The rfkill event hard just goes 1 and 0 whenever I
> slide the switch,
> > regardless of what NM does . e.g. NM set to disable
> networking has no
> > effect on the 1/0 switch (it happens just depending on
> the slide
> > switch and nothing else), and nothing changes when NM
> noticed
> > rfkill'ed if down & decided to if'up and
> reassociate.
>
> Right, I just wanted to make sure the switch could be
> correctly read
> while the interface is down.
>
> > Basically the rfkill event state just depends on the
> slide switch,
> > regardless of NM (if it is set to enable wireless
> networking, it just
> > if up the device again; if it is set to disable, it
> just stayed
> > disable & the device stay down, but the event
> state continues to
> > respond to the slide switch).
>
> Ok. But this isn't making a lot of sense to me, since
> cfg80211 should
> refuse to UP the device when it's rfkilled.
>
> Or wait ... are you using compat-wireless?
Yes, I am. I mentioned this and did wonder if the _backport/ part in /sys/class is important.
Hin-Tak
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
