From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Tony Vroon <tony@linx.net>, Len Brown <lenb@kernel.org>,
Ivo van Doorn <ivdoorn@gmail.com>,
linux-acpi@vger.kernel.org, jwoithe@physics.adelaide.edu.au,
Peter Gruber <nokos@gmx.net>,
linux-wireless@vger.kernel.org
Subject: Re: Fuijtsu Lifebook RFKILL support
Date: Sat, 13 Dec 2008 17:57:45 +0000 [thread overview]
Message-ID: <20081213175745.GA6825@srcf.ucam.org> (raw)
In-Reply-To: <20081213132857.GA11428@khazad-dum.debian.net>
On Sat, Dec 13, 2008 at 11:28:57AM -0200, Henrique de Moraes Holschuh wrote:
> > Len, I would still like to export the 3 values learned about in this
> > event to userspace. Is it alright for me to create 3 read-only files on
> > the platform device? (docked, lid, radios)
> > It would if anything simplify the code.
>
> FWIW, I think this is also the way to go. It is much easier for
> userspace to deal with sysfs attributes. HAL can deal with more
> complex stuff, but shell script writers often don't know how to, nor
> care to, deal with HAL.
I feel like I'm missing something here, but surely what we're talking
about is simply a single rfkill device that affects all radios and as
such should have a new RFKILL_TYPE_ALL type associated with it? I'd read
this as there being a software control that affected all radios. If
there's no software control at all then I agree that providing an rfkill
class here isn't appropriate.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-12-13 17:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1228957506.4045.11.camel@localhost>
[not found] ` <20081211165247.GA4844@khazad-dum.debian.net>
[not found] ` <1229016827.6446.6.camel@localhost>
[not found] ` <20081211194734.GA18132@khazad-dum.debian.net>
[not found] ` <1229046602.4030.13.camel@localhost>
[not found] ` <20081212195331.GA12679@khazad-dum.debian.net>
2008-12-12 20:33 ` Fuijtsu Lifebook RFKILL support Len Brown
2008-12-13 12:47 ` Tony Vroon
2008-12-13 13:28 ` Henrique de Moraes Holschuh
2008-12-13 17:57 ` Matthew Garrett [this message]
2008-12-13 20:55 ` Tony Vroon
2008-12-13 21:24 ` Matthew Garrett
2008-12-14 3:13 ` Henrique de Moraes Holschuh
2008-12-14 17:05 ` Dan Williams
2008-12-15 11:53 ` Henrique de Moraes Holschuh
2008-12-15 15:19 ` Dan Williams
2008-12-15 17:14 ` Tony Vroon
2008-12-15 17:59 ` Dan Williams
2008-12-16 13:50 ` Tony Vroon
2008-12-16 15:23 ` Dan Williams
2008-12-15 23:42 ` Jonathan Woithe
2008-12-15 23:48 ` Tony Vroon
2008-12-16 0:02 ` Jonathan Woithe
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=20081213175745.GA6825@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nokos@gmx.net \
--cc=tony@linx.net \
/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).