Warner Losh writes:
| In message [EMAIL PROTECTED] Luigi Rizzo writes:
| : We'd also be able to load the kernel out of ROM :-)
| :
| : the whole issue is the size of the ROM isn't it ?
|
| Yes. I saw a few datasheets for embedded systems that have 2M or 4M
| of flash. Some of that is for the
In message [EMAIL PROTECTED] Doug Ambrisko writes:
: Is this bits or bytes. The Intel firmware hub can have 4 or 8 Mbits that
: comes with any Intel 8XX system so with gzip you could fit a bunch of
: stuff in a standard off the shelf motherboard. Also CMOS memory is
: increasing and that
+ put some conditional-compilation code in boot1.s
+ have a separate file, say bootrom.s, maybe in the same directory
as the existing boot1
+ pass the modified code to the etherboot people so they can include
in their source tree.
in all sincerity i'd love to have
In message [EMAIL PROTECTED] Luigi Rizzo writes:
: If we had it, we could just 'dd' the boot code and the kernel onto
: a compactflash and boot from it without having to worry about
: creating a filesystem.
We'd also be able to load the kernel out of ROM :-)
Warner
To Unsubscribe: send mail
In message [EMAIL PROTECTED] Luigi Rizzo writes:
: If we had it, we could just 'dd' the boot code and the kernel onto
: a compactflash and boot from it without having to worry about
: creating a filesystem.
We'd also be able to load the kernel out of ROM :-)
the whole issue is the size of
In message [EMAIL PROTECTED] Luigi Rizzo writes:
: We'd also be able to load the kernel out of ROM :-)
:
: the whole issue is the size of the ROM isn't it ?
Yes. I saw a few datasheets for embedded systems that have 2M or 4M
of flash. Some of that is for the BIOS, but part of it can be used
Luigi Rizzo wrote:
+ put some conditional-compilation code in boot1.s
+ have a separate file, say bootrom.s, maybe in the same directory
as the existing boot1
+ pass the modified code to the etherboot people so they can include
in their source tree.
in all
Luigi Rizzo wrote:
+ put some conditional-compilation code in boot1.s
+ have a separate file, say bootrom.s, maybe in the same directory
as the existing boot1
+ pass the modified code to the etherboot people so they can include
in their source tree.
in all
Luigi Rizzo wrote:
I have spent some time trying to put etherboot[1] code onto the
hard disk so that it can be selected using the FreeBSD boot
manager. I ended up doing it with a small amt of modifications
to the "boot1" code, for which a patch is attached.
Maybe it could be interesting
Luigi Rizzo wrote:
I have spent some time trying to put etherboot[1] code onto the
hard disk so that it can be selected using the FreeBSD boot
manager. I ended up doing it with a small amt of modifications
to the "boot1" code, for which a patch is attached.
Maybe it could be
Luigi Rizzo wrote:
Luigi Rizzo wrote:
I have spent some time trying to put etherboot[1] code onto the
hard disk so that it can be selected using the FreeBSD boot
manager. I ended up doing it with a small amt of modifications
to the "boot1" code, for which a patch is attached.
sorry if this is not the most appropriate forum to discuss this,
redirects appreciated.
I have spent some time trying to put etherboot[1] code onto the
hard disk so that it can be selected using the FreeBSD boot
manager. I ended up doing it with a small amt of modifications
to the "boot1"
12 matches
Mail list logo
