linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Korpilla <okorpil@fh-landshut.de>
To: Marius Groeger <mgroeger@sysgo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux and RTAI on the Motorola VME Boards
Date: Thu, 18 Mar 2004 16:42:18 +0100	[thread overview]
Message-ID: <4059C35A.1000203@fh-landshut.de> (raw)
In-Reply-To: <Pine.LNX.4.56.0403181202500.4114@mag.sysgo.com>


>However, RTAI does share the kernel memory map, so any memory region mapped
>by the Linux kernel (or a driver) is also visible to RTAI.
>
>
Actually, from reading the RTAI mailing list, it may just be possible to
let a Linux driver establish the necessary mappings, and use those in a
RTAI task. If I catch the interrupts related to that device (that info
should be obtainable , too, on task initialization, where real-time
isn't needed) and process them only in the RTAI space, using the
established mappings, this could actually be sufficient for my purposes.
I first have to evaluate that.

>I don't know the VME driver you're about to use, but you should be
>able to safely use the VME memory regions it maps.
>
>BTW, you may want to join the RTAI list,
>
I did. :)

Since enough of the entries on this list seem to refer to VME stuff on
MVME boards, and solutions with RTAI and Linux were proposed or offered
here as well (for example by Xavier Grave), I thought it to be wise to
drop a mail here still.

Of course I would be grateful on any help about drivers, stuff, and
(open?) BSPs about those boards (MVME 2100, MVME 5500) in general, too! :)

Thanks,
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/

      reply	other threads:[~2004-03-18 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18  9:50 Linux and RTAI on the Motorola VME Boards Oliver Korpilla
2004-03-18 11:11 ` Marius Groeger
2004-03-18 15:42   ` Oliver Korpilla [this message]

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=4059C35A.1000203@fh-landshut.de \
    --to=okorpil@fh-landshut.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mgroeger@sysgo.com \
    /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).