From: David Woodhouse <dwmw2@infradead.org>
To: "Sébastien Côté" <scote1@Matrox.COM>
Cc: mtd@infradead.org
Subject: Re: Status of MTD for CFI
Date: Fri, 30 Jun 2000 14:25:50 +0100 [thread overview]
Message-ID: <7996.962371550@cygnus.co.uk> (raw)
In-Reply-To: <395C9BEC.98AC005A@matrox.com>
scote1@Matrox.COM said:
> : what is nora.c for (from the name, I guess it's a NOR flash and from
> the code I guess it's CFI but that's all I know)?
nora.c is misnamed. It's just a 'map' driver for memory chips which are
mapped directly into the CPU's VM, which is what happens on a lot of ARM
boards. It's not really CFI-specific at all, except that it happens to call
the cfi_probe function and none other at the moment.
By changing a couple of defines for the address and size, you can make it
handle memory chips mapped anywhere in VM rather than just where my
particular board happens to have them.
> and what does SBC stand for ?
Single Board Computer.
scote1@Matrox.COM said:
> I've got an Intel StrataFlash so it's both 16 bits and CFI compliant.
> I quickly checked the files you mentioned and this all seems very
> simple.
It just got less simple. We now make an attempt to do proper async handling
of flash chips, and I'm just about to test it. If it works, I'll try to
build up the courage to shift the erase stuff into a timer, and enable
suspension of in-progress erases.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-06-30 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-29 19:45 Status of MTD for CFI Sébastien Côté
2000-06-29 21:03 ` David Woodhouse
2000-06-30 13:09 ` Sébastien Côté
2000-06-30 13:25 ` David Woodhouse [this message]
2000-07-03 23:12 ` Jason Gunthorpe
2000-07-04 7:31 ` David Woodhouse
2000-07-04 15:39 ` Jason Gunthorpe
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=7996.962371550@cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=mtd@infradead.org \
--cc=scote1@Matrox.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