From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-in25.apple.com (mail-out25.apple.com [17.171.2.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 5729A21DFC86B for ; Sun, 13 Aug 2017 11:06:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1502647729; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=n2KZ0kg1NeRa86I9fueQpaFoWOCffq+HAI8A0ShHivw=; b=0N0oSoYkpvpI4bcYV0Sv4q0dx5xS0Ir5FJrtS/SaFelv9eH472Q1IJZYY52zg0Ji w29fE3fcM2RYlWEUY3+rOTg1Z97BHNZiHae7gfZKc6isfOPSNhSyqB9xsnTSOcWn /pE8pEUMWYyxqj+RDO4rZI5gqOXaP/ZCf9zIjpzJW1spWHJk7F6GenOZtmKfU7+V L/R1nFwtSpYHw3kNqJQFvyM92g5mPNERcHA3MrfProdk43Qj4iXOQAOoTJfHVzRS i0gtlLx0G9QvxWqelyf/9YnlSP3K9B+gbyXu54EyhjCVsQFyCMzFw5NJsBpr9i7d j9How+Bc+naAn09Hc+xzSA==; Received: from relay23.apple.com (relay23.apple.com [17.171.128.104]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in25.apple.com (Apple Secure Mail Relay) with SMTP id 17.13.05744.1B590995; Sun, 13 Aug 2017 11:08:49 -0700 (PDT) X-AuditID: 11ab0219-8e5ff70000001670-84-599095b1529c Received: from ma1-mmpp-sz11.apple.com (ma1-mmpp-sz11.apple.com [17.171.128.33]) by relay23.apple.com (Apple SCV relay) with SMTP id 15.F8.07952.1B590995; Sun, 13 Aug 2017 11:08:49 -0700 (PDT) MIME-version: 1.0 Received: from [17.234.211.74] by ma1-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.1.2.20170621 64bit (built Jun 21 2017)) with ESMTPSA id <0OUM00MUYYEMLE90@ma1-mmpp-sz11.apple.com>; Sun, 13 Aug 2017 11:08:49 -0700 (PDT) Sender: afish@apple.com From: Andrew Fish Message-id: Date: Sun, 13 Aug 2017 11:08:44 -0700 In-reply-to: Cc: Rod Smith , edk2-devel@lists.01.org To: Rafael Machado References: <42CE0497-A269-4D40-9E65-31A3CE27F197@apple.com> <3b578f09-8c29-4168-2524-49c8a2d5e210@rodsbooks.com> X-Mailer: Apple Mail (2.3273) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrALMWRmVeSWpSXmKPExsUiuLohQ3fj1AmRBl8+GFvsOXSU2WLnyxns FtOeL2NyYPbYOesuu0f37H8sHj+e72YOYI7isklJzcksSy3St0vgyrj24zB7wYTIip2zXrI2 MJ717mLk5JAQMJHYe3g2WxcjF4eQwHomid+dN9hgEhNuTmWESBxilNgw9QQrSIJXQFDix+R7 LCA2s0CYRNv9aSwQRV8ZJZ7fu88MkhAWEJd4d2YTmM0moCyxYv4HdohmG4l3L/ugahwlOk4d A4uzCKhKXJ+zlgnE5hQIlvh0cxorxAJ7ic4Lu8AuEhEwk9g7awI7xLJmJolbzx+xQJwqK3Fr 9iVmkISEwBI2iZ+PJ7NNYBSaheTaWUiuncXIAWSrS0yZkgsR1pZ48u4CK4StJrHw9yImZPEF jGyrGIVzEzNzdDPzjEz1EgsKclL1kvNzNzGCo4RJcgfj19eGhxgFOBiVeHhPZE+IFGJNLCuu zD3EKM3BoiTOG2PbFykkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qB0ZWt48sFmetf3Xa8EuWr DLscuHIeX+9VzaX8B5VmV68SO/FR9PbJ5puPdlTmP5sxMUp4Q/dGhnVZye16IgxPQr5mHOv8 M/3R8QuJHPJLZq78UR746dvnpMMC635caLJIeVwf+j1gf50OZ7FyTZt0snYGXwvfkRcrml+b fp2kdrSkNqbD49iHB0osxRmJhlrMRcWJABkum9JzAgAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMLMWRmVeSWpSXmKPExsUiuLpBUXfj1AmRBjtuaVvsOXSU2WLnyxns FtOeL2NyYPbYOesuu0f37H8sHj+e72YOYI7isklJzcksSy3St0vgyrj24zB7wYTIip2zXrI2 MJ717mLk5JAQMJGYcHMqYxcjF4eQwCFGiQ1TT7CCJHgFBCV+TL7HAmIzC4RJtN2fxgJR9JVR 4vm9+8wgCWEBcYl3ZzaB2WwCyhIr5n9gh2i2kXj3sg+qxlGi49QxsDiLgKrE9TlrmUBsToFg iU83p7FCLLCX6Lywiw3EFhEwk9g7awI7xLJmJolbzx+xQJwqK3Fr9iXmCYz8s5AcOAvJgbMY OYBsdYkpU3IhwtoST95dYIWw1SQW/l7EhCy+gJFtFaNgUWpOYqWRsV5iQUFOql5yfu4mRkhQ Z+xgvH7T7BCjAAejEg+vQUB/pBBrYllxZS4wmDiYlUR4Xd0nRArxpiRWVqUW5ccXleakFh9i lOZgURLn/dHRHSkkkJ5YkpqdmlqQWgSTZeLglGpgzHjT/miKmMmCKfLWHhMV+n8bKxrte7Dj nMHTA690osqZlz2r6Ixunb2Ty27KNY/illn908/GfygzENKcKCn1VUFRiL0l4pWo//2e6mfO F2wlSz7/Wz+9RH7BJRFhhd+uCX4PWAuq9VvzHPQ3CJbz5jMz9Zp9P2P37E74x/uBDq9rplgx sbAosRRnJBpqMRcVJwIA6GNxwGYCAAA= X-Content-Filtered-By: Mailman/MimeDel 2.1.22 Subject: Re: What Bios data is sent to the Bootloader/OS ? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Aug 2017 18:06:29 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Aug 13, 2017, at 6:07 AM, Rafael Machado = wrote: >=20 > Thanks a lot Andrew and Rod. Your comments clarified a lot. >=20 > Just onde last question. > In case of int15/e820 and uefi getMemoryMap. Do you know If this > information os used by the bootloaders? Yes it is, this is how the OS discovers the memory map.=20 > And do you know the format on these calls outputs? (For the = getMemoryMap > the uefi Spec os clear, but didn't find anything about e820). >=20 The modern version of 0xE820 is documented in the ACPI Spec owned by = your friendly UEFI Forum. ACPI Spec is here: = http://www.uefi.org/specifications .=20= There are some other specs from the 1990's that may be useful for legacy = BIOS. Plug and Play BIOS Specification from 1994, and BIOS Boot = Specification from 1996. For older stuff most people use Ralf Brown's = interrupt list. You kind find all this old BIOS stuff searching the = internwebs.=20 Thanks, Andrew Fish > Thanks and Regards > Rafael Machado >=20 > Em s=C3=A1b, 12 de ago de 2017 00:23, Rod Smith = > escreveu: >=20 >> On Aug 11, 2017, at 6:00 AM, Rafael Machado >> wrote: >>>>=20 >>>> Hi everyone >>>>=20 >>>> I have a question that probably some guys here can help. >>>> The scenario I have, is that I need to create a OS image that must = be >> able >>>> to boot at a UEFI system (with no csm module), and at a legacy bios >> system. >>>> My fist thought is that this is not possible. >>=20 >> If I understand you correctly, it most definitely IS possible. Most >> major Linux distributions provide installation media that can boot in >> either BIOS/CSM/legacy mode or in EFI/UEFI mode. Replicating what = those >> media do might not be the best way to go, though, since they are also >> typically designed to boot when written to optical media or when = written >> to USB flash drives. To do this, they use a sort of "Frankenstein's >> Monster" disk format, so unless you need this cross-media = compatibility, >> too, using the tools and procedures used to create these installation >> media would be overkill and would create something that's overly >> complex. These media do illustrate the practicality of what you're >> suggesting -- or at least, what I *BELIEVE* you're suggesting. If = I've >> misinterpreted, please clarify your needs. >>=20 >>>> The OS in this case is Linux, and the bootloader is Grub or = Syslinux. >>=20 >> A single GRUB (or SYSLINUX) binary will not do the job; however, = there >> are both BIOS and EFI builds of both GRUB and SYSLINUX. The details = of >> what you'd do would depend on the boot medium (hard disk, USB flash >> drive, optical disc, etc.); however, broadly speaking you need to = write >> both BIOS-mode and EFI-mode versions of your chosen boot loader to = the >> boot medium, with suitable configuration files in appropriate = locations. >>=20 >> Both GRUB and SYSLINUX are boot loaders that can load a Linux kernel >> into memory. The Linux kernel, in turn, does not need to be built for >> either BIOS or EFI environments; the same kernel binary will work in >> either environment. (One partial exception is that there's a feature >> known as the EFI stub loader that turns the Linux kernel into its own >> EFI boot loader. If you wanted to use this feature, it would = obviously >> need to be compiled into the kernel. GRUB does not require this = feature, >> though, and its presence will not interfere with the kernel being = booted >> on a BIOS-based computer. Thus, you probably don't need to worry = about >> it for your purposes. I mention it simply so you don't think it's an >> issue if you read something about it elsewhere.) >>=20 >> -- >> Rod Smith >> rodsmith@rodsbooks.com >> http://www.rodsbooks.com >> _______________________________________________ >> edk2-devel mailing list >> edk2-devel@lists.01.org >> https://lists.01.org/mailman/listinfo/edk2-devel >>=20 > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel