From: Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: tony-MIcqEarIBAk@public.gmane.org
Cc: Henrique de Moraes Holschuh
<hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>,
Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Ivo van Doorn <ivdoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jwoithe-JAjqph6Yjy+wq2+NMbbSVdf8k/1jCSAM@public.gmane.org,
Peter Gruber <nokos-hi6Y0CQ0nG0@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Fuijtsu Lifebook RFKILL support
Date: Mon, 15 Dec 2008 12:59:44 -0500 [thread overview]
Message-ID: <1229363984.12163.114.camel@localhost.localdomain> (raw)
In-Reply-To: <1229361241.13400.1.camel@localhost>
On Mon, 2008-12-15 at 17:14 +0000, Tony Vroon wrote:
> On Mon, 2008-12-15 at 10:19 -0500, Dan Williams wrote:
> > I plan to beat the shit out of the hal killswitch support pretty soon.
> > AFAIK it still doesn't know about softblock, which is part of the whole
> > reason for the rfkill rewrite in 2.6.26 anyway. It also doesn't yet
> > (AFAIK) support uevents from killswitches either, which sucks.
>
> Thanks Dan.
> Could you let me know when you've committed this code so I have another
> shot at implementing rfkill reporting in fujitsu-laptop?
Yeah, though the HAL support will be coded to the kernel rfkill devices,
so if the platform or the wifi driver supports the kernel rfkill
interface, the HAL bits should work.
> P.S. Did you get my e-mail about the Sierra Wireless MC8790?
Yes; it's hal-info commit 8912ec2b5d0a221a74156c047b18a26b2d916e13.
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-12-15 17:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 1:05 Fuijtsu Lifebook RFKILL support Tony Vroon
2008-12-11 1:20 ` Jonathan Woithe
2008-12-11 1:31 ` Tony Vroon
2008-12-11 1:44 ` Jonathan Woithe
2008-12-11 16:52 ` Henrique de Moraes Holschuh
2008-12-11 17:33 ` Tony Vroon
2008-12-11 19:47 ` Henrique de Moraes Holschuh
2008-12-12 1:50 ` Tony Vroon
2008-12-12 19:53 ` Henrique de Moraes Holschuh
2008-12-12 20:33 ` 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
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
[not found] ` <20081215115336.GD17648-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>
2008-12-15 15:19 ` Dan Williams
2008-12-15 17:14 ` Tony Vroon
2008-12-15 17:59 ` Dan Williams [this message]
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=1229363984.12163.114.camel@localhost.localdomain \
--to=dcbw-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org \
--cc=ivdoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jwoithe-JAjqph6Yjy+wq2+NMbbSVdf8k/1jCSAM@public.gmane.org \
--cc=lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nokos-hi6Y0CQ0nG0@public.gmane.org \
--cc=tony-MIcqEarIBAk@public.gmane.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