From: Larry Doolittle <ldoolitt@recycle.lbl.gov>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: problems with 28F320B still
Date: Tue, 25 Sep 2001 14:25:49 -0700 [thread overview]
Message-ID: <20010925142549.A22356@recycle.lbl.gov> (raw)
In-Reply-To: <24339.1001451631@redhat.com>; from David Woodhouse on Tue, Sep 25, 2001 at 10:00:31PM +0100
David -
> [the 28F320B3] is not a CFI chip. Why is cfi_probe claiming to
> recognise it? The CFI structure you quoted is obviously wrong.
I can't tell you why it was recognized, but the probe was
triggered by the line in drivers/mtd/maps/physmap.c :
mymtd = do_map_probe("cfi_probe", &physmap_map);
I added a coupla printk's, and find it entered cfi_probe_chip with
cfi->device_type==2. The line in the logfile
Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit mode
came from the first of two cfi_probe_chip_1() calls within cfi_probe_chip(),
which returned index == 0.
I'll happily apply patches and help debug, but I'm not terribly
familiar with this corner of the Linux kernel, so suggestions
and comments will be greatly appreciated.
- Larry
next prev parent reply other threads:[~2001-09-25 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 20:40 problems with 28F320B still Larry Doolittle
2001-09-25 21:00 ` David Woodhouse
2001-09-25 21:25 ` Larry Doolittle [this message]
2001-09-25 21:28 ` David Woodhouse
[not found] ` <20010925143742.A22632@recycle.lbl.gov>
[not found] ` <25445.1001454134@redhat.com>
[not found] ` <20010925150341.A22897@recycle.lbl.gov>
[not found] ` <26239.1001455701@redhat.com>
[not found] ` <20010925153929.A24347@recycle.lbl.gov>
[not found] ` <20010927163205.A4845@recycle.lbl.gov>
[not found] ` <24249.1001660788@redhat.com>
[not found] ` <20010928123452.A6016@recycle.lbl.gov>
2001-09-28 23:07 ` problems with 28F320B: resolved? Larry Doolittle
2001-09-26 19:38 ` problems with 28F320B still Larry Doolittle
2001-09-27 22:39 ` Larry Doolittle
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=20010925142549.A22356@recycle.lbl.gov \
--to=ldoolitt@recycle.lbl.gov \
--cc=dwmw2@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox