Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757916Ab2FTT2O (ORCPT ); Wed, 20 Jun 2012 15:28:14 -0400 Received: from mail-pb0-f46.google.com ([209.85.160.46]:56927 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757549Ab2FTT2M convert rfc822-to-8bit (ORCPT ); Wed, 20 Jun 2012 15:28:12 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 20 Jun 2012 12:28:12 -0700 X-Google-Sender-Auth: qT4aS6cUrJVUrme3vdS-oSiyUzk Message-ID: Subject: Re: SNB PCI root information From: Yinghai Lu To: Bjorn Helgaas Cc: Ulrich Drepper , jbarnes@virtuousgeek.org, Linux Kernel Mailing List , lenb@kernel.org, x86@kernel.org, linux-pci@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1016 Lines: 23 On Wed, Jun 20, 2012 at 11:46 AM, Bjorn Helgaas wrote: > As far as I can tell, here's Yinghai's recommendation: ?the user > argument should not override BIOS _PXM because if the BIOS gets the > _PXM wrong, the user won't be able to work around it with the > argument, which will force the vendor to fix the BIOS. > > I'm not buying it. ?The convention that user-supplied arguments always > take precedence is useful, easy to document, and matches user > expectations. ?It allows the user to work around both missing _PXM and > incorrect _PXM. if the vendor provide _PXM, that _PXM should be right and be trusted. if the vendor does not provide _PXM, we can have command line to input it before user can get one updated BIOS from vendor. Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/