On Fri, 2 Mar 2007 14:18:40 +0000, Matthew Garrett wrote: > On Fri, Mar 02, 2007 at 03:10:55PM +0100, Jean Delvare wrote: > > > I'm not familiar with APCI at all so I didn't know, but what you write > > here brings some hope. Would it be possible to parse all the DSDT code > > at boot time and deduce all the ports which ACPI would need to request > > to be safe? Or do we have to wait for the accesses to actually happen? > > In theory I /think/ so, but it would probably end up being an > overestimate of the coverage actually needed. Trapping at runtime is > arguably more elegant? It might be more elegant but it won't work. We don't want to prevent ACPI from accessing these I/O ports. If we need to choose only one "driver" accessing the I/O port, it must be acpi, at leat for now, despite the fact that acpi provides very weak hardware monitoring capabilities compared to the specific drivers. Why would we end up with an overestimation if we check the I/O ports at boot time? Do you have concrete cases in mind? Thanks, -- Jean Delvare
