lkml.org 
[lkml]   [2015]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [Linux-nvdimm] [PATCH 0/2] e820: Fix handling of NvDIMM chips
    From
    On Wed, Feb 18, 2015 at 4:47 PM, Christoph Hellwig <hch@infradead.org> wrote:
    > On Wed, Feb 18, 2015 at 10:15:32AM -0800, Dan Williams wrote:
    >> In fact it was originally "type-6" until ACPI 5 claimed that number
    >> for official use, so these platforms, with early proof-of-concept
    >> nvdimm support, have already gone through one transition to a new
    >> number. They need to do the same once an official number for nvdimm
    >> support is published.
    >>
    >> Put another way, these early platforms are already using out-of-tree
    >> patches for nvdimm enabling. They can continue to do so, or switch to
    >> standard methods when the standard is published.
    >
    > Not supporting hardware that is widely avaiable (I have some, too)
    > is not very user friendly.

    Yes, as I agreed with Ingo, allowing a driver to assume control of an
    unknown memory type with a warning or a kernel taint seems fine.


    \
     
     \ /
      Last update: 2015-02-19 02:21    [W:4.358 / U:0.028 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site