Christoph Plattner <[EMAIL PROTECTED]> writes:
> Now, my 'patched' GRUB detects, whether it was booted
> by netboot or 'normal' by disk.
Please send a patch to the list. I want to see what you have done
so I can do it similarly in my PXE hacks (no need to do things
very differently if we can avoid it).
I'm thinking of adding code to the netboot/ directory and make a
network card definition that uses the PXE's built-in functions,
if available. They are somewhat different than the already available
function, in particular when receiving data, but it should be doable.
It's also possible to hook PXE into the TFTP code and use PXE's
predefined TFTP routines, but I figured that it would make more
sense to hook into the lower level network drivers so that other
remote filesystems have a chance to work if they would ever be
implemented.
Is there a limit on the size of pre_grub2? It's increasing towards
64k.
I also need some help with GAS; I'm unfamiliar with the syntax of
far calls and other things. In ES:DI is a structure called SEGOFF16
containing the segment and offset of a function in memory. Currently
I use this code to call it (PXE code can unfortunately only be called
from 16 bit real mode);
mov %es:(%di), ABS(offset)
mov %es:2(%di), ABS(segment)
.byte 0x9a
segment: .word 0
offset: .word 0
Is this the right way to do it?
