LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Shawn Bohrer <shawn.bohrer@gmail.com>
To: Greg KH <gregkh@suse.de>
Cc: David Schleef <ds@schleef.org>,
	Frank Mori Hess <fmhess@users.sourceforge.net>,
	Ian Abbott <abbotti@mev.co.uk>,
	linux-kernel@vger.kernel.org, Wolfgang Beiter <w.beiter@aon.at>
Subject: Re: staging: me4000 and relation to other data acquisition devices
Date: Wed, 29 Oct 2008 12:37:19 -0500	[thread overview]
Message-ID: <20081029173719.GB5630@mediacenter> (raw)
In-Reply-To: <20081028163456.GA4278@suse.de>

On Tue, Oct 28, 2008 at 09:34:56AM -0700, Greg KH wrote:
> On Tue, Oct 28, 2008 at 10:49:18AM -0500, Shawn Bohrer wrote:
> > I have some questions about the user-kernel interface of the me4000
> > driver.  From my looking through the code it seems specific to the
> > me4000 hardware which does concern me since there are hundreds of
> > different data acquisition devices from many different vendors.  In my
> > opinion it would beneficial if at the very least all of these devices
> > shared a common device interface.
> 
> I totally agree.
> 
> The me4000's user interface is not "set in stone" and needs to be fixed
> up in order to move into the main kernel tree.
> 
> > Additionally there is the out of tree Comedi project:
> > 
> > http://comedi.org
> > 
> > Which supports this hardware, and many more, with a generic device
> > interface.  There may be other reason not to merge Comedi (I know they
> > have a desire to maintain support of their RT support), but I can't help
> > but feel that merging the me4000 driver without thinking about the
> > hundreds of other devices out there is a mistake.
> 
> I would love to get comedi into the kernel tree.  People have talked
> about it for years now, is it time for me to just take a snapshot and
> place it in drivers/staging/ for everyone to then work on cleaning up
> properly?

I think that is up to the Comedi maintainers.  If the Comedi maintainers
do not want to head in that direction, I'm sure the me4000 driver
currently in drivers/staging/ would benefit from their review.

--
Shawn

  parent reply	other threads:[~2008-10-29 17:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 15:49 Shawn Bohrer
2008-10-28 16:34 ` Greg KH
2008-10-28 17:33   ` Randy Dunlap
2008-10-28 18:14     ` Greg KH
2008-10-29 15:12       ` Wolfgang Beiter
2008-10-30  0:02         ` Greg KH
2008-10-29 18:57       ` Moritz Muehlenhoff
2008-10-30  0:37         ` J.R. Mauro
2008-10-30  0:46           ` Richard Holden
2008-10-30  1:42           ` Greg KH
2008-10-30 14:25             ` J.R. Mauro
2008-10-30 15:23               ` Greg KH
2008-10-30 15:42                 ` J.R. Mauro
2008-10-31 15:00                   ` Greg KH
2008-10-31 15:10                     ` J.R. Mauro
2008-10-30  1:43         ` Greg KH
2008-10-29 17:37   ` Shawn Bohrer [this message]
2008-10-30  0:04     ` Greg KH

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=20081029173719.GB5630@mediacenter \
    --to=shawn.bohrer@gmail.com \
    --cc=abbotti@mev.co.uk \
    --cc=ds@schleef.org \
    --cc=fmhess@users.sourceforge.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w.beiter@aon.at \
    --subject='Re: staging: me4000 and relation to other data acquisition devices' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).