[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1321581563.13860.111.camel@yhuang-dev>
Date: Fri, 18 Nov 2011 09:59:23 +0800
From: Huang Ying <ying.huang@...el.com>
To: Seiji Aguchi <seiji.aguchi@....com>
Cc: "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"lenb@...nel.org" <lenb@...nel.org>,
"Luck, Tony" <tony.luck@...el.com>,
"Chen, Gong" <gong.chen@...el.com>,
Matthew Garrett <mjg@...hat.com>,
"dle-develop@...ts.sourceforge.net"
<dle-develop@...ts.sourceforge.net>,
Satoru Moriya <satoru.moriya@....com>
Subject: Re: [RFC][PATCH]ACPI,APEI,ERST, back end driver for NVRAM
On Fri, 2011-11-18 at 04:47 +0800, Seiji Aguchi wrote:
> Hi,
>
> I developed write/read/clear functions of ERST driver for NVRAM.
> According to ACPI 4.0 specification, we can use the same procedure as storage.
>
> This patch is tested on DELL PowerEdge T310.
This machine has error log address range in NVRAM?
According to ACPI 4.0a spec:
"""
17.5.2.4.1 Error Log Address Range Resides in NVRAM
If the Error Log Address Range resides in NVRAM, then when OSPM writes a
record into the logging
range, the record is automatically persistent and the busy bit can be
cleared immediately. On a subsequent
boot, OSPM can read any persisted error records directly from the
persistent store range. The size of the
persistent store, in this case, is expected to be enough for several
error records.
"""
So it should not work with the same procedure.
Best Regards,
Huang Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists