From: David Updegraff <dave@cray.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Large block NAND
Date: Mon, 22 Mar 2004 09:37:36 -0600 [thread overview]
Message-ID: <405F0840.3030503@cray.com> (raw)
In-Reply-To: <1079621971.16952.154.camel@hades.cambridge.redhat.com>
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, 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.
next prev parent reply other threads:[~2004-03-22 15:37 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 [this message]
2004-03-22 15:57 ` David Woodhouse
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=405F0840.3030503@cray.com \
--to=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