From: David Woodhouse <dwmw2@infradead.org>
To: ian.nelson@echostar.com
Cc: "mtd@infradead.org" <mtd@infradead.org>
Subject: Re: CFI Physical Mapped working?
Date: Thu, 07 Dec 2000 08:02:18 +0000 [thread overview]
Message-ID: <2963.976176138@redhat.com> (raw)
In-Reply-To: <3A2ED2CA.14522213@echostar.com>
ian.nelson@echostar.com said:
> I've been trying to get either the CFI AMD or CFI Physical Mapping to
> work with no luck. Are there any tricks to making it work? It
> doesn't look like any of that code is ever called. I can load the
> modules but nothing ever happens. I've put some printks in the
> init_module function and nothing ever prints.
There's no known reason why it shouldn't work.
init_physmap() ought to autoload the cfi_probe module, which in turn will
autoload the cfi_cmdset_0002 module if it finds an appropriate chip.
You may find it's best to write a custom map driver instead of the physmap
driver, which handles the chip select line for you.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
prev parent reply other threads:[~2000-12-07 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 23:59 CFI Physical Mapped working? Ian S. Nelson
2000-12-07 8:02 ` David Woodhouse [this message]
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=2963.976176138@redhat.com \
--to=dwmw2@infradead.org \
--cc=ian.nelson@echostar.com \
--cc=mtd@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