On 25.04.2012 02:16, Richard Chan wrote: > 5. I have looked at the existing GRUB net+efinet stack. During my > simple testing I have to be unaable to trigger the code path where > grub populates the grub_net_structure from the UEFI PXE code. This > occurs in grub_efi_net_config_real() in > grub-core/net/drivers/efi/efinet.c. The information from EFI network is used only if efinet is embed in grub.efi. Otherwise you have to call net_bootp manually > When I do > grub> insmod efinet > grub> net_ls_cards That's not what is expected. Could you try debug where grub_efinet_findcards in efinet.c stopped? > grub> net_ls_addr > I cannot see any information from the PXE boot (i.e. I have booted > grub using UEFI PXE and I expected the efinet structures - at least > one of the cards - to be populated from PXE). > > Nevertheless, since the UEFI/PXE stack works independently of Grub, > would it be ok to bypass the whole grub/net/drivers infrastructure and > use UEFI directly, as what grub-legacy currently does? No. You basically say "code A has a bug, let's throw it away and write code B, which will have other bugs". Such approach is unmaintainable.
-- Regards Vladimir 'φ-coder/phcoder' Serbinenko
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
