All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
	Michael Haberler <haberlerm@gmail.com>
Cc: xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] RTDM-native mainlining - status?
Date: Sun, 14 Jun 2015 10:53:10 +0200	[thread overview]
Message-ID: <557D40F6.9000105@xenomai.org> (raw)
In-Reply-To: <438716acfb1172076225e9266fa98c04.squirrel@sourcetrek.com>

On 06/14/2015 10:46 AM, Gilles Chanteperdrix wrote:
> 
> Michael Haberler wrote:
>>
>>> Am 13.06.2015 um 09:19 schrieb Gilles Chanteperdrix
>>> <gilles.chanteperdrix@xenomai.org>:
>>>
>>>
>>> Michael Haberler wrote:
>>>> I hope I do not overlook some boundary condition - but assuming that
>>>> building out-of-tree RTDM support is significantly less invasive and
>>>> version-dependent than patching a kernel, that scheme could enormously
>>>> widen the range of platforms we could deploy with good results, and at
>>>> the
>>>> same time lower maintenance requirements.
>>>
>>> No, alas a Linux driver is always version-dependent, so, the driver
>>> would
>>> contain some wrappers to handle differences between version. But this is
>>> not something new, everybody maintaining out-of-tree Linux kernel code
>>> has
>>> been doing it for a very long time. We do it for Xenomai, even Linux
>>> developers are doing it for the driver backport project.
>>
>> certainly, but if the problem scope changes from "patch a specific kernel
>> version for full Xenomai support" to "maintain the API and support library
>> for a set of out-of-tree drivers on top of a stock kernel from elsewhere"
>> we're in a different (my guess: easier and more widely applicable)
>> ballgame
> 
> There should not be a need for a support library, since RTDM uses the
> usual driver API open, read, write, ioctl, I would expect an RTDM native
> driver to work with the plain Linux version of these calls.
> 
>>
>> I would really be interested in exploring this route with a simple
>> example, like this GPIO RTDM driver, and try to make this work with say a
>> vanilla or RT-PREEMPT kernel - if only to gauge feasibility, effort and
>> results
>>
>> what would you recommend as a starting point?
> 
> Well, RTDM native is not part of Xenomai (yet), so, the first step would
> be to to try and compile it. The last commits in the git date back from
> 2007, so, some adaptation will be needed to get it running with the latest
> kernels.
> 
> https://git.xenomai.org/rtdm-native.git/
> 

And changes to the RTDM API brought in by the transition to xenomai 3 too.


-- 
Philippe.


  reply	other threads:[~2015-06-14  8:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 21:41 [Xenomai] RTDM-native mainlining - status? Michael Haberler
2015-06-12 23:02 ` Gilles Chanteperdrix
2015-06-13  4:48   ` Michael Haberler
2015-06-13  7:19     ` Gilles Chanteperdrix
2015-06-14  7:31       ` Michael Haberler
2015-06-14  8:46         ` Gilles Chanteperdrix
2015-06-14  8:53           ` Philippe Gerum [this message]
2015-06-14  8:55             ` Gilles Chanteperdrix
2015-06-14 11:37           ` Michael Haberler
2015-06-14 11:43             ` Gilles Chanteperdrix

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=557D40F6.9000105@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.