Hi,
in the DSDT there are two different ways of defining, how an interrupt
is supposed to be routed. Currently we are using the LNKA - LNKD method,
which afaict is for legacy support.
The other method is to directly tell the Operating System, which APIC
pin the device is attached to. We can get t
Alexander Graf wrote:
> Hi,
>
> in the DSDT there are two different ways of defining, how an interrupt
> is supposed to be routed. Currently we are using the LNKA - LNKD
> method, which afaict is for legacy support.
> The other method is to directly tell the Operating System, which APIC
> pin th
On May 2, 2008, at 5:35 PM, Marcelo Tosatti wrote:
> On Fri, May 02, 2008 at 04:55:24PM +0200, Alexander Graf wrote:
>> Hi,
>>
>> in the DSDT there are two different ways of defining, how an
>> interrupt
>> is supposed to be routed. Currently we are using the LNKA - LNKD
>> method,
>> which a
On Fri, May 02, 2008 at 04:55:24PM +0200, Alexander Graf wrote:
> Hi,
>
> in the DSDT there are two different ways of defining, how an interrupt
> is supposed to be routed. Currently we are using the LNKA - LNKD method,
> which afaict is for legacy support.
> The other method is to directly tell
Hi,
in the DSDT there are two different ways of defining, how an interrupt
is supposed to be routed. Currently we are using the LNKA - LNKD method,
which afaict is for legacy support.
The other method is to directly tell the Operating System, which APIC
pin the device is attached to. We can ge