[ipxe-devel] EFI_SIMPLE_FILESYSTEM_PROTOCOL commit breaks snponly.efi

Jarrod Johnson jarrod.b.johnson at gmail.com
Thu Apr 11 13:26:27 UTC 2013


The only thing I'm smart enough to do is go back to
db014f3c23be19e11964d48f2bcb25b54a9bf722.  I tried doing various things to
make the snponly 'net0' work despite not being in the PCI device list, but
the quick things I thought to try didn't work and I don't have the time to
do what I think would be a correct answer.


I'm presuming either something got skipped and snponly 'net0' device should
have been subjected to magic from efi_pci.c or else that efi_snp.c adds a
case to recognize the particular 'net0' that is currently constructed as-is
(I'm guessing it must grab it based on loaded image protocol, but I haven't
looked that hard).

As an aside, what's the correct efi binary name to build/approach to have
an ipxe binary that can use any of the snp devices available, not just the
snp device as discovered through loaded image protocol?  The use case being
arbitrary SNP drivers and ipxe starting from a non-network context such as
vfat partition on local flash.  My next step will be examining the
viability of ipxe reading certificate data and scripts from efi filesystem,
so if there are any particular things to know about there, that would be
interesting too.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20130411/dee1802e/attachment.htm>


More information about the ipxe-devel mailing list