From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>, furlot@free.fr
Subject: Re: Compaq laptop RFKILL problems
Date: Thu, 11 Sep 2008 13:00:02 +0100 [thread overview]
Message-ID: <20080911120002.GA1387@srcf.ucam.org> (raw)
In-Reply-To: <48C80241.4000409@lwfinger.net>
On Wed, Sep 10, 2008 at 12:22:09PM -0500, Larry Finger wrote:
> I'm trying to help a Ubuntu user get his BCM4303 working on a Compaq
> Presario R3215. His radio is hardware disabled, but the RFKILL switch
> does not issue a scancode when pushed. Obviously, the Windows software
> polls that key in some manner, but we have no idea what it does.
Can you try the hp-wmi driver?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-09-11 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 17:22 Compaq laptop RFKILL problems Larry Finger
2008-09-11 12:00 ` Matthew Garrett [this message]
2008-09-11 19:50 ` Larry Finger
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=20080911120002.GA1387@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=Larry.Finger@lwfinger.net \
--cc=furlot@free.fr \
--cc=linux-wireless@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).