From: Philippe Gerum <rpm@xenomai.org>
To: Jesus Villena <j.villena@ecler.com>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: Re: [EVL] Problems writing to physical memory with mmap on oob context
Date: Tue, 26 Sep 2023 17:46:26 +0200 [thread overview]
Message-ID: <87o7hpndh0.fsf@xenomai.org> (raw)
In-Reply-To: <DB8PR10MB3706B544A1AD8812E2ACA78BF9C3A@DB8PR10MB3706.EURPRD10.PROD.OUTLOOK.COM>
Jesus Villena <j.villena@ecler.com> writes:
> Thanks Philippe,
>
> I have already tried the custom driver solution you mention, mapping the shared memory in kernel with ioremap, and adding read and write handlers instead of mapping the memory to userland, and it works, but I would prefer to do a proper mmap to access to the memory in a transparent way.
>
I meant writing a driver exporting a mmap interface restricted to your
SRAM area, instead of using the generic /dev/mem device for this.
--
Philippe.
next prev parent reply other threads:[~2023-09-26 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 11:21 [EVL] Problems writing to physical memory with mmap on oob context Jesus Villena
2023-09-26 14:15 ` Philippe Gerum
2023-09-26 15:40 ` Jesus Villena
2023-09-26 15:46 ` Philippe Gerum [this message]
2023-09-26 16:04 ` Jesus Villena
2023-09-27 6:51 ` Philippe Gerum
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=87o7hpndh0.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=j.villena@ecler.com \
--cc=xenomai@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.