From: Roger <rogerxxmaillist@speakeasy.net>
To: Selwyn Tang <selwyn@hectrix.com>, linux-mtd@lists.infradead.org
Subject: Re: Problems with DOC 2000 on 2.4.21
Date: 06 Aug 2003 00:55:41 -0700 [thread overview]
Message-ID: <1060156541.4912.9.camel@localhost3.localdomain> (raw)
In-Reply-To: <3F3058C8.2060404@hectrix.com>
On Tue, 2003-08-05 at 18:24, Selwyn Tang wrote:
> 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.
yup. the mtd device will remain invisible until unshadowed. even the
dos utilites fail to see the mtd device (or bios DIP socket with DOC
inserted).
funny. i never tried the msys binary drivers that they provide -- i
believe that i was concerned i was using something out-dated and/or
wouldn't work with my kernel versioning. maybe i should try it since
you've said you have had success with it. odd.
>
> 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.
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
--
Roger
http://www.eskimo.com/~roger/index.html
prev parent reply other threads:[~2003-08-06 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 10:08 Problems with DOC 2000 on 2.4.21 Selwyn Tang
2003-08-04 10:23 ` Roger
[not found] ` <3F2E38FE.8030800@hectrix.com>
2003-08-05 14:32 ` Roger
2003-08-06 1:24 ` Selwyn Tang
2003-08-06 7:55 ` Roger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1060156541.4912.9.camel@localhost3.localdomain \
--to=rogerxxmaillist@speakeasy.net \
--cc=linux-mtd@lists.infradead.org \
--cc=selwyn@hectrix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox