From: Michael Buesch <mb@bu3sch.de>
To: Jason Lunz <lunz@falooley.org>
Cc: netdev@vger.kernel.org
Subject: Re: Hardware button support for Wireless cards
Date: Mon, 15 May 2006 18:01:06 +0200 [thread overview]
Message-ID: <200605151801.06379.mb@bu3sch.de> (raw)
In-Reply-To: <e4a6lq$g5v$1@sea.gmane.org>
On Monday 15 May 2006 17:27, you wrote:
> mwallis@serialmonkey.com said:
> > Some people are saying that instead of throwing and ACPI event we should be
> > either use hotplug or internally just disable the radio and somehow inform
> > the dscape stack that the radio has been disabled.
> >
> > What are peoples thoughts here, should we
> >
> > A. be handling this within our drivers and doing "what the user expects" and
> > disabling the hardware radio, or
>
> On my HP laptop with bcm43xx wireless, the button disables the radio in
> HARDWARE, and afaict the driver has no idea about it. The driver notices
> that it's not connected and happily starts scanning again, unaware that
> anything is wrong.
There are registers on the bcm43xx chip (0x158 and 0x49A) that indicate
some "Radio is hardware-disabled" state. We currently don't use that flag
correctly in the driver. Could you please assist me on testing if your switch
actually toggles the bit?
I think best place for this would be on irc.freenode.net #bcm-users
next prev parent reply other threads:[~2006-05-15 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 12:57 Hardware button support for Wireless cards Mark Wallis
2006-05-15 13:25 ` Jiri Benc
2006-05-15 13:59 ` Ivo van Doorn
2006-05-15 14:06 ` Sergey Vlasov
2006-05-15 14:37 ` Dan Williams
2006-05-15 15:12 ` Ivo van Doorn
2006-05-15 16:20 ` Jouni Malinen
2006-05-16 3:10 ` Mark Wallis
2006-05-25 15:15 ` [RFC PATCH 0/2] " Ivo van Doorn
2006-05-15 16:19 ` David Zeuthen
2006-05-15 15:27 ` Jason Lunz
2006-05-15 16:01 ` Michael Buesch [this message]
2006-05-15 19:12 ` Dan Williams
2006-05-15 19:32 ` Michael Buesch
2006-05-15 19:46 ` Jason Lunz
2006-05-15 21:42 ` Ivo van Doorn
2006-05-15 20:08 ` John W. Linville
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200605151801.06379.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=lunz@falooley.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).