From: Thayne Harbaugh <tharbaugh@lnxi.com>
To: Ben Dooks <ben-mtd@fluff.org>
Cc: ben@fluff.org, linux-mtd@lists.infradead.org, ch@hpl.hp.com
Subject: Re: jedec_probe problems with 16bit devices
Date: Tue, 07 Sep 2004 07:34:51 -0600 [thread overview]
Message-ID: <1094564091.20769.350.camel@tubarao> (raw)
In-Reply-To: <20040904173703.GA2100@fluff.org>
On Sat, 2004-09-04 at 18:37 +0100, Ben Dooks wrote:
> I have been trying to get an SST 39LF160 on an Simtec Electronics
> EB2410ITX (aka Bast). I have found some problems with jedec_probe
> with non-8bit devices.
> 1) A number of functions are masking out bits from the command
> addresses, but the cfi_send_gen_cmd() moves the addresses up
> depending on the chip type, so the masking is not needed.
Dave, can you comment on this? It seems like it was something that you
worked with - something about not probing at unaligned addresses?
> 2) the cfi_send_gen_cmd() is called with CFI_DEVICETYPE_X8
> instead of cfi->device_type, which causes the wrong accesses to
> be generated to the chip.
It seems like the CFI_DEVICETYPE_X8 was changed to cfi->device_type at
one point and it broke some 16-bit chips.
I think all of the CFI_DEVICETYPE_X8s were removed from jedec_probe.c
1.30, but then some were added back in at 1.36. I'm trying to find the
discussion as to why this happened, but what I'm finding isn't very
descriptive:
http://lists.infradead.org/pipermail/linux-mtd/2003-October/008685.html
I seem to remember IRC'ing with Christopher Hoover on this. Maybe he
can remember something? Christopher? My memory is somewhat murky.
next prev parent reply other threads:[~2004-09-07 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 17:37 jedec_probe problems with 16bit devices Ben Dooks
2004-09-07 13:34 ` Thayne Harbaugh [this message]
2004-09-07 15:08 ` David Woodhouse
2004-09-07 23:52 ` Christopher Hoover
2004-09-13 13:12 ` Thayne Harbaugh
2004-09-14 22:46 ` Ben Dooks
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=1094564091.20769.350.camel@tubarao \
--to=tharbaugh@lnxi.com \
--cc=ben-mtd@fluff.org \
--cc=ben@fluff.org \
--cc=ch@hpl.hp.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