[syslinux] move firmware-specific code into a directory

Geert Stappers stappers at stappers.nl
Sun Sep 20 01:18:37 PDT 2015


On Sun, Sep 20, 2015 at 06:32:48AM +0200, Celelibi via Syslinux wrote:
> 2015-09-20 0:04 UTC+02:00, Gene Cumm via Syslinux <syslinux op zytor.com>:
> > On Sat, Sep 19, 2015 at 4:32 PM, BALATON Zoltan <balaton op eik.bme.hu> wrote:
> >> On Fri, 18 Sep 2015, Gene Cumm via Syslinux wrote:
> >>>
> >>> No.  pxechn.c32 is BIOS only for now.
> >>
> >>
> >> Why are there binaries of non-working components in the distribution?
> >> This is confusing for us not knowing syslinux so well. Is there a
> >> list of files somewhere that are known not to work despite being
> >> distributed?
> >> Is there a way to not include these binaries to avoid confusion?
> >
> > No one has spent the time to prevent some of the COM32s from being
> > built on EFI architectures by working on the Makefiles.
> 
> This is related to bug #37.
> http://bugzilla.syslinux.org/show_bug.cgi?id=37
> 
> Actually, I think this raises a more general issue about the source
> code organization. Most of the code of syslinux has been developped in
> a time where only BIOSes were supported. And now, there is no real
> separation between generic code and BIOS-only code (while UEFI code
> has its own directory). So some modules compiles for UEFI but are
> non-functional.
> 
> I wonder if anyone has a knowledge of the source code general enough
> to clarify this and move the firmware-specific code into a directory
> arch/{bios,efi}. I personnally mostly know about the efi part.

I like the proposal of arch/{bios,efi}.
And because Free software is mostly do-o-cracy, please do.


> Anyway this would be a large change conflicting with most pending
> patches.

So be it.
I mean: Choose high level design improvement above outstanding patches.
(and I think we, the Syslinux project, have a backlog of patches
due fear of changing "too much" (yes, I say: What has to be done
has to be done ))


> Not sure it's gonna happen anytime soon.

Which makes it only harder.

There should no fear for breaking what is allready broken.






Groeten
Geert Stappers
-- 
Leven en laten leven
------------- volgend deel ------------
Een niet-tekst bijlage is gescrubt...
Naam: signature.asc
Type: application/pgp-signature
Grootte: 836 bytes
Omschrijving: Digital signature
URL : <http://www.zytor.com/pipermail/syslinux/attachments/20150920/4a95aead/attachment.sig>


More information about the Syslinux mailing list