From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 077F9E0030F for ; Tue, 29 Nov 2011 01:11:33 -0800 (PST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 29 Nov 2011 01:11:33 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,351,1309762800"; d="scan'208";a="81033503" Received: from unknown (HELO envy.home) ([10.255.12.98]) by orsmga002.jf.intel.com with ESMTP; 29 Nov 2011 01:11:33 -0800 Message-ID: <4ED4A1C9.4050102@linux.intel.com> Date: Tue, 29 Nov 2011 01:11:37 -0800 From: Darren Hart User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0 MIME-Version: 1.0 To: Josef Ahmad References: <4ECD138D.50401@linux.intel.com> <4ECE6A6D.8000309@linux.intel.com> <4ED3A1AE.3090107@linux.intel.com> In-Reply-To: X-Enigmail-Version: 1.3.3 Cc: yocto@yoctoproject.org Subject: Re: [PATCH] EFI support for IA X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2011 09:11:34 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 11/29/2011 01:06 AM, Josef Ahmad wrote: > Darren, > > My bad. I added the two configuration statements into local.conf. > Now I moved the two statements into my machine configuration files, and > I confirm it works. The system image is deployed including bootia32.efi > and configuration file, and I successfully booted the kernel. > Excellent! > Good work! > Regarding Grub vs Syslinux as the adopted bootloader, I agree with > choosing the second one as the default, as soon as an EFI release of > Syslinux shows up. > At the same time though, I reckon it might be worthy to keep Grub as a > second choice for EFI bootloading, rather than drop its support. Also, > because of the way you refactored the boot image generation procedure, > adding further bootloaders doesn't require any longer a big effort. Great, we're of the same mind here. -- Darren > > Josef > > On 28 November 2011 14:58, Darren Hart > wrote: > > > > On 11/28/2011 01:06 AM, Josef Ahmad wrote: > > Hi Darren, > > > > I checked out your dvhart/efi branch and attempted to build my BSP. > > I inlcuded "efi" to my MACHINE_FEATURES, and "live" to my > IMAGE_FSTYPES, > > so as to get an .hddimg file. > > > > I haven't found GRUB in my deployed hddimg though. Maybe I'm missing > > something? > > > Hi Josef, > > Do you see bootia32.efi and grub.cfg in the root directory of the > hddimg? That is all it installs. > > -- > Darren > > > > > Thanks > > > > Josef > > > > On 24 November 2011 16:01, Darren Hart > > >> > wrote: > > > > On 11/24/2011 12:48 AM, Josef Ahmad wrote: > > > Hi Darren, > > > > > > I'll track your branch to sync our efforts. > > > > Hi Josef, > > > > Great. I just sent an RFC patch series to this list last > night. Please > > try it out and see how it goes. > > > > > > > > I meant to only generate the Grub EFI binary for the target, > without > > > including any tool/library into the root filesystem: I assumed > > that it's > > > sufficient to deploy the bootloader onto the top-level image. > > That's why > > > > Agreed. > > > > > I build natively the mkimage tool and run that on the host > to get the > > > EFI executable. Now, as you justly point out, there's a target > > mismatch: > > > mkimage incorrectly calls out the host architecture under the -O > > switch, > > > whereas it should have been something like ${TARGET_ARCH}-efi. > > > > Right. That took some doing, but it is now resolved in my branch. > > > > > > > > That said, surely a solution that embodies the GRUB tools > into the > > root > > > filesystem is desirable. > > > > That can be accomplished using the grub_1.99 recipe. Perhaps > we should > > enable building with EFI if MACHINE_FEATURES includes "efi". I > consider > > that to be separate from this effort. > > > > > > > Feel free to merge my grub config generator into your branch, as > > well as > > > any of my contrib you may like. Speaking of grub.bbclass, I > named > > it so > > > as it's not specifically tied to the EFI mode. It basically > builds up > > > the grub configuration menu, based off machine-specific > parameters. I > > > implemented it among the lines of syslinux.bbclass. > > > > While the menu creation isn't necessarily EFI specific, the > rest of the > > bbclass is. If we wanted to, we could create another > grub.bbclass that > > can do a live image with GRUB legacy booting. However, I'm > also working > > to use the syslinux family of loaders wherever possible. I'm using > > grub-efi as a stop-gap until an EFI syslinux becomes > available. The idea > > here is to keep things consistent from the live image to the > installed > > image, as well as reduce the number of bootloaders and > configuration > > files we need deal with for a given BSP. > > > > Please review the patch series I sent out and let me know if > it works > > for your purposes. General code review is needed as well. > > > > Thanks Josef! > > > > -- > > Darren Hart > > Intel Open Source Technology Center > > Yocto Project - Linux Kernel > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > > > https://lists.yoctoproject.org/listinfo/yocto > > > > > > -- > Darren Hart > Intel Open Source Technology Center > Yocto Project - Linux Kernel > > -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel