From: Thomas Gleixner <tglx@linutronix.de>
To: Ed Berube <eberube@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD Driver problem/question with 384MB MD2202-D384.
Date: Tue, 02 Nov 2004 10:46:40 +0100 [thread overview]
Message-ID: <1099388800.3337.68.camel@thomas> (raw)
In-Reply-To: <a084b59f04110114152b341fea@mail.gmail.com>
On Mon, 2004-11-01 at 17:15 -0500, Ed Berube wrote:
> I have to ask is the MD2202-D384 supported by MTD? Is there a work
> around to get this DOC to work with MTD. Or am I missing something
> and this should all be working.
Which DoC driver are you using ?
drivers/mtd/devices/doc...
or
drivers/mtd/nand/diskonchip.c
The latter is the one we support. Can you try it ?
The DoC firmware version is not really relevant for the first step. The
first step is to make sure, that the chip driver itself recognizes the
devices correctly. The firmware version is relevant for the (I)NFTL
drivers, which can only work when the device can be handled by the low
level driver.
tglx
prev parent reply other threads:[~2004-11-02 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 22:15 MTD Driver problem/question with 384MB MD2202-D384 Ed Berube
2004-11-02 9:46 ` Thomas Gleixner [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=1099388800.3337.68.camel@thomas \
--to=tglx@linutronix.de \
--cc=eberube@gmail.com \
--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