From: ebiederman@lnxi.com (Eric W. Biederman)
To: <linux-mtd@lists.infradead.org>
Subject: Q: Probing for devices > buswidth???
Date: 08 Oct 2001 23:23:44 -0600 [thread overview]
Message-ID: <m3y9mljsin.fsf@DLT.linuxnetworx.com> (raw)
I'm trying to bringin some mtd map drivers for some non cfi devices.
Trying to understand some anomolous results I discovered that
gen_probe_newchip is looking for:
16 bit devices on an 8 bit bus.
byte interleaved 16 bit devices on a 16 bit bus.
And some really bizare things for a 32 bit bus.
Is there any good reason for doing it that way?
If not I'm going to figure out how to kill that extra confusing code.
Eric
next reply other threads:[~2001-10-09 5:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 5:23 Eric W. Biederman [this message]
2001-10-09 6:45 ` Q: Probing for devices > buswidth??? David Woodhouse
2001-10-09 6:50 ` Eric W. Biederman
2001-10-09 6:53 ` David Woodhouse
2001-10-09 7:04 ` Eric W. Biederman
2001-10-09 13:19 ` Kenneth Johansson
2001-10-09 13:22 ` David Woodhouse
2001-10-09 13:56 ` Kenneth Johansson
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=m3y9mljsin.fsf@DLT.linuxnetworx.com \
--to=ebiederman@lnxi.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