DiskOnChip for PowerPC embedded system.
Brendan J Simon
Brendan.Simon at ctam.com.au
Tue Jan 4 17:06:06 EST 2000
David Woodhouse wrote:
> Brendan.Simon at ctam.com.au said:
> > 1) Do I need to reprogram the firmware on the DOC device or is the
> > Linux driver software all I need ?
> Some kind of firmware is required to get the machine booting off the
> DiskOnChip, but the normal firmware doesn't work very happily with LILO or
> grub. Apparently it works OK with syslinux though.
I'm using a PowerPC embedded system. There is no floppy and it is obviously
non-Intel. From what I know, lilo, grub and syslinux are Intel specific.
I can currently run a linux kernel out of a linear flash SIMM. If this kernel
has the DOC drivers compiled in then I should be able to use the DOC without
having to touch the firmware. Is this correct ?
I would have to write the low-end driver for the DOC I assume.
> I'd like to add code to grub to drive the DiskOnChip directly and replace the
> standard firmware. But I want to get the Linux drivers working first.
I thought they were working ?
Is it useable for a production system ?
What else needs to be done ?
I'm using kernel 2.2.5 at the moment. Is this OK ?
> > 2) Can I use the firmware/ROM space to put own bootloader code ? How
> > big is it ?
> 48K by default IIRC. You can use that as a first stage and load more though.
This could be handy :)
> > 3) Is there an FAQ for DOCs that aren't Intetl PC specific ?
> None of the stuff I've done so far is ia32-specific. The DiskOnChip Linux
> driver has been tested on Alpha, and although I don't have a big-endian box
> with an ISA slot I can fit the eval board in, I believe it should also work.
> Booting's a different problem - but I haven't addressed that yet.
I guess I could write some simple boot code that could read ext2 filesystem and
load the kernel into memory from the DOC, then boot the kernel. I'm not sure
how much work is involved in that though. M-Systems have on OS Adaption Kit
which has ANSI source for the TrueFFS, FAT FS, etc. This may be worth
considering but I imagine it might be expensive, but I guess there is no harm in
> The firmware is _only_ required for booting the kernel. In DOS, it also
> provides INT 13h (Disk BIOS) services to access the DiskOnChip as a normal
> DASD, but under Linux we don't need that because we drive the hardware
When you say the "firmware is _only_ required for booting the kernel", I take it
you mean only required when boot a kernel that is actually stored on the DOC
itself. Sorry if this sounds like a dumb question.
To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org
More information about the linux-mtd