From: Oliver Korpilla <okorpil@fh-landshut.de>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Linux and RTAI on the Motorola VME Boards
Date: Thu, 18 Mar 2004 10:50:59 +0100 [thread overview]
Message-ID: <40597103.3090704@fh-landshut.de> (raw)
Hello!
I'm doing a university project on Linux in realtime applications.
The ultimate goal is to evaluate realtime options for the MVME 2100,
MVME 5500, and VMIVME 7050 (ok, that's an Intel one, just mentioned it
for completeness :) ).
Since hard realtime is preferred, kernel preemption doesn't seem to be
good enough, so I wanted to focus on RTAI. I found several Linux drivers
for CPU and board hardware, and several drivers for the Tundra Universe
II PCI-VME bridge.
Unfortunately, I didn't find very much documentation on RTAI. I'm
actually wondering what I need to communicate with the VME bus in
realtime. Can I safely call the Linux drivers functions? Do I need to
use a modified version of the driver? What features in a driver do not
mix with RTAI?
I've read on the list Xavier Grave seemed to have done something very
similar on the MVME 5500, but he seems to have not published all of it,
at least not now.
On a similar issue:
I found a discussion about problems using the open_pic driver with the
MVME 2100, and considerations about a possible rewrite of the driver to
accomodate more flexibility. Has someone done it by now?
Thanks in advance,
Oliver Korpilla
CS student at the University of Applied Sciences at Landshut, Germany
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-03-18 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 9:50 Oliver Korpilla [this message]
2004-03-18 11:11 ` Linux and RTAI on the Motorola VME Boards Marius Groeger
2004-03-18 15:42 ` Oliver Korpilla
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=40597103.3090704@fh-landshut.de \
--to=okorpil@fh-landshut.de \
--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).