From: Tony Vroon <tony@linx.net>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: Ivo van Doorn <ivdoorn@gmail.com>, linux-acpi@vger.kernel.org
Subject: Re: Fuijtsu Lifebook RFKILL support
Date: Thu, 11 Dec 2008 01:31:41 +0000 [thread overview]
Message-ID: <1228959101.4045.19.camel@localhost> (raw)
In-Reply-To: <200812110120.mBB1KU9u027511@turbo.physics.adelaide.edu.au>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
On Thu, 2008-12-11 at 11:50 +1030, Jonathan Woithe wrote:
> Do the laptops in question allow you to control each radio individually or
> is it just a single global kill switch?
S6410, S6420 & E8410 all have the one global kill switch on the front.
It seems only the BIOS allows disabling individual radios.
> The only DSDT I have access to is the one from my box - an S7020. This has
> a hardware rfkill switch which AFAIK doesn't have a software interface.
I do believe the S7020 is similar in this respect. It has a global
all-or-nothing switch with no software override. I need to see the DSDT
to be sure, but I'm quite certain I can get an on/off status from it
like on mine.
> There are a few owners of more recent Fujitsu laptops on the list though;
> perhaps they can help out (although at first glance they may not have any
> models additional to those you've already got).
Alright. S6410 testing might still be useful once the code is out there
though. Most of my colleagues prefer to stay on a stable kernel and
don't have a C toolchain to hand.
> Despite this I'll get a DSDT for the S7020 for you in the next few days if
> you like.
Yes please. That one is new to me :)
> Regards
> jonathan
Regards,
Tony V.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-11 1:32 UTC|newest]
Thread overview: 31+ 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 [this message]
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 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 15:19 ` Dan Williams
2008-12-15 17:14 ` Tony Vroon
2008-12-15 17:59 ` Dan Williams
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:42 ` Jonathan Woithe
2008-12-15 23:48 ` Tony Vroon
2008-12-16 0:02 ` Jonathan Woithe
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=1228959101.4045.19.camel@localhost \
--to=tony@linx.net \
--cc=ivdoorn@gmail.com \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=linux-acpi@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 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.