All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Shawn Bohrer <shawn.bohrer@gmail.com>
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>,
	Guenter Gebhardt <g.gebhardt@meilhaus.de>
Subject: Re: staging: me4000 and relation to other data acquisition devices
Date: Tue, 28 Oct 2008 09:34:56 -0700	[thread overview]
Message-ID: <20081028163456.GA4278@suse.de> (raw)
In-Reply-To: <20081028154918.GA5630@mediacenter>

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?

thanks,

greg k-h

  reply	other threads:[~2008-10-28 16:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 15:49 staging: me4000 and relation to other data acquisition devices Shawn Bohrer
2008-10-28 16:34 ` Greg KH [this message]
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
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=20081028163456.GA4278@suse.de \
    --to=gregkh@suse.de \
    --cc=abbotti@mev.co.uk \
    --cc=ds@schleef.org \
    --cc=fmhess@users.sourceforge.net \
    --cc=g.gebhardt@meilhaus.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn.bohrer@gmail.com \
    --cc=w.beiter@aon.at \
    /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.