From: Philippe Gerum <rpm@xenomai.org>
To: Alexis Berlemont <berlemont.hauw@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Unstable driver integration policy
Date: Fri, 21 Nov 2008 05:23:39 +0100 [thread overview]
Message-ID: <492637CB.1000707@domain.hid> (raw)
In-Reply-To: <200811190056.12595.berlemont.hauw@domain.hid>
Alex,
Alexis Berlemont wrote:
> Hi,
>
> I would like to find a way to populate the Comedi drivers set.
>
> However, I am stuck by a simple fact: I have no acquisition board to validate
> a least driver...
>
> Starting from here, I am trying to find out what should be the proper method
> to provide non-validated drivers to anybody inclined to test them.
>
> Do you think creating a specific subversion branch for this stuff would be a
> good idea ?
>
I don't think so. Moving that code away from the focal point where people are
expected to find new code to test and work with won't help.
You could decide instead to implement drivers for a small set of very popular
acquisition cards; whether that implementation is eventually fully validated or
not depends on other people to have enough interest in that work to give you
access to some hw, or to validate the driver themselves. As Jan pointed out,
"experimental" is a convenient sticker to tell people about the exact state of
this work.
You spark the effort (this is _always_ the hardest and most demanding part of
the job), they help finalize it if they want to get serious about this.
> Alexis.
>
>
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
>
--
Philippe.
next prev parent reply other threads:[~2008-11-21 4:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 23:56 [Xenomai-core] Unstable driver integration policy Alexis Berlemont
2008-11-20 13:38 ` Jan Kiszka
2008-11-21 4:23 ` Philippe Gerum [this message]
2008-11-23 23:35 ` Alexis Berlemont
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=492637CB.1000707@domain.hid \
--to=rpm@xenomai.org \
--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.