All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Marko Roganovic <marko.roganovic@pupin.rs>, xenomai@xenomai.org
Subject: Re: [Xenomai] CAN bus on beaglebone black
Date: Tue, 01 Jul 2014 21:37:20 +0200	[thread overview]
Message-ID: <53B30DF0.80301@grandegger.com> (raw)
In-Reply-To: <A7F7E9DFC6DD4132AD68D2EE9D2A451A@pc2012PC>

On 07/01/2014 10:30 AM, Marko Roganovic wrote:
> Dear Xenomai users and developers,
> 
> 
> 
> I am relatively new to Xenomai, and we are working on a project that uses Beaglebone black platform (3.8.13xenomai kernel). The idea is to port our code that runs on x86 platform and RTAI Linux interface, to Beaglebone black. In a process we decided to switch from RTAI to Xenomai. Most of the job is done relatively with no problems, but now we are facing the challenge how to connect our proprietary hardware to this new Beaglebone black platform. The idea is to use CAN bus, since it best suits real time constraints that we must meet. 
> 
> 
> 
> As I understood, in rtcan core within Xenomai, there is no support for c_can (d_can) driver which is used on Beaglebone black (we tried kernel driver and it worked with our hardware fine). So I am interested if someone is working on porting this driver to rtcan (or has ported it already). Any help is appreciated.

Yes, the c_can linux kernel driver needs to be ported to rtcan. This
should be rather straight forward. I have done it some time ago for the
Flexcan controller.

Wolfgang.



  reply	other threads:[~2014-07-01 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01  8:30 [Xenomai] CAN bus on beaglebone black Marko Roganovic
2014-07-01 19:37 ` Wolfgang Grandegger [this message]
     [not found]   ` <65D33F68-CF96-4C36-8135-4C66E9357154@mah.priv.at>
2015-03-16  7:21     ` Wolfgang Grandegger

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=53B30DF0.80301@grandegger.com \
    --to=wg@grandegger.com \
    --cc=marko.roganovic@pupin.rs \
    --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.