From: Josh Boyer <jwboyer@gmail.com>
To: Franck <vagabon.xyz@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: How can I prevent MTD to access the end of a flash device ?
Date: Tue, 22 Nov 2005 09:21:52 -0600 [thread overview]
Message-ID: <625fc13d0511220721m3a6ad3ebp21b28a6b331ca05a@mail.gmail.com> (raw)
In-Reply-To: <cda58cb80511220658n671bc070v@mail.gmail.com>
On 11/22/05, Franck <vagabon.xyz@gmail.com> wrote:
> Hi,
>
> I have two questions that I can't answer by my own. I tried to look at
> FAQ and documentation on MTD website but found no answer.
>
> First question is about size of flash. I have a Intel strataflash
> whose size is 32MB but because of a buggy platform hardware I can't
> access to the last 64KB of the flash. How can I make MTD module aware
> of this new size. The restricted map size is initialized by my driver
> but it doesn't seem to be used by MTD.
The chip driver will detect a 32MiB chip from the CFI probe. The map
size isn't really used by the chip driver, it's just needed to ensure
that the area is accessible. What you could try doing is adding a
cfi_fixup function that changes the CFI data read in to remove the
last 64KiB of the chip... not sure if that will work though.
> The second question is about the "cacheable" mapping field in map_info
> structure. I looked at others drivers and this field seems to be
> optional. Does this field, if set, improve flash access a lot ? Should
> I set up a cacheable mapping ?
Usually this isn't something you want to do especially with flash. If
a cache line is flushed back to the chip it's probably not going to
work. The cacheable mappings work for RAM based devices though.
josh
next prev parent reply other threads:[~2005-11-22 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cda58cb80511070248o6d7a18bex@mail.gmail.com>
2005-11-22 14:58 ` Franck
2005-11-22 15:21 ` Josh Boyer [this message]
2005-11-22 15:53 ` Nicolas Pitre
2005-11-24 8:32 ` Franck
2005-11-28 16:55 ` Nicolas Pitre
2006-04-23 17:06 ` Franck Bui-Huu
2006-04-23 17:24 ` Nicolas Pitre
2006-04-23 18:57 ` Franck Bui-Huu
2006-04-24 15:40 ` David Woodhouse
2006-04-24 16:12 ` Franck Bui-Huu
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=625fc13d0511220721m3a6ad3ebp21b28a6b331ca05a@mail.gmail.com \
--to=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vagabon.xyz@gmail.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
all inboxes | Powered by JetHome®