iPXE discussion forum

Hi,

Pardon me if I am wrong here, but from my understanding of UEFI, interrupt services are not supported there. Also from the ipxe code I see COM32 image format using interrupts.

Don't read further if the above was wrong!!

So my question is
1. Is bin-i386-efi a valid target - because again I think UEFI supports only 64 bit systems ?
2. If bin-i386-efi was valid, then it includes a lot of arch/i386/interface/syslinux code (COMBOOT and COM32), which it should not support (because of interrupts) ?

Thanks for the help!

(2013-07-22 02:11)Game Wrote: [ -> ]1. Is bin-i386-efi a valid target - because again I think UEFI supports only 64 bit systems ?

Yes, it is. There are 32-bit UEFI systems in existence, although they are rare.

Quote: 2. If bin-i386-efi was valid, then it includes a lot of arch/i386/interface/syslinux code (COMBOOT and COM32), which it should not support (because of interrupts) ?

The general build policy for iPXE is to compile as many files as possible in each build. This helps to avoid code rot: if a change is introduced which prevents the EFI code from compiling, then it will be noticed immediately since the EFI code is compiled even when building a standard PCBIOS target.

Michael

Hi Michael,
Thanks for the reply.

But UEFI still would not support COM32? And so should not be linked?

Thanks

(2013-07-22 15:10)Game Wrote: [ -> ]But UEFI still would not support COM32? And so should not be linked?

Correct; UEFI will not support COM32.

Michael

Game: And yes, even though everything is built on each compile, not everything is linked in all the time. arch/i386/* is not linked into any UEFI build, to my knowledge.