From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1YKrCW-0004tL-OW for mharc-grub-devel@gnu.org; Mon, 09 Feb 2015 11:28:44 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50240) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YKrCT-0004sW-Lm for grub-devel@gnu.org; Mon, 09 Feb 2015 11:28:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YKrCQ-0000s9-Ff for grub-devel@gnu.org; Mon, 09 Feb 2015 11:28:41 -0500 Received: from mx1.redhat.com ([209.132.183.28]:45162) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YKrCQ-0000s5-9T for grub-devel@gnu.org; Mon, 09 Feb 2015 11:28:38 -0500 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t19GSZVW026375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 9 Feb 2015 11:28:35 -0500 Received: from [10.16.186.145] (prarit-guest.khw.lab.eng.bos.redhat.com [10.16.186.145]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t19GSYla032262; Mon, 9 Feb 2015 11:28:35 -0500 Message-ID: <54D8E032.4040206@redhat.com> Date: Mon, 09 Feb 2015 11:28:34 -0500 From: Prarit Bhargava User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131028 Thunderbird/17.0.10 MIME-Version: 1.0 To: Rajat Jain Subject: Re: [PATCH v2] Add a module for retrieving SMBIOS information References: <87wq3s5j49.fsf@gmail.com> <54D8AB80.9000804@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 209.132.183.28 Cc: "grub-devel@gnu.org" , David Michael , Raghuraman Thirumalairajan , Andrei Borzenkov , Leif Lindholm , Sanjay Jain , Stu Grossman X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 16:28:43 -0000 On 02/09/2015 10:27 AM, Rajat Jain wrote: > Hello, > >>> 1) We have a board that boots Linux and this board itself can be plugged >> into one of different chassis types. We need to pass different parameters to >> the kernel based on the "CHASSIS_TYPE" information that is passed by the >> bios in the DMI / SMBIOS tables. > > Actually, I had simplified the problem statement, to avoid complicating the discussion. Basically, we have enhanced the grub with a "devicetree" command that supplies a flattened device tree to the kernel (just like u-boot or others do in embedded world). > > http://www.denx.de/wiki/view/DULG/LinuxFDTBlob > > However, we need to pass different flattened device tree to the kernel based on different CHASSIS_TYPE. (because different chassis have different hardware components, slots etc that need to be handled differently). > >>> >> >> Whups ... somehow stripped all the cc's on my original reply. >> >> why isn't 1) already in the kernel itself? > > I hope my problem statement clarification above makes it clearer. However, I think the problem is more generic - essentially depending on the current machine type, we may have to do different things on different platforms, such as: > * Loading different kernels / initrd / device tree etc. > * Passing different kernel parameters for: > - different root fs mount points (root=/dev/sda[a/b/c/d]......) > - enabling disabling different kernel features / drivers / subsystem (pci=[nocrs/use_crs]...) > - etc. > Well I understand the request for different kernels, but 1) implies that you're adding additional kernel parameters based on the CHASSIS type? So I'm wondering why you're not making some boot time decision based on the CHASSIS type instead of a bootloader time decision. /me is not against the patchset. I think the idea of booting different kernels based on the HW sounds reasonable from a administration perspective. P. > Thanks, > > Rajat > > > >> -----Original Message----- >> From: Prarit Bhargava [mailto:prarit@redhat.com] >> Sent: Monday, February 09, 2015 4:44 AM >> To: David Michael >> Cc: grub-devel@gnu.org; Leif Lindholm; Andrei Borzenkov; Rajat Jain; Sanjay >> Jain; Raghuraman Thirumalairajan; Stu Grossman >> Subject: Re: [PATCH v2] Add a module for retrieving SMBIOS information >> >> On 02/08/2015 01:54 PM, David Michael wrote: >>> The following are two use cases from Rajat Jain : >>> >>> 1) We have a board that boots Linux and this board itself can be plugged >> into one of different chassis types. We need to pass different parameters to >> the kernel based on the "CHASSIS_TYPE" information that is passed by the >> bios in the DMI / SMBIOS tables. >>> >> >> Whups ... somehow stripped all the cc's on my original reply. >> >> why isn't 1) already in the kernel itself? >> >> P. >