From: Thomas Lockhart <Thomas.Lockhart@domain.hid>
To: Guenter Ebermann <guenter.ebermann@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] migration scenario to xenomai
Date: Fri, 06 Aug 2010 14:51:33 -0700 [thread overview]
Message-ID: <4C5C83E5.9040508@domain.hid> (raw)
In-Reply-To: <AANLkTi=yDXty82va8JGzmRA453e021EvomyYitaQTCTg@domain.hid>
> So I thought of moving this part of our communication stack which has hard-real
> time requirement (FlexRay, CAN, LIN) into a seperate process which only lives
> in the xenomai domain (it will communicate with low-prio linux processes via
> non-blocking fifo or such). But this raises two important questions: Can I
> access the FPGA registers directly from a xenomai task in the user space? Or
> do I have to write a minimal linux or xenomai-rtdm device driver which maps
> FPGA registers from kernel to user space?
You can do direct register access from userland; we do this with several
device drivers in our system.
We are thinking about trying to refactor a driver to use RTDM due to the
recent discussions on losing support for userland interrupt handling,
but for our purposes the current support for interrupts in userland has
worked fine.
We use pci_scan_bus() and friends for finding the device, and mmap to
get it into userland memory.
hth
- Tom
next prev parent reply other threads:[~2010-08-06 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 21:42 [Xenomai-help] migration scenario to xenomai Guenter Ebermann
2010-08-06 21:51 ` Thomas Lockhart [this message]
2010-08-07 9:28 ` Guenter Ebermann
2010-08-07 23:17 ` Wolfgang Denk
2010-08-07 7:46 ` Gilles Chanteperdrix
2010-08-07 10:13 ` Guenter Ebermann
2010-08-07 10:36 ` Gilles Chanteperdrix
[not found] ` <B6A5952D-4182-4D39-B28E-0D9BAE2872C4@domain.hid>
2010-08-07 11:02 ` Gilles Chanteperdrix
2010-08-07 11:36 ` 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=4C5C83E5.9040508@domain.hid \
--to=thomas.lockhart@domain.hid \
--cc=guenter.ebermann@domain.hid \
--cc=xenomai@xenomai.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 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.