From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752019AbbCIMKm (ORCPT ); Mon, 9 Mar 2015 08:10:42 -0400 Received: from mail-we0-f175.google.com ([74.125.82.175]:46726 "EHLO mail-we0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751213AbbCIMKl (ORCPT ); Mon, 9 Mar 2015 08:10:41 -0400 Message-ID: <54FD8DBD.3070309@plexistor.com> Date: Mon, 09 Mar 2015 14:10:37 +0200 From: Boaz Harrosh User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Andy Lutomirski , Dan Williams CC: Ingo Molnar , X86 ML , linux-kernel , "Roger C. Pao" , Thomas Gleixner , linux-nvdimm , "H. Peter Anvin" , Matthew Wilcox , Christoph Hellwig , Ross Zwisler Subject: Re: [PATCH 3/3] e820: Add the unknown-12 Memory type (DDR3-NvDIMM) References: <54F82CE0.4040502@plexistor.com> <54F82ED1.8030900@plexistor.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/06/2015 01:09 AM, Andy Lutomirski wrote: <> > > I will be shocked if a standard of this form ever appears. Modern > systems *don't have e820*. The BIOSes that are using this type 12 > hack are awful throwbacks. So far the systems we have, with DDR4 NvDIMM(s) (Actual chips arriving soon) still have BIOS (On by default). The BIOS was yelled "Wolfe" for so long NOW ;-) Again these are working system in the field, who will switch them all to UEFI? How will the UEFI present them to the system? can you point me to the relevant code? (Or did you mean BIOS but with a different communication path than e820?) > > --Andy > Thanks Boaz