From: Robert Kaiser <rob@sysgo.de>
To: Vipin Malik <vmalik@danielind.com>
Cc: Nicolas Pitre <nico@cam.org>,
Kevin Jacobs <jacobs@penguin.theopalgroup.com>,
mtd@infradead.org
Subject: Re: Oh, the many joys of MTD...
Date: Mon, 12 Mar 2001 11:10:44 +0100 [thread overview]
Message-ID: <01031211300300.00792@rob> (raw)
In-Reply-To: <3AA7C45C.E7652E1F@danielind.com>
On Don, 08 Mär 2001 you wrote:
> >
> > The device mapping is done with the ioremap() call which is responsible for
> > providing a non-cacheable mapping.
>
> Actually I had to use ioremap_nocache() call with my ELANSC520 processor (which
> has a processor I&D cache).
Strange, I had just the opposite experience here. I'm using the SC520 CDP board.
> This is even with caching actually disabled for the flash banks inside the
> processor (by the startup processor init code).
My board's BIOS provides options to enable/disable write buffering and to
set cache operation to write-back/write-through. No matter how I set these,
the mtd code always seemed to work, even if I used plain ioremap() . The SC520
has a set of PAR registers which allow to set individual cachability attributes
for ROM (i.e. chips that are selected by the ROMCS[12] and BOOTCS signals).
These are always set to non-cacheable by my BIOS. Then there are also the
cacheability attributes in the page table (this is what ioremap() and
ioremap_nocache() differ in).
So there are several obscure places where one can enable/disable cacheing for
a given address region on an SC520. Question is which of them takes
precedence in case they contradict.
Nevertheless, since everybody seems to agree that FlashROM needs to be
non-cached for the MTD code to work, I guess it's safer to generally use
ioremap_nocache().
Rob
----------------------------------------------------------------
Robert Kaiser email: rkaiser@sysgo.de
SYSGO RTS GmbH
Am Pfaffenstein 14 phone: (49) 6136 9948-762
D-55270 Klein-Winternheim / Germany fax: (49) 6136 9948-10
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-03-12 10:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 13:38 Oh, the many joys of MTD Kevin Jacobs
2001-03-08 14:43 ` David Woodhouse
2001-03-08 14:49 ` Kevin Jacobs
2001-03-08 16:27 ` Nicolas Pitre
2001-03-08 16:29 ` Kevin Jacobs
2001-03-08 17:41 ` Vipin Malik
2001-03-08 17:40 ` Kevin Jacobs
2001-03-09 2:54 ` Alice Hennessy
2001-03-12 10:10 ` Robert Kaiser [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-13 7:24 Jonas Holmberg
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=01031211300300.00792@rob \
--to=rob@sysgo.de \
--cc=jacobs@penguin.theopalgroup.com \
--cc=mtd@infradead.org \
--cc=nico@cam.org \
--cc=vmalik@danielind.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