The nbiloader.S already does this job. The etherboot/netboot stuff also
only can load not below 0x10000 and so the loader includes a routine,
copy
the diskless code down to 0x8200.
But you have to check the protocol of the loading itself. nbiloader.S
uses
the netboot protocol used by etherboot and netboot stuff. BOOTP/TFTP is
not all
of the downloading. Also other points are important:
* where is the image loaded
* can it be loaded at once or in blocks
* which address is called (entry point of execution)
:
and so on.
If (only if so) the loader expects an image of one block, loaded at
0x10000 and
with an entry point of 0x10000 then you have a chance by changing the
nbiloader.S
file (removing the first 32bytes of the data table and set there a jump
to the
address offset 32 bytes. Then it could be possible to load the `nbgrub'
file.
But of course this is a `hack' (trial version).
With friendly regards
Christoph Plattner
Florian Weimer wrote:
>
> I've got a NIC (3com 3c905c TX-M) which supports BOOTP and can load
> images up to a certain size (~450 KB) via TFTP. Unfortunately, the
> image is stored at address 0x10000 and onwards, so I couldn't any of
> the existing boot loaders, and couldn't load the 'diskless' image
> directly. In order to solve this problem, I've written a small loader
> which copies the 'diskless' image to adress 0x8200 regardless of its
> initial location.
>
> If you're interested, I'll clean up the code and you can have it.
>
> _______________________________________________
> Bug-grub mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/bug-grub
--
-------------------------------------------------------------------------
private: [EMAIL PROTECTED]
company: [EMAIL PROTECTED]
_______________________________________________
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub