public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
* Locking out AML code
@ 2009-07-07 14:08 Hector Martin
  2009-07-07 14:29 ` Lin Ming
  0 siblings, 1 reply; 2+ messages in thread
From: Hector Martin @ 2009-07-07 14:08 UTC (permalink / raw)
  To: linux-acpi

I'm writing a driver to access some EC-related functionality on some
Acer laptops. This uses a separate IO port interface and cannot be done
using the standard ec_read / ec_write ACPI functions. The DSDT also
accesses these IO ports for a few things (most notably display
brightness and some WMI methods). Is there a lock I can hold (from
outside the ACPI subsystem) that will lock out AML method execution
while I poke the hardware?

FWIW, the Windows drivers from Acer also access those IO ports directly
(from userspace, no less, with a dumb kernel driver to provide port I/O
to userspace and in the process introduce a huge security hole of
course). There is no way of talking to this hardware via DSDT methods.

-- 
Hector Martin (hector@marcansoft.com)
Public Key: http://www.marcansoft.com/marcan.asc


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-07-07 14:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-07 14:08 Locking out AML code Hector Martin
2009-07-07 14:29 ` Lin Ming

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox