Le jeudi 04 janvier 2007 à 20:16 -0800, Andrew Morton a écrit :
> On Fri, 05 Jan 2007 00:54:32 +0100
> Stelian Pop <[EMAIL PROTECTED]> wrote:
>
> > Le jeudi 04 janvier 2007 à 15:44 -0800, Andrew Morton a écrit :
> > > On Fri, 05 Jan 2007 00:36:23 +0100
> > > Stelian Pop <[EMAIL PROTECTED]> wrote:
> > >
> > > > Added acpi_bus_generate event for forwarding Fn-keys pressed to acpi
> > > > subsystem,
> > > > and made correspondent necessary changes for this to work.
> > >
> > > neato.
> > >
> > > err, how does one use this?
> >
> > :)
> >
> > Well, it seems that on some Vaios (including Nilton's pcg-frv26 but not
> > only this one), the Fn key events aren't seen by sonypi or sony_acpi
> > GHKE method, but do generate an ACPI notify event.
>
> Speak English ;)
Oh, sorry, I'll try again :)
There are several ways of detecting the Fn key events, depending on the
Vaio series:
- some Vaios report them using the SPIC device (driven by sonypi)
- some Vaios let the driver poll for the Fn key status using the GHKE
ACPI method of the SNC device (driven by sony_acpi)
- some Vaios generate an ACPI notify event on the SNC device when a Fn
key is pressed - this is what the latest patch is for.
Unfortunately there are way too many different Vaio series, and no
information about what series support what method. I should have
maintained some sort of wiki to let the users build themselves a
comprehensive list, but I never get around to do it. Maybe Mattia could
do it if he has the time and will...
> > For those laptops, the patch forwards the ACPI event to the ACPI system
> > and can be later interpreted in userspace using
> > acpid's /etc/acpi/default.sh (example directly from Nilton):
>
> The only things Mr Red Hat gave me are /etc/acpi/events/sample.conf and
> /etc/acpi/events/video.conf.
Well, there was an /etc/acpi/default.sh in an older version of acpid...
I'm not sure what it looks like now on a recent Fedora but on my Ubuntu
I still have an acpid package, which has some files in /etc/acpi/
looking familiar.
> I pressed then released a button and dmesg said
>
> [ 76.961568] evbug.c: Event. Dev: <NULL>, Type: 1, Code: 148, Value: 1
> [ 76.961576] evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
> [ 76.963277] evbug.c: Event. Dev: <NULL>, Type: 1, Code: 148, Value: 0
> [ 76.963284] evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
> [ 76.967341] evbug.c: Event. Dev: <NULL>, Type: 1, Code: 148, Value: 1
> [ 76.967349] evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
> [ 76.968136] evbug.c: Event. Dev: <NULL>, Type: 1, Code: 148, Value: 0
> [ 76.968143] evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
>
> Nothing else happened.
Well, you got the events from evdev, which means you probably got them
directly from sonypi (or the regular keyboard..)
Unless your distribution does some neat tricks and somehow feeds the
events coming from somewhere into the event subsystem (like Ubuntu's
acpi_fakekey for example...).
Stelian.
--
Stelian Pop <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
