linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Muaddi, Cecilia" <cecilia.muaddi@alloptic.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: access memory mapped registers
Date: Fri, 10 Jan 2003 00:14:06 +0100	[thread overview]
Message-ID: <20030109231411.AE68EC608E@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 09 Jan 2003 14:00:13 PST." <885489B3B89FB6449F93E525DF78777F06453B@srvnt506.ALLOPTIC.COM>


In message <885489B3B89FB6449F93E525DF78777F06453B@srvnt506.ALLOPTIC.COM> you wrote:
>
> I will like to access some memory mapped registers through user space
> applications.
> Do i just use the "mmap" function calls to map the physical memory to my
> user space?

You don't. Design a proper device driver interface instead.


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
By the way, ALL software projects are done by iterative  prototyping.
Some companies call their prototypes "releases", that's all.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-01-09 23:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 22:00 access memory mapped registers Muaddi, Cecilia
2003-01-09 23:14 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-10  0:18 Kerl, John
     [not found] <885489B3B89FB6449F93E525DF78777F06453E@srvnt506.ALLOPTIC.COM>
2003-01-10  0:25 ` Wolfgang Denk
2003-01-10  0:27 Muaddi, Cecilia
2003-01-10  1:12 ` Wolfgang Denk
     [not found] <885489B3B89FB6449F93E525DF78777F064542@srvnt506.ALLOPTIC.COM>
2003-01-10  1:20 ` Wolfgang Denk
2003-01-13 15:14 ` Kenneth Johansson

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=20030109231411.AE68EC608E@atlas.denx.de \
    --to=wd@denx.de \
    --cc=cecilia.muaddi@alloptic.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).