[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74962ea30903311506m41306659td0cd70c5736f6660@mail.gmail.com>
Date: Wed, 1 Apr 2009 15:06:12 +1700
From: Azael Avalos <coproscefalo@...il.com>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: linux-acpi@...r.kernel.org, dsilvers@...tec.co.uk,
toshiba_acpi@...ebeam.org, linux-kernel@...r.kernel.org,
lenb@...el.com
Subject: Re: [PATCH 2/2] toshiba-acpi: Support TOS1900-type devices
Hi there,
On Wed, Apr 1, 2009 at 2:47 PM, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> Despite toshiba_acpi exporting TOS1900 as a modalias, it doesn't appear to
> support these machines. They have their HCI method implemented in a
> different but compatible manner and so need a different method address.
Indeed, my Satellite X205-9800 uses that method, however, it only provides
HCI call 0x001E (Hotkey Events) and no System Event FIFO (0x0016),
instead, hotkeys are entered on a variable called TOHK (TOshiba HotKeys?).
Located in my model in
PCI0.LPCB.EC0.TOHK
and it appears that it can be _polled_ tru' method INFO
(TOSH_INTERFACE_2 ".INFO"),
perhaps a small change in the polling to reflect to that method for
TOS1900 devices would be necessary.
On my model the complete call would be:
\\_SB.VALZ.SPFC
\\_SB.VALZ.INFO
Is it different from \\_SB_.VALZ.SPFC or it simply doesn't matter?
Saludos
Azael
--
-- El mundo apesta y vosotros apestais tambien --
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists