[syslinux] move firmware-specific code into a directory

[Patrick Masotta]

>>>    
 FWIW, I would rather see efforts invested on making c32 modules usable 
 under all supported firmware architectures, instead of changing the 
 whole directory tree structure. Adding some kind of conditional(s) in 
 Makefiles seems appropriate.
 
 BTW, if a c32 module would be built for BIOS only and then someone 
 patches the code so to make it usable under UEFI also, then the change 
 in Makefiles should be simple. The code in Syslinux already requires 
 skills, knowledge, and a certain learning curve; so lets not 
 over-complicate matters.
 
 Indeed, producing c32 modules under the efi32 and efi64 subdirectories 
 while they are not really usable under such systems is not nice nor 
 user-friendly, but lets not pretend it is the worse / most important 
 issue in the current Syslinux code.
 
 If it can be done, without making it more difficult for contributors / 
 coders (especially for potential new ones), great. If it is going to 
 make things more difficult for new developers to learn how the code 
 works (with the intention of contributing), or if it happens to require 
 too much focus / investments from the very few contributors that 
 Syslinux currently has...
 
 As I have said in past emails (among other places), current regressions 
 and essential features are still the main issue for Syslinux these days
 
 (or rather, years). In fact, let me emphasize that statement: it is 
 _the_ issue.
 
 @Patrick (and whoever might be interested):
 I have posted the link several times (even recently):
 
 "[PATCH 0/1] EFI access from Com32 modules"
  http://www.syslinux.org/archives/2015-March/023320.html
 
 
 (and please, remember the "8.3 file name format"; TIA)

 Regards,
 Ady.
  
<<<

I agree; 
thanks for the link.

Best,
Patrick