Displaying 4 results from an estimated 4 matches for "pxenv_undi_get_information".
2016 Feb 26
3
lpxelinux.0 with device that doesn't support Interrupts
...le using UNDI API.
but before that it will close and open the underlying device (which is ipxe), and hooking the device interrupt so it can start getting some packets.
What I'm experiencing is that if the underlying device doesn't support interrupts, i.e. the IntNumber that is returned in PXENV_UNDI_GET_INFORMATION is 0, then lpxelinux.0 will hook IRQ0 which is very bad behavior.
one good example of the faulty code is in undinet.c where we open a device, we hook the IRQ regardless if its 0 or not, while in the latest iPXE code this behavior was corrected and a check expression was added to avoid such bad beh...
2008 Mar 03
3
finding mac address while in menusystem (com32)
Hi
I have made myself a derivated menusystem based on the complex.c menu that cames with syslinux.
And now I need to read a file, search for my pxebooted netcards mac address, and write some changes back to the same file.
All the writing and reading I hopes will be of no trouble, but how can i find my own mac address? (and IP adress would be nice).
I have searched the list, but I really cannot
2016 Feb 26
2
lpxelinux.0 with device that doesn't support Interrupts
hi
does anyone know if there are some known issues with running lpxelinux.0 with device that doesn't support Interrupts? i.e. irq function is null...
2016 Mar 01
0
lpxelinux.0 with device that doesn't support Interrupts
...that it will close and open the underlying device (which
> is ipxe), and hooking the device interrupt so it can start getting
> some packets.
>
> What I'm experiencing is that if the underlying device doesn't
> support interrupts, i.e. the IntNumber that is returned in
> PXENV_UNDI_GET_INFORMATION is 0, then lpxelinux.0 will hook IRQ0
> which is very bad behavior.
>
> one good example of the faulty code is in undinet.c where we open a
> device, we hook the IRQ regardless if its 0 or not, while in the
> latest iPXE code this behavior was corrected and a check expression
> w...