public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Chris Ellec <cellec@celerity.net>
To: linux-mtd@lists.infradead.org
Subject: INFTL problems
Date: Tue, 28 Oct 2003 09:32:00 -0800	[thread overview]
Message-ID: <3F9EA810.6010905@celerity.net> (raw)

Hello,

I have a WinSystems devel board with a DOC on it. Dinfo from MSystems 
reports a DOC 2000 at address D800 with 256 MB and an INFTL format.

I apllied the latest CVS patches to 2.4.22, but I can't seem to detect 
the chip.

I followed the doc in CVS and compiled as modules with the following 
options:

-------------------  from .config  ---------------------------
#
# Memory Technology Devices (MTD)
CONFIG_MTD=m
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=3
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLOCK=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m

# Self-contained MTD device drivers
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCPROBE_ADDRESS=0

#
# NAND Flash Device Drivers
CONFIG_MTD_NAND_IDS=m
------------- end of .config  ----------------------------

Then I do
# modprobe -a doc2000  inftl mtdchar mtdblock
# modprobe -a docprobe
/lib/modules/2.4.22/kernel/driver/mtd/devices/docprobe.o: init_module: 
Resource temporarily unavailable
insmod docprobe failed


in /var/log/messages I get:
INFL: inftlcore.c $Revision 1.14 inftlmount.c $Revision 1.12
No Recognized DiskOnChip found


Now what do I do ?

Chris.

             reply	other threads:[~2003-10-28 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-28 17:32 Chris Ellec [this message]
2003-10-28 21:34 ` INFTL problems Dave Dillow
2003-10-29 11:41   ` David Woodhouse
2003-11-05 10:27   ` David Woodhouse
2003-11-05 13:28   ` David Woodhouse
2003-11-05 17:23 ` David Woodhouse

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=3F9EA810.6010905@celerity.net \
    --to=cellec@celerity.net \
    --cc=linux-mtd@lists.infradead.org \
    /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