Re: Problems with using doc2001 module

[roger <rogerxxmaillist@san.rr.com>]

ok. just for kicks. i booted into DOS using M-SYS's tffs_5.1.4_DOS_TOOLS
and dinfo and dformat refused to find the DiskonChip even after
specifing it's address of 0xfff00000.

something isn't right here.  it's obviously something with the code.  I
also get the same results on a duplicate 440BX motherboard.

arrrghh.

On Sun, 2003-06-08 at 17:23, roger wrote:
> For the past couple of days and using every available option with
> docprobe (kernel compile time options), I have not been able to get the
> several DiskOnChips-2001 recognized by kernel 2.4.20.
> 
> by a fluke accident, i've gotten the DOC recognized.
> 
> I'm on a 2x750P3 SMP Tyan Tiger 1832dl and induced a "kernel oops" on
> cpu1 by trying to insmod ./bios.o
> (http://www.openbios.info/download/index.html
> devbios-0.3.2.tar.gz).
> 
> the docprobe.o is compiled with "Physical Address = 0" and no other
> options for docprobe.o.  ... using doc2001.o
> 
> i've attached dmesg output below of the oops condition  when trying to
> insmod bios.o and then after the kernel-oops occurred, modprobed
> mtdcore, mtdchar,dos2001,dosprobe doc_config_location=0xfff00000. 
> (unknown if the doc_config_location is needed...have yet to try without
> as i've only duplicated 3 times.)
> 
> (i've been advised that there might be a "hidden write enable" problem -
> i.e. there is a special GPIO line used to control write enable in
> addition to the normal mechanism.)
-- 

Roger
http://www.eskimo.com/~roger/index.html