From: Mattia Dongili <malattia@linux.it>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] sony-laptop: support rfkill via ACPI interfaces
Date: Sat, 21 Mar 2009 23:37:18 +0900 [thread overview]
Message-ID: <20090321143717.GA21091@kamineko.org> (raw)
In-Reply-To: <20090321140654.GA28039@srcf.ucam.org>
On Sat, Mar 21, 2009 at 02:06:54PM +0000, Matthew Garrett wrote:
> On Sat, Mar 21, 2009 at 03:32:30PM +0900, Mattia Dongili wrote:
>
> > sure, that DMI whitelist is already annoying in its current shape.
> > Getting the ACPI tables to tell us what SNC version we are looking at
> > would be so much better.
> > I just grepped the DSDTs I have here and this is what I got:
> > DSDT.c1s.dsl: Name (SNI4, 0x344A0001)
> > DSDT.c71bw.dsl: Name (SNI4, 0x344A0001)
>
> (snip)
>
> The second byte seems to be the most consistent here - 0x4a for the
> models currently handled by the nc code, 0x4d for the tt and z, 0x55 for
> the p. I've no idea whether this is a monotonically increasing version
> string or a bitmask of supported functionality, but it ought to be
> enough to key off to begin with.
Oh, do you have a vaio type P DSDT to share?
> > want to try to push your patch to mainline or would you prefer to wait?
> > IMO pushing it and eventually fixing support for 0x344a000[10] models is
> > fine. After all your snc_setup code could be easily plugged into the DMI
> > list for the time being and Z and TT users would be happy.
>
> Might as well push it and see what happens?
Sure, if you're ok I'll apply the patch you sent just changing the
rfkill_free and send the whole patch-set to Len tomorrow morning (JST).
cheers
--
mattia
:wq!
next prev parent reply other threads:[~2009-03-21 14:37 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 21:21 [PATCH] sony-laptop: support rfkill via ACPI interfaces Matthew Garrett
2009-03-19 21:28 ` Matthew Garrett
2009-03-19 21:34 ` Norbert Preining
2009-03-19 21:44 ` Matthew Garrett
2009-03-19 21:49 ` Norbert Preining
2009-03-19 21:56 ` Matthew Garrett
2009-03-19 22:15 ` Norbert Preining
2009-03-20 0:28 ` Norbert Preining
2009-03-20 0:38 ` Matthew Garrett
2009-03-20 0:40 ` Norbert Preining
2009-03-20 1:18 ` Norbert Preining
2009-03-20 7:33 ` Matthias Welwarsky
2009-03-21 11:22 ` Matthias Welwarsky
2009-03-21 13:53 ` Matthias Welwarsky
2009-03-21 14:45 ` Mattia Dongili
2009-03-21 16:51 ` Norbert Preining
2009-03-22 17:56 ` Matthew Garrett
2009-03-22 18:03 ` Matthew Garrett
2009-03-22 20:36 ` Norbert Preining
2009-03-22 20:37 ` Matthew Garrett
2009-03-22 22:06 ` Norbert Preining
2009-03-22 22:46 ` Matthew Garrett
2009-03-22 23:10 ` Mattia Dongili
2009-03-22 23:14 ` Matthew Garrett
2009-03-23 0:08 ` Mattia Dongili
2009-03-23 0:10 ` Matthew Garrett
2009-03-23 12:30 ` Norbert Preining
2009-03-23 13:04 ` Mattia Dongili
2009-03-23 15:32 ` Norbert Preining
2009-03-23 15:43 ` Matthew Garrett
2009-03-23 16:00 ` Norbert Preining
2009-03-23 16:09 ` Matthew Garrett
2009-03-23 16:27 ` Norbert Preining
2009-03-23 16:30 ` Matthew Garrett
2009-03-23 16:37 ` Norbert Preining
2009-03-23 16:40 ` Matthew Garrett
2009-03-23 16:41 ` Norbert Preining
2009-03-23 16:51 ` Matthew Garrett
2009-03-23 17:48 ` Norbert Preining
2009-03-23 19:51 ` Matthew Garrett
2009-03-24 0:01 ` Norbert Preining
2009-03-24 0:08 ` Mattia Dongili
2009-03-23 21:48 ` Matthew Garrett
2009-03-24 0:02 ` Norbert Preining
2009-03-24 0:04 ` Matthew Garrett
2009-03-23 12:29 ` Norbert Preining
2009-03-23 14:58 ` Matthew Garrett
2009-03-21 16:18 ` Norbert Preining
2009-03-20 8:52 ` Mattia Dongili
2009-03-20 14:00 ` Matthew Garrett
2009-03-21 4:00 ` Mattia Dongili
2009-03-21 4:35 ` Matthew Garrett
2009-03-21 6:32 ` Mattia Dongili
2009-03-21 14:06 ` Matthew Garrett
2009-03-21 14:37 ` Mattia Dongili [this message]
2009-03-21 14:55 ` Matthew Garrett
2009-03-21 15:10 ` Matthew Garrett
2009-03-21 19:15 ` Matthias Welwarsky
2009-03-22 13:33 ` Matthew Garrett
2009-03-22 2:38 ` Mattia Dongili
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=20090321143717.GA21091@kamineko.org \
--to=malattia@linux.it \
--cc=linux-acpi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox