From: Marcin Glogowski <marcin.glogowski@interia.pl>
To: linux-kernel@vger.kernel.org
Subject: ioremap - simply question, big problem (to me)
Date: Sat, 02 Apr 2005 09:42:32 +0200 [thread overview]
Message-ID: <424E4CE8.4070702@interia.pl> (raw)
Hi everybody,
I have several questions about ioremap:
1) I have two 16 bit sram memory devices. To force it works I had to use
ioremap with memorysize*2, because
I was able to write to the 1 and 2 byte, 5,6, 9,10, 13,14 and so on.
Please explain why my ioremap space is non-continous,
how to ioremap a 32 bit device that consists of 2 16 bit devices? (in
another system I simply copied the 16 bits to first device and another
16 bits
to the second device and I had a working system) and why in the remapped
memory are holes?
2) In my another system to get a value of the register from a flash
device I had to use "volatile u16 the_address_of_my_device".
How to get the value in the case when Linux has virtual remapped the
physical address?
Thank you.
----------------------------------------------------------------------
Startuj z INTERIA.PL! >>> http://link.interia.pl/f186c
reply other threads:[~2005-04-02 7:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=424E4CE8.4070702@interia.pl \
--to=marcin.glogowski@interia.pl \
--cc=linux-kernel@vger.kernel.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