public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Norbert Preining <preining@logic.at>
Cc: Matthias Welwarsky <matze@welwarsky.de>, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] sony-laptop: support rfkill via ACPI interfaces
Date: Sun, 22 Mar 2009 22:46:52 +0000	[thread overview]
Message-ID: <20090322224652.GA13814@srcf.ucam.org> (raw)
In-Reply-To: <20090322220655.GA13887@gamma.logic.tuwien.ac.at>

On Sun, Mar 22, 2009 at 11:06:55PM +0100, Norbert Preining wrote:

> BUT:
> - suddenly the sony-laptop module is convinced that the *hardware*
>   rfkill switch is always turned on, always. Not even reloading an older
>   sony-laptop helped. Rebooting neither. Shutting down and rebooting
>   with an older sony-laptop as default made wifi show up again.
>   I am not sure if cold booting into the latest version of your patch
>   will work, haven't tried till now, sorry, will do tomorrow.

Hmm. Don't /think/ I did anything that should affect that, but it's 
possible. If it's reproducable, can you try commenting out the 
sony_call_snc_handle calls in sony_nc_function_setup and see if they 
change the behaviour? You'll probably need to reboot in between.

> - S1 and S2 do adjustment of the brightness, while Fn-F5 and Fn-F6 do
>   not do anything, but this is probably only configuration stuff.

Ok, sounds like the mapping needs to be changed. Can you let me know 
which ACPI events are generated for each key?

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2009-03-22 22:46 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 [this message]
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
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=20090322224652.GA13814@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=matze@welwarsky.de \
    --cc=preining@logic.at \
    /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