From: scarayol@assystembrime.com
To: Jean-Christophe Dubois <jdubois@mc.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Réf. : Re: Réf. : RE: mmap : please help !
Date: Thu, 14 Apr 2005 16:37:53 +0200 [thread overview]
Message-ID: <OF6D9DF5A3.572A1EAE-ONC1256FE3.004DDA93@brime.fr> (raw)
Hello Jean-Christophe,
That's right, I verify all the useful parameters in my driver and
everything seems OK.
But, the real question is : if you use the /dev/mem (with open() and mm=
ap
()), could you use, in the user space, the pointer returned by the mmap=
function to access the physical memory or do you have to use read/write=
(on
the file descriptor) to access physical memory because i haven't the sa=
me
results according to the used method.
Thanks for 'od' but i haven't in my packages.
Sophie.
=
=
Jean-Christop =
=
he Dubois Pour : scarayol@assystembrime=
.com =
<jdubois@mc.c cc : linuxppc-embedded@ozla=
bs.org =
om> Objet : Re: R=E9f. : RE: =
mmap : please help ! =
=20
=
=
14/04/05 =
=
12:09 =
=
=
=
=
=
Hello Sophie,
On Thu, 2005-04-14 at 11:38 +0200, scarayol@assystembrime.com wrote:
> St=E9phane,
>
> thanks for your help.
> But I think that, except instruction eieio, I do similar things. You=
use
> the virtual address returned by mmap but have you the same values if =
you
> use write/read(axs_mem_fd,...) instead of in_8/out_8.
> That is my problem : I want to be sure that when I use the virtual
address
> returned by mmap, I access really to the physical memory mapped area.=
As the /dev/map_mc is your custom driver it should be fairly easy for
you to check the parameters you pass to remap_page_range().
> Do you know a shell command in order to dump the memory and verify wh=
at I
> do ?
try "od"
JC
> ----------------------------------------------------------
> Sophie CARAYOL
>
> TECHNOLOGIES & SYSTEMES
> 50 rue du Pr=E9sident Sadate
> F - 29337 QUIMPER CEDEX
>
> T=E9l: +33 2 98 10 30 06
> mailto:scarayol@assystembrime.com
> ----------------------------------------------------------
>
>
>
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
=
next reply other threads:[~2005-04-14 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 14:37 scarayol [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 14:51 Réf. : Re: Réf. : RE: mmap : please help ! Fillod Stephane
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=OF6D9DF5A3.572A1EAE-ONC1256FE3.004DDA93@brime.fr \
--to=scarayol@assystembrime.com \
--cc=jdubois@mc.com \
--cc=linuxppc-embedded@ozlabs.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