All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Marcel Holtmann <marcel@holtmann.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: [RFC] b43: rework rfkill code
Date: Wed, 10 Dec 2008 22:42:33 +0100	[thread overview]
Message-ID: <200812102242.35995.mb@bu3sch.de> (raw)
In-Reply-To: <20081210213334.GA7589@khazad-dum.debian.net>

On Wednesday 10 December 2008 22:33:34 Henrique de Moraes Holschuh wrote:
> On Wed, 10 Dec 2008, Johannes Berg wrote:
> > On Wed, 2008-12-10 at 18:23 +0100, Johannes Berg wrote:
> > > Then there's user_claim_unsupported which is set by all drivers but
> > > rt2x00, probably because they have hardware kill switches and thus they
> > > have to set it even if it's not strictly true, because of the lacking
> > > separation between these things (that I pointed out)
> > 
> > IOW, correct me if I'm wrong, it seems to me that user_claim_unsupported
> > really is a wrong name for "has hw kill", which could be avoided if sw
> 
> I never understood what user_claim_unsupported is for.  I left it alone
> because of that, but it looks like some artifact of the old rfkill that did
> horrible things to the input layer.

No, as I just explained. It comes from a time when we didn't have all that input stuff at all.
It was a workaround. rfkill basically had a facility to change the hardware rfkill state from
userspace. As b43 does not support that, I introduced the flag.
Today we have three states (which is still broken, but you saw the rest of the thread...), so I guess
we can remove it again.
We cannot change the hardware state. That's what the flag is (was) for.

-- 
Greetings, Michael.

  reply	other threads:[~2008-12-10 21:43 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 [this message]
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
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=200812102242.35995.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --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=mjg59@srcf.ucam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.