Skip to content
Discussion options

You must be logged in to vote

I enabled debug logging, and that uncovered a further error

Support(): UNDI3.1 found on handle 23EF5CE98
!PXE structure is not paragraph aligned.

I had to align my SW Undi struct to 16 bytes, and the driver was recognized as a PXE device

PXE_SW_UNDI __attribute__((aligned(16))) definition { ... }

This is noted in the spec, but not sure why it wasn't an issue for OVMF/X86

"!PXE structure signature. This field is used to locate an UNDI hardware or software interface in system memory (or I/O) space. ‘!’ is in the first (lowest address) byte, ‘P’ is in the second byte, ‘X’ in the third and ‘E’ in the last. This field must be aligned on a 16-byte boundary (the last address byte must be zero)…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by ddaskala
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant