LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: David Ho <DavidHo@nanometrics.ca>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: user access to physical memory
Date: Wed, 05 May 2004 16:27:53 +0200	[thread overview]
Message-ID: <20040505142758.C691EC109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 05 May 2004 09:24:58 EDT." <OFD0681AD7.24E6EB05-ON85256E8B.004961BC-85256E8B.0049B26E@nanometrics.ca>


In message <OFD0681AD7.24E6EB05-ON85256E8B.004961BC-85256E8B.0049B26E@nanometrics.ca> you wrote:
>
> I know this question has been asked before, but I can't seem to find it in
> the archive.

You mean a simple search for "physical memory" like this one:

http://lists.linuxppc.org/results.html?restrict=linuxppc-embedded&words=physical+memory

didn't give you any results? Strange... I get quite a lot of messages.

> How do I get access to physical memory from user space?  I want to write a
> simple test problem to access the frame buffer directly on the LCD
> controller.

See the archives.

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
A conservative is a man with two perfectly good legs  who  has  never
learned to walk.                              - Franklin D. Roosevelt

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

  reply	other threads:[~2004-05-05 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-05 13:24 user access to physical memory David Ho
2004-05-05 14:27 ` Wolfgang Denk [this message]
2004-05-05 16:14   ` David Ho
2004-05-05 17:16     ` devfs with ramdisk problem dong in kang

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=20040505142758.C691EC109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=DavidHo@nanometrics.ca \
    --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