All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Michael Haberler <haberlerm@gmail.com>, xenomai@xenomai.org
Subject: Re: [Xenomai] RT-CAN question (was: CAN bus on beaglebone black)
Date: Sat, 21 Mar 2015 09:57:53 +0100	[thread overview]
Message-ID: <550D3291.7030100@grandegger.com> (raw)
In-Reply-To: <CADvZd9Z8LSPRMAJWb1Tp91i4i9N5wLGMxb3_suaDyFRwRiJd-w@mail.gmail.com>

On 03/19/2015 10:57 AM, Michael Haberler wrote:
> status:
> 
> I have Steve Batazzo's driver running on the beaglebone, using a stock
> Xenomai kernel from Robert Nelson's repo (linux-image-3.8.13-xenomai-r71
> from http://repos.rcn-ee.net/debian/), current driver out of tree at
> https://github.com/mhaberler/rtcan-bb branch mah
> 
> I also have a preliminary HAL driver for machinekit which talks to a
> Trinamic motor over RT-CAN just fine (beaglebone for now, x86 once I get a
> CAN PCI card).
> 
> I'm working with Steve to get the driver polished and hope we can inject it
> into the Xenomai foodchain eventually, after which it will be eventually
> picked up by Robert's periodic builds, and the whole thing becomes an
> 'apt-get install' - affair. But we're not there yet.
> 
> 
> I have a few questions on RT-CAN (I guess really RTDM):
> 
> - can the RTDM API (
> https://xenomai.org/documentation/trunk/html/api/group__userapi.html) be
> used from a normal Posix thread (non-RT) just alike? from the rtcansend*
> utilities src it looks like at least for setup, even if the send/receive
> ops are done in an RT thread.
> 
> - socket-CAN and RT-CAN interworking: I assume this is an either-or affair,
> right? (background: for some jobs the RT-CAN features are overkill, and in
> that case something like the python-can binding would be convenient to use)

If the resources (irq, mem, etc.) used by the device are clearly
separated, it might be possible to use one device (of the same type) for
Linux and the other for RTCAN. It will work for sure for devices using
different drivers (belonging to different controllers).

Wolfgang.



  parent reply	other threads:[~2015-03-21  8:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  9:57 [Xenomai] RT-CAN question (was: CAN bus on beaglebone black) Michael Haberler
2015-03-19 18:44 ` Steve B
2015-03-20  6:15   ` Michael Haberler
2015-03-20  6:58     ` Michael Haberler
2015-03-20  7:26       ` Michael Haberler
2015-03-20  7:54         ` Jan Kiszka
2015-03-20  8:02           ` Michael Haberler
2015-03-20 17:42             ` Steve B
2015-03-20 18:16               ` Gilles Chanteperdrix
2015-03-20 18:28                 ` Steve B
2015-03-20 18:39                   ` Gilles Chanteperdrix
2015-03-21  8:48                 ` Wolfgang Grandegger
2015-03-21  8:57 ` Wolfgang Grandegger [this message]
2015-03-21 14:56   ` Michael Haberler

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=550D3291.7030100@grandegger.com \
    --to=wg@grandegger.com \
    --cc=haberlerm@gmail.com \
    --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.