linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Buesch <mb@bu3sch.de>,
	Marcel Holtmann <marcel@holtmann.org>,
	linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de,
	hmh@hmh.eng.br
Subject: Re: [RFC] b43: rework rfkill code
Date: Wed, 10 Dec 2008 18:09:18 +0000	[thread overview]
Message-ID: <20081210180918.GA14782@srcf.ucam.org> (raw)
In-Reply-To: <1228932343.15837.57.camel@johannes.berg>

On Wed, Dec 10, 2008 at 07:05:43PM +0100, Johannes Berg wrote:

> Does the wireless driver get the notification about this from the
> hardware, like it would if this was a real physical switch?

Yes.

> Then it's probably pretty simple: provide a rfkill struct from the 
> driver that updates hard-kill and provide a second rfkill struct for 
> the platform device that doesn't get hard-killed, but also provide a 
> soft-kill input form the platform device. That way, you can toggle 
> that button, but you can also software-enable the platform rfkill 
> device and that in turn re-enables the wifi-rfkill "hw" switch device.

Right. That's prety close to the current situation.
 
> If we need to tie them together in software it gets more complicated
> though.

I think we can avoid that, thankfully.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2008-12-10 18:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 15:09 [RFC] b43: rework rfkill code Matthew Garrett
2008-12-10 15:29 ` Johannes Berg
2008-12-10 16:15   ` Ivo van Doorn
2008-12-10 16:51   ` Marcel Holtmann
2008-12-10 17:18     ` Johannes Berg
2008-12-10 17:23       ` Johannes Berg
2008-12-10 17:28         ` Johannes Berg
2008-12-10 21:33           ` Henrique de Moraes Holschuh
2008-12-10 21:42             ` Michael Buesch
2008-12-10 17:31         ` Michael Buesch
2008-12-10 17:37           ` Johannes Berg
2008-12-10 17:51             ` Matthew Garrett
2008-12-10 18:04               ` Michael Buesch
2008-12-10 18:05               ` Johannes Berg
2008-12-10 18:09                 ` Matthew Garrett [this message]
2008-12-10 18:29                 ` Dan Williams
2008-12-10 18:33                   ` Johannes Berg
2008-12-10 18:59                     ` Dan Williams
2008-12-10 20:07                   ` Michael Buesch
2009-03-29 18:19     ` Johannes Berg
2008-12-11  0:32   ` Julian Calaby
2008-12-11  1:27     ` Michael Buesch
2008-12-11 13:28       ` Kalle Valo
2008-12-10 15:48 ` Michael Buesch
2008-12-10 16:12   ` Matthew Garrett
2008-12-11 16:55 ` Larry Finger
2008-12-12  4:28 ` Larry Finger
2008-12-17 15:48   ` 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=20081210180918.GA14782@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=hmh@hmh.eng.br \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mb@bu3sch.de \
    /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).