Re: Problems with DOC 2000 on 2.4.21

[Selwyn Tang <selwyn@hectrix.com>]

I used the MAKEDEV script provided by the mtd from cvs to create the 
various device files (/dev/mtd*, /dev/nftl*, etc.) and now I can access 
my DOC2000.

But concerning the unshadowing of the DIP socket, I do have a problem. 
My Intel D845BG borad seems to be unable to detect my DOC development 
board (M-Sys' PCI EVB), and even dinfo.exe in DOS cannot detect it. But 
in Linux, I can still access it using M-Sys's Linux driver. I wonder if 
it is the shadowing problem you are talking about. Right now, I am using 
a ASUS board smoothly with DOC.

Selwyn

Roger wrote:
> On both of my 440BX boards, Intel incorporated a shadow feature which
> shadows the mtd devices (bios chip/DIP socket) from the normal mtd
> drivers/modules.
> 
> I have to utilize the openbios/devbios module/code to unshadow the 440BX
> DIP socket.
> 
> There are many other chipsets supported for unshadowing in that code.  I
> believe the code only needs to be implemented into mtd somehow.
> 
> But basically, I get nothing found in dmesg when loading the DOC modules
> and nothing showing in /proc/mtd* -- but mtdchar does show some info in
> the /proc/mtd* files.
> 
> After unshadowing the 440BX DIP socket (using openbios/devbios -- i
> hacked module to leave the DIP socket unshadowed after unloading;-), and
> then loading the mtd/doc modules,  I get 'found DOC ...' in dmesg and I
> get good info in the /proc/mtd* files.