Borislav Petkov writes:
> On Fri, Feb 17, 2017 at 08:31:12AM +0800, Huang, Ying wrote:
>> I am not sure whether the NVS area is a part of the BERT area, but
>> apparently they are overlapped in some way. We will access the whole
>> BERT area here via ioremap the whole range.
>
> This is the part
On Fri, Feb 17, 2017 at 08:31:12AM +0800, Huang, Ying wrote:
> I am not sure whether the NVS area is a part of the BERT area, but
> apparently they are overlapped in some way. We will access the whole
> BERT area here via ioremap the whole range.
This is the part that was missing from the commit
Borislav Petkov writes:
> On Thu, Feb 16, 2017 at 06:24:39PM +0800, Huang, Ying wrote:
>> The NVS area is excluded when request the resources, because the NVS
>> area has been marked as busy already. But the whole BERT memory area is
>> mapped, so we can read from it.
>
> So you're saying the NV
On Thu, Feb 16, 2017 at 06:24:39PM +0800, Huang, Ying wrote:
> The NVS area is excluded when request the resources, because the NVS
> area has been marked as busy already. But the whole BERT memory area is
> mapped, so we can read from it.
So you're saying the NVS area is part of the BERT area an
Borislav Petkov writes:
> On Thu, Feb 16, 2017 at 12:42:00AM +0100, Rafael J. Wysocki wrote:
>> On Tuesday, February 14, 2017 10:01:13 AM Huang, Ying wrote:
>> > From: Huang Ying
>> >
>> > It was reported that some firmware will use ACPI NVS area for BERT
>> > address range. This will cause re
On Thu, Feb 16, 2017 at 12:42:00AM +0100, Rafael J. Wysocki wrote:
> On Tuesday, February 14, 2017 10:01:13 AM Huang, Ying wrote:
> > From: Huang Ying
> >
> > It was reported that some firmware will use ACPI NVS area for BERT
> > address range. This will cause resources conflict because the ACPI
On Tuesday, February 14, 2017 10:01:13 AM Huang, Ying wrote:
> From: Huang Ying
>
> It was reported that some firmware will use ACPI NVS area for BERT
> address range. This will cause resources conflict because the ACPI
> NVS area is marked as busy already. Fix this via excluding ACPI NVS
> are
On 2/13/2017 7:01 PM, Huang, Ying wrote:
From: Huang Ying
It was reported that some firmware will use ACPI NVS area for BERT
address range. This will cause resources conflict because the ACPI
NVS area is marked as busy already. Fix this via excluding ACPI NVS
area when requesting IO resources
From: Huang Ying
It was reported that some firmware will use ACPI NVS area for BERT
address range. This will cause resources conflict because the ACPI
NVS area is marked as busy already. Fix this via excluding ACPI NVS
area when requesting IO resources for BERT.
Reported-and-tested-by: Hans Kr
9 matches
Mail list logo