From: David Woodhouse <dwmw2@infradead.org>
To: David Updegraff <dave@cray.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Large block NAND
Date: Mon, 22 Mar 2004 15:57:49 +0000 [thread overview]
Message-ID: <1079971069.16509.125.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <405F0840.3030503@cray.com>
On Mon, 2004-03-22 at 09:37 -0600, David Updegraff wrote:
> I am looking at the existing 'drivers' in drivers/mtd/nand; am a bit
> baffled; need help understanding approach.
>
> The files (spia, autcpu12..) are apparently drivers for particular NAND
> chips,
They're not. They're drivers for particular ways wiring up a NAND chip.
The code in nand.c handles all currently-supported (i.e 8-bit, 256- or
512-byte per page) NAND chips, and uses access functions provided by the
board-specific 'wiring' driver to waggle the control lines, etc.
> but it appears to me that they all call nand_scan in nand.c,
> which in turn just looks for ids enumerated in nand_ids.h. Does this
> not make it necessary to hand-tune which driver you want to compile with
> nand.c instead of having the drivers themselves control with nand chip
> they know how to drive -- based on what ID one finds? Or is the
> thinking that the quirks of each little embedded gadget to too wierd
> anyway; so must hand-tune?
>
> -dbu.
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
--
dwmw2
next prev parent reply other threads:[~2004-03-22 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 12:14 Large block NAND llandre
2004-03-18 13:11 ` Thomas Gleixner
2004-03-18 14:16 ` David Woodhouse
2004-03-18 14:26 ` Thomas Gleixner
2004-03-18 14:52 ` llandre
2004-03-18 14:57 ` Thomas Gleixner
2004-03-18 14:59 ` David Woodhouse
2004-03-22 15:37 ` David Updegraff
2004-03-22 15:57 ` David Woodhouse [this message]
2004-03-18 18:32 ` David Updegraff
2004-03-19 8:21 ` llandre
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=1079971069.16509.125.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=dave@cray.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