From: Adrian Bunk <bunk@stusta.de>
To: dwmw2@infradead.org
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [RFC: 2.6 patch] Kconfig help: MTD_JEDECPROBE already supports Intel chips
Date: Wed, 25 Jan 2006 00:50:38 +0100 [thread overview]
Message-ID: <20060124235038.GL3590@stusta.de> (raw)
Unless I'm misunderstanding the code in jedec_probe.c, Intel chips are
already supported.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
drivers/mtd/chips/Kconfig | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--- linux-2.6.16-rc1-mm2-full/drivers/mtd/chips/Kconfig.old 2006-01-25 00:42:51.000000000 +0100
+++ linux-2.6.16-rc1-mm2-full/drivers/mtd/chips/Kconfig 2006-01-25 00:43:20.000000000 +0100
@@ -19,21 +19,20 @@
config MTD_JEDECPROBE
tristate "Detect non-CFI AMD/JEDEC-compatible flash chips"
depends on MTD
select MTD_GEN_PROBE
help
This option enables JEDEC-style probing of flash chips which are not
compatible with the Common Flash Interface, but will use the common
CFI-targetted flash drivers for any chips which are identified which
are in fact compatible in all but the probe method. This actually
- covers most AMD/Fujitsu-compatible chips, and will shortly cover also
- non-CFI Intel chips (that code is in MTD CVS and should shortly be sent
- for inclusion in Linus' tree)
+ covers most AMD/Fujitsu-compatible chips and also non-CFI
+ Intel chips.
config MTD_GEN_PROBE
tristate
select OBSOLETE_INTERMODULE
config MTD_CFI_ADV_OPTIONS
bool "Flash chip driver advanced configuration options"
depends on MTD_GEN_PROBE
help
next reply other threads:[~2006-01-24 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 23:50 Adrian Bunk [this message]
2006-01-25 0:47 ` [RFC: 2.6 patch] Kconfig help: MTD_JEDECPROBE already supports Intel chips 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=20060124235038.GL3590@stusta.de \
--to=bunk@stusta.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.