lilo patch

lilo patch

[Ian Thompson]

Forgive me if I'm covering familiar territory.

What was the purpose of the lilo-ebda.patch?

I have a development setup with a hard-drive and a DiskOnChip
and I was looking for a lilo patch that would allow me to boot
the hard-drive with a configured DiskOnChip in place but this 
didn't do it.

I have a 32M DOC2000 @ 0xd000:0000 

Other things I have noticed, that I, with my limited DOC knowledge,
can't explain...

A configured 32M Millenium will allow lilo to boot the hard-drive but
a configured 16M Millenium wiil not.

64M DOC2000s don't seem to work with M-Systems binary driver.

Has anyone any experience with 64M DOC2000s? We have several and 
approx. 25% won't format to full capacity with the M-Systems utilities.

Ian T.


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: lilo patch

[Miguel Freitas]

	Hi Ian,

> 64M DOC2000s don't seem to work with M-Systems binary driver.
> 
> Has anyone any experience with 64M DOC2000s? We have several and
> approx. 25% won't format to full capacity with the M-Systems
> utilities.

   The newest DiskOnChip driver in CVS (our driver, not the M-
Systems) should be aware of 64M nand chips. Unfortunatly, NFTL 
may not work with non 8kbytes erase blocks (64M have 16kbytes 
blocks), but I really don't know. I'm a little busy, and I haven't 
checked nftl code yet....
   I would be grateful if you could try the latest CVS code and report 
and success/failures. There is a utility (nandtest) where you can test 
raw access to nand chips without nftl.
   I think there are new drivers on the M-Systems site to handle 64M 
DOC2000s, but probably not for linux.


Regards,

Miguel Freitas
Center for Telecommunications Studies
CATHOLIC UNIVERSITY - BRASIL
e-mail: miguel@cetuc.puc-rio.br
phone/fax#:+55-21-540-8854


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org