Re: Problems with DOC 2000 on 2.4.21

[Roger <rogerxxmaillist@speakeasy.net>]

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. 


On Mon, 2003-08-04 at 03:44, Selwyn Tang wrote:
> Dear Roger,
> 
> Roger wrote:
> > I usually find after loading the mtd doc200x modules, doing:
> > # modprobe mtdchar
> > will usually produce the /dev/mtd* devices.
> 
> When I compiled those MTD stuffs as modules, and after modprobe, I still 
> didn't get any /dev/mtd* devices. But when I compiled those as builtin, 
> I can cat /proc/mtd and get "mtd0:..." but still no /dev/mtd*
> 
> Do you know why?
> 
> Selwyn
-- 

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