On 06/30/2015 08:06 PM, Hanjun Guo wrote:
> On 2015/7/1 2:35, Rafael J. Wysocki wrote:
>> On Tue, Jun 30, 2015 at 8:25 PM, Rafael J. Wysocki wrote:
>>> Hi Al,
>>>
>>> On Tue, Jun 30, 2015 at 7:29 PM, Al Stone wrote:
On 06/30/2015 11:07 AM, Sudeep Holla wrote:
> Hi Al,
>
> On 18/0
On 2015/7/1 2:35, Rafael J. Wysocki wrote:
> On Tue, Jun 30, 2015 at 8:25 PM, Rafael J. Wysocki wrote:
>> Hi Al,
>>
>> On Tue, Jun 30, 2015 at 7:29 PM, Al Stone wrote:
>>> On 06/30/2015 11:07 AM, Sudeep Holla wrote:
Hi Al,
On 18/06/15 23:36, Al Stone wrote:
> In the ACPI 5.1 ve
Hi Al,
On Tue, Jun 30, 2015 at 9:45 PM, Al Stone wrote:
> On 06/30/2015 12:25 PM, Rafael J. Wysocki wrote:
>> Hi Al,
>>
>> On Tue, Jun 30, 2015 at 7:29 PM, Al Stone wrote:
>>> On 06/30/2015 11:07 AM, Sudeep Holla wrote:
Hi Al,
On 18/06/15 23:36, Al Stone wrote:
> In the ACPI 5
On 06/30/2015 01:05 PM, Rafael J. Wysocki wrote:
> Hi Al,
>
> On Tue, Jun 30, 2015 at 8:39 PM, Al Stone wrote:
>> On 06/30/2015 12:25 PM, Rafael J. Wysocki wrote:
>>> Hi Al,
>>>
>>> On Tue, Jun 30, 2015 at 7:29 PM, Al Stone wrote:
On 06/30/2015 11:07 AM, Sudeep Holla wrote:
> Hi Al,
>>>
On 06/30/2015 12:25 PM, Rafael J. Wysocki wrote:
> Hi Al,
>
> On Tue, Jun 30, 2015 at 7:29 PM, Al Stone wrote:
>> On 06/30/2015 11:07 AM, Sudeep Holla wrote:
>>> Hi Al,
>>>
>>> On 18/06/15 23:36, Al Stone wrote:
In the ACPI 5.1 version of the spec, the struct for the GICC subtable
(stru
Hi Al,
On Tue, Jun 30, 2015 at 8:39 PM, Al Stone wrote:
> On 06/30/2015 12:25 PM, Rafael J. Wysocki wrote:
>> Hi Al,
>>
>> On Tue, Jun 30, 2015 at 7:29 PM, Al Stone wrote:
>>> On 06/30/2015 11:07 AM, Sudeep Holla wrote:
Hi Al,
On 18/06/15 23:36, Al Stone wrote:
> In the ACPI 5
On 06/30/2015 12:25 PM, Rafael J. Wysocki wrote:
> Hi Al,
>
> On Tue, Jun 30, 2015 at 7:29 PM, Al Stone wrote:
>> On 06/30/2015 11:07 AM, Sudeep Holla wrote:
>>> Hi Al,
>>>
>>> On 18/06/15 23:36, Al Stone wrote:
In the ACPI 5.1 version of the spec, the struct for the GICC subtable
(stru
On Tue, Jun 30, 2015 at 8:25 PM, Rafael J. Wysocki wrote:
> Hi Al,
>
> On Tue, Jun 30, 2015 at 7:29 PM, Al Stone wrote:
>> On 06/30/2015 11:07 AM, Sudeep Holla wrote:
>>> Hi Al,
>>>
>>> On 18/06/15 23:36, Al Stone wrote:
In the ACPI 5.1 version of the spec, the struct for the GICC subtable
>
Hi Al,
On Tue, Jun 30, 2015 at 7:29 PM, Al Stone wrote:
> On 06/30/2015 11:07 AM, Sudeep Holla wrote:
>> Hi Al,
>>
>> On 18/06/15 23:36, Al Stone wrote:
>>> In the ACPI 5.1 version of the spec, the struct for the GICC subtable
>>> (struct acpi_madt_generic_interrupt) of the MADT is 76 bytes long;
On 06/30/2015 11:07 AM, Sudeep Holla wrote:
> Hi Al,
>
> On 18/06/15 23:36, Al Stone wrote:
>> In the ACPI 5.1 version of the spec, the struct for the GICC subtable
>> (struct acpi_madt_generic_interrupt) of the MADT is 76 bytes long; in
>> ACPI 6.0, the struct is 80 bytes long. But, there is onl
Hi Al,
On 18/06/15 23:36, Al Stone wrote:
In the ACPI 5.1 version of the spec, the struct for the GICC subtable
(struct acpi_madt_generic_interrupt) of the MADT is 76 bytes long; in
ACPI 6.0, the struct is 80 bytes long. But, there is only one definition
in ACPICA for this struct -- and that is
On 06/19/2015 04:54 AM, Hanjun Guo wrote:
> On 06/19/2015 06:36 AM, Al Stone wrote:
>> In the ACPI 5.1 version of the spec, the struct for the GICC subtable
>> (struct acpi_madt_generic_interrupt) of the MADT is 76 bytes long; in
>> ACPI 6.0, the struct is 80 bytes long. But, there is only one def
On 06/19/2015 06:36 AM, Al Stone wrote:
In the ACPI 5.1 version of the spec, the struct for the GICC subtable
(struct acpi_madt_generic_interrupt) of the MADT is 76 bytes long; in
ACPI 6.0, the struct is 80 bytes long. But, there is only one definition
in ACPICA for this struct -- and that is th
In the ACPI 5.1 version of the spec, the struct for the GICC subtable
(struct acpi_madt_generic_interrupt) of the MADT is 76 bytes long; in
ACPI 6.0, the struct is 80 bytes long. But, there is only one definition
in ACPICA for this struct -- and that is the 6.0 version. Hence, when
BAD_MADT_ENTRY
14 matches
Mail list logo