From: Luke <luke_epsilon@yahoo.com>
To: Vipin Malik <vipin@embeddedlinuxworks.com>,
linux-mtd@lists.infradead.org
Subject: ZFMicro MachZ modification of physmap.c
Date: Thu, 23 Aug 2001 12:41:28 -0700 (PDT) [thread overview]
Message-ID: <20010823194128.72225.qmail@web13602.mail.yahoo.com> (raw)
In-Reply-To: <5.1.0.14.0.20010823095635.00b00ca0@mail.spewey.com>
Hello,
--- Vipin Malik <vipin@embeddedlinuxworks.com> wrote:
>
> Normally, one map's the entire flash as far as the chip select's are
> concerned, and set's the start/length logically in the map driver (in your
> case physmap.c).
> Of course you don't want to start/stop in the middle of a sector. Only on
> sector boundaries please :)
>
It seems that the standard physmap.c just takes the 3 CONFIG_* inputs of start (of the physical
memory address to look for the flash),length, and bus width. To change the offset of the flash to
access do you modify the return from ioremap() ?
For example, if I have an 8 Mbyte flash chip that I want to access with MTD and I only want to map
from byte offset 0x300000 to 0x700000 of the flash I should set my CONFIG_MTD_PHYSMAP_LEN to 4
Mbytes and inside the physmap.c code add an offset of 0x300000 to something?
Sorry for being a slow learner on this one,
Luke
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
next prev parent reply other threads:[~2001-08-23 19:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-11 4:34 Am29LV065D woes??? Luke
2001-08-12 14:06 ` Vipin Malik
2001-08-14 0:35 ` Am29LV065D woes -- ZFMicro MachZ help? Luke
2001-08-14 2:30 ` Vipin Malik
2001-08-14 4:08 ` Luke
2001-08-23 6:08 ` ZFMicro MachZ success with the Am29LV065D Luke
2001-08-23 10:33 ` Vipin Malik
2001-08-23 14:54 ` Luke
2001-08-23 15:00 ` Vipin Malik
2001-08-23 19:41 ` Luke [this message]
2001-08-23 21:36 ` ZFMicro MachZ modification of physmap.c Vipin Malik
2001-08-14 3:10 ` Am29LV065D woes -- ZFMicro MachZ help? Changwoo Ryu
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=20010823194128.72225.qmail@web13602.mail.yahoo.com \
--to=luke_epsilon@yahoo.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vipin@embeddedlinuxworks.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