Re: boot from diskonchip millenium

From: Glen <mtd@empireenterprises.com>
To: Ilguiz Latypov <ilatypov@superbt.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: boot from diskonchip millenium
Date: 05 Aug 2002 19:20:36 -0400	[thread overview]
Message-ID: <1028589640.12920.177.camel@glen> (raw)
In-Reply-To: <Pine.LNX.4.44.0208051313320.6631-100000@server.superbt.com>

Well, I've gotten a bit farther.  
Since I would prefer grub, we'll go that route.  

For description, we'll say I have the mtd-source in /mtd and grub in
/grub-0.92.

First, I compiled grub with --enable-diskonchip-mil, --enable-ext2fs,
and --enable-vfat

# cp /grub-0.92/stage2/pre_stage2 /mtd/grub
# /mtd/util/doc_loadbios /dev/mtd/0 /mtd/grub/grub_firmware  

This didn't seem to present any results, as the bios didn't recognize a
bootloader at all.  

Then I tried running doc_loadbios with the grub_firmware generated from
within /grub-0.92/stage1.  

Now the bios recognizes and runs the boot loader, but it can't seem to
read my diskonchip filesystem.  

I've been loosely following the directions at:
http://lists.infradead.org/pipermail/linux-mtd/2001-October/003475.html

I'm a bit confused.  
What's the difference between the grub_firmware generated by grub and
grub_firmware generated by mtd?  

-g

First, I tried loading the grub_firmware that was generated from <mtd
source>/grub.  
On Mon, 2002-08-05 at 13:26, Ilguiz Latypov wrote:
> 
> On 5 Aug 2002, Glen wrote:
> 
> > The available grub patches seem to do absolutely nothing useful,
> 
> Interesting.  Are there any messages on screen during the system boot?  
> 
> Are there any errors in compiling and setting up the bootloader as
> explained in README_DiskOnChip?  The latter file can be seen only after
> applying the patch, sorry.
> 
> Have you tried the --enable-diskonchip-biosnetboot configuration parameter
> and toggled the BIOS network boot option?
> 
> > the only lilo references I can find assume you are using msys's
> > software.
> 
> One has to implement a simple BIOS INT 13h interface. I guess you can
> re-use the GRUB MTD firmware open source code including its
> bdev_diskonchip.c NFTL driver.
> 
> Once this is done, you would erase all /dev/mtd0 blocks preceding the NFTL
> layer and run lilo against /dev/mtd0 so that it can install itself and the
> list of filesystem block numbers relative to device /dev/nftla.  These
> numbers are persistent.  This is unlike to locations of flash erase blocks
> abstracted by the NFTL layer.
> 
> Ilguiz
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 