On 12.04.19 14:08, Marc Zyngier wrote:
> Hi Zeev,
>
> On 04/04/2019 15:45, Zeev Zilberman wrote:
>> Hi Marc,
>>
>> We have considered exposing our interrupt controller both via MADT
>> OEM-specific entry and via DSDT.
>> We've chosen MADT OEM-specific entry, because it seemed like a
>> reasonabl
On Fri, Apr 12, 2019 at 01:08:00PM +0100, Marc Zyngier wrote:
> Hi Zeev,
>
> On 04/04/2019 15:45, Zeev Zilberman wrote:
> > Hi Marc,
> >
> > We have considered exposing our interrupt controller both via MADT
> > OEM-specific entry and via DSDT.
> > We've chosen MADT OEM-specific entry, because i
Hi Zeev,
On 04/04/2019 15:45, Zeev Zilberman wrote:
> Hi Marc,
>
> We have considered exposing our interrupt controller both via MADT
> OEM-specific entry and via DSDT.
> We've chosen MADT OEM-specific entry, because it seemed like a
> reasonable placeholder for custom interrupt controller, but
Hi Marc,
We have considered exposing our interrupt controller both via MADT
OEM-specific entry and via DSDT.
We've chosen MADT OEM-specific entry, because it seemed like a
reasonable placeholder for custom interrupt controller, but we can move
to DSDT, if this seems like a better way to repres
On Sun, 31 Mar 2019 13:35:33 +0100,
Hanna Hawa wrote:
>
> This patch adds ACPI support for AL-MSIx driver.
>
> The AL-MSIx controller is not standard, is not included in the UEFI
> specification, and will not be added. The driver ACPI binding is
> performed when the following conditions are true
This patch adds ACPI support for AL-MSIx driver.
The AL-MSIx controller is not standard, is not included in the UEFI
specification, and will not be added. The driver ACPI binding is
performed when the following conditions are true:
- OEM ID is AMAZON
- MADT table type is 0x80 (part of the OEM rese
6 matches
Mail list logo
