From: "Christopher Hoover" <ch@hpl.hp.com>
To: <tharbaugh@lnxi.com>, "'Ben Dooks'" <ben-mtd@fluff.org>
Cc: ben@fluff.org, linux-mtd@lists.infradead.org
Subject: RE: jedec_probe problems with 16bit devices
Date: Tue, 7 Sep 2004 16:52:53 -0700 [thread overview]
Message-ID: <20040907235310.31BF32711A@mailhub.hp.com> (raw)
In-Reply-To: <1094564091.20769.350.camel@tubarao>
> 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/00
> 8685.html
>
> I seem to remember IRC'ing with Christopher Hoover on this. Maybe he
> can remember something? Christopher? My memory is somewhat murky.
I don't have any new information to report -- only what is noted above, that
some regression in the mtd tree about the time the CFI_DEVICETYPE_X8's
disappeared. It was never fixed while I worked with the board. It may be
fine now, but unfortunately I am unable to check easily.
Can we locate someone with a suitable platform and coax them into testing
the latest code?
-ch
next prev parent reply other threads:[~2004-09-07 23:56 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
2004-09-07 15:08 ` David Woodhouse
2004-09-07 23:52 ` Christopher Hoover [this message]
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=20040907235310.31BF32711A@mailhub.hp.com \
--to=ch@hpl.hp.com \
--cc=ben-mtd@fluff.org \
--cc=ben@fluff.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tharbaugh@lnxi.com \
/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