[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA9_cmenbY9GStibRjO0BfTq0kzzzqThiLeOygJsT9L03BFsBQ@mail.gmail.com>
Date: Mon, 18 Jun 2018 12:01:37 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Toshi Kani <toshi.kani@....com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Bob Moore <robert.moore@...el.com>,
Linux ACPI <linux-acpi@...r.kernel.org>,
"Elliott, Robert (Persistent Memory)" <elliott@....com>,
juston.li@...el.com
Subject: Re: [PATCH v3 1/2] acpi/nfit: Update nfit driver to comply with ACPI 6.1
On Mon, Apr 25, 2016 at 2:43 PM Toshi Kani <toshi.kani@....com> wrote:
>
> ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure
> as follows.
> - Valid Fields, Manufacturing Location, and Manufacturing Date
> are added from reserved range. No change in the structure size.
> - IDs (SPD values) are stored as arrays of bytes (i.e. big-endian
> format). The spec clarifies that they need to be represented
> as arrays of bytes as well.
>
Circling back on this a couple years too late... where are you reading
this "arrays of bytes" note. As far as I can see this is wrong. JEDEC
says that vendor id is stored LSB of the id is stored at the lowest
byte in SPD, which is little endian. So it seems Linux has showing the
incorrect value for a long time now.
Powered by blists - more mailing lists