All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Alexis Berlemont <berlemont.hauw@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Comedi drivers in Xenomai porting/integration status ?
Date: Tue, 17 Feb 2009 10:27:40 +0100	[thread overview]
Message-ID: <499A830C.3070803@domain.hid> (raw)
In-Reply-To: <200902170000.00900.berlemont.hauw@domain.hid>

Alexis Berlemont wrote:
> Hi,
> 
>> Hello all! I would like to know what is the current status of the Comedi
>> port to Xenomai.
>>
>> Should all the specific Comedi drivers (ni_pcimio, ni_mite) be available
>> for testing (by me or someone with a supported DAQ card) and (if ok) for
>> futher integration ?
> 
> I am still working on that port. It is a long work and I am wondering at each 
> line whether I should rewrite any part of code which does not comply with 
> common coding constraints. Unfortunately, I currently do not have a lot of 
> spare time. Anyway, most of the ni subdevices drivers have been ported (mite, 
> tio, mio, 8255). I am trying to finalize the global driver port.
> 
> By the way, in the middle of january, I noticed that the legacy Comedi branch 
> found its way into the mainline (through the staging tree). I do not know 
> what will be the future of such a package in mainstream. I assume the main 
> goal is the definition of a global framework for acquisition boards like V4L2 
> is for video cards. 
> 
> Starting from here, I have been thinking on some alternatives so as to benefit 
> from the kernel code. But I am a bit perplexed as the code does not seem to 
> evolve a lot (the 2.6.29-rc5 patch still contains some rtlinux/rtai/fusion 
> related code). I was unable to notice any significant work on the framework 
> to reach main kernel standards.
> 
> Since the beginning of January, there was only one mail thread which dealt 
> with Comedi on the lkml (which is, by the way, interesting): 
> http://lkml.org/lkml/2009/2/9/335

The staging tree does not start an automatic merging process. Unless the
original maintainers or some new pusher (don't count on GKH for this)
step in and work with the kernel people to address remaining issues
beyond coding style, staging may also be a dead end (specifically if the
project is adding a new user space interface that always needs extra
care). For larger projects like comedi, I would say staging is more of a
test if someone is serious about mainlining it.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


      parent reply	other threads:[~2009-02-17  9:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 12:55 [Xenomai-core] Comedi drivers in Xenomai porting/integration status ? Cristian Axenie
2009-02-16 23:00 ` Alexis Berlemont
2009-02-17  8:10   ` Cristian Axenie
2009-02-17  8:40   ` Peter Soetens
2009-02-17  9:41     ` Jan Kiszka
2009-02-17 11:08       ` Peter Soetens
2009-02-17 11:21         ` Jan Kiszka
2009-02-18  1:20         ` Alexis Berlemont
2009-02-18  7:38           ` Jan Kiszka
2009-02-18 23:43             ` Alexis Berlemont
2009-02-19  8:21               ` Anders Blomdell
2009-02-19 10:19               ` Jan Kiszka
2009-02-19 12:08               ` Peter Soetens
2009-02-19 16:22                 ` Jan Kiszka
2009-02-17  9:27   ` Jan Kiszka [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=499A830C.3070803@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=berlemont.hauw@domain.hid \
    --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.