From: "Juha Yrjölä" <juha.yrjola@solidboot.com>
To: Martin Margraf <m_margraf@web.de>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: change cpu_freq
Date: Wed, 14 Jun 2006 15:44:06 +0300 [thread overview]
Message-ID: <44900496.40400@solidboot.com> (raw)
In-Reply-To: <44900251.3050702@web.de>
Martin Margraf wrote:
> my next question is, how can i read/write to the regs of the omap5912?
> during using 2.4 kernel i was able to access the regs directly with a
> module. but now with 2.6 kernel i get a segmentation fault. maybe
> someone can help me?
Nowadays there isn't 1-to-1 mapping between physical and virtual I/O
addresses. If you're operating on a physical address, you can use the
omap_{read,write} helper macros to access the registers. Alternatively,
you can convert the physical address to a virtual one first by io_p2v(),
after which the memory accesses can be done directly.
Cheers,
Juha
next prev parent reply other threads:[~2006-06-14 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 12:34 change cpu_freq Martin Margraf
2006-06-14 12:44 ` Juha Yrjölä [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-15 18:19 Minjie Lin
2006-06-16 6:40 Martin Margraf
2006-06-16 23:35 Minjie Lin
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=44900496.40400@solidboot.com \
--to=juha.yrjola@solidboot.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=m_margraf@web.de \
/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