It is accurately reporting that it doesn't support flash on the UDB, as
it also says in the documentation.
I have hacked a version that can write the flash on a UDB. However, it is
not yet useful, as Milo won't actually work out of flash on the UDB (yet).
Some changes will need to be made to Milo to handle the complete cold-start
initialization of the UDB correctly.
This will probably result in the need for separate UDB and Noname
configurations for Milo, unless someone can recommend a good way to detect the
difference at runtime. I've though about using the presence of the Intel
82365 (?) ISA to PCMCIA interface, or the Microsoft Sound System, however both
of these could be plugged into an ISA slot on a Noname. I thought about trying
to detect whether the SROM code is from the UDB or the Noname, but as far as
I know the SROM code is *only* loaded into the Icache, so there is no way to
inspect it as data. Maybe I could look at the return address on the stack
when the SROM calls the loaded flash image; it might be different. Then again,
the SROM may just _jump_ to the image rather than calling it. I don't
actually have a Noname, so it will be difficult for me to develop autodetection
code of any sort.
Also, I need to add an option for Milo to allow setting the boot option on
the UDB, so that it will be possible to switch back to ARC or SRM. Note that
there is not room in the flash for ARC, SRM, and Milo, so you'll have to give
up one of them.
Anyhow, if I get Milo working from flash on the UDB (and I'm not promising
that I will have time to do it), I'll contribute the changes back to
Dave Rusling to merge into the standard Milo distribution.
In the mean time, it is recommended that you keep a very small DOS partition
on your hard disk (typically /dev/sda1 of one or two megabytes) from which
ARC can load linload and Milo. Some people actually dd a floppy image over
the partition (in which case it needs to be at least 1.44 MB). I made my
partition about 1 MB and mount it directly as a file system when I want to
update it.
Cheers,
Eric
-- To unsubscribe: send e-mail to axp-list-request@redhat.com with 'unsubscribe' as the subject. Do not send it to axp-list@redhat.com
Copyright © 1995-1997 Red Hat Software. Legal notices