[syslinux] Question about syslinux EFI alpha version

Jeffrey Hutzelman jhutz at cmu.edu
Thu May 9 08:23:35 PDT 2013

On Thu, 2013-05-09 at 15:48 +0100, Matt Fleming wrote:
> On Thu, 09 May, at 07:03:21AM, H. Peter Anvin wrote:
> > On 05/09/2013 05:51 AM, Matt Fleming wrote:
> > > 
> > > Yeah, that could be a good idea. It would save us from having to invent
> > > a scheme to ensure we load the correct ldlinux.c32 depending on whether
> > > we're booting 32-bit or 64-bit.
> > > 
> > 
> > The question is if we don't need that anyway for modules... after all,
> > every module, not just ldlinux.c32, is affected here.
> > 
> > Additionally, I do believe BIOS and EFI have different .c32 modules, no?
> Yes, the .c32 modules for BIOS, efi32 and efi64 are all different.
> Notably the BIOS and efi32 modules are compiled with different CFLAGS
> (the immediate thing that comes to mind is -mno-red-zone).
> > Unless they are in separate trees, I think we'll need separate names.
> Once ldlinux.c32 is loaded it can parse the PATH directive in a config
> file, which can be used to point to separate trees. Of course, you need
> to be able to load *different* config files for BIOS, efi32 and efi64,
> so that moves the problem rather than solving it.

It seems like you could solve this by introducing variable expansion
along the lines of what ld.so does with its search paths.  So, you
interpret $PLATFORM as bios, efi32, or efi64, as appropriate, and then
set the default PATH to something like syslinux/$PLATFORM:syslinux

-- Jeff

More information about the Syslinux mailing list