public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Shawn Bohrer <shawn.bohrer@ni.com>
Cc: fmhess@users.sourceforge.net, linux-kernel@vger.kernel.org,
	abbotti@mev.co.uk, ds@schleef.org
Subject: Re: [staging] High level Comedi feedback
Date: Wed, 11 Feb 2009 15:34:11 -0800	[thread overview]
Message-ID: <20090211233411.GA21860@suse.de> (raw)
In-Reply-To: <20090211231728.GC23561@bohrers.amer.corp.natinst.com>

On Wed, Feb 11, 2009 at 05:17:28PM -0600, Shawn Bohrer wrote:
> Hey Frank,
> 
> On Mon, Feb 09, 2009 at 10:38:44PM -0500, Frank Mori Hess wrote:
> > On Monday 09 February 2009 13:01, Shawn Bohrer wrote:
> > > 6. COMEDI doesn't yet support configuring hardware buffer sizes for deep
> > > on-board FIFOs.
> >
> > There is INSN_CONFIG_BLOCK_SIZE, which a couple drivers use to configure
> > their hardware fifo size.
> 
> Thanks I'll take a close look at this.
> 
> > By the way, I'm not subscribed to linux-kernel.  Comedi does have its own
> > mailing list, maybe this kind of discussion would be easier on a more
> > specific, lower traffic list?
> 
> Since Comedi is working its way into the kernel I'd like to get a
> little broader exposure on some of the things that we'd like to see
> improved before any interfaces get set in stone.  I think it could be
> beneficial to cc the Comedi list, but it looks like that list only
> accepts emails from subscribers.

The Comedi interface is not set in stone at all yet.  I've just
integrated the core, and am still adding the remaining drivers
(hopefully get to the rest of them tomorrow).  Then we can start
cleaning up the interfaces between the core and drivers, and review the
external interface as well, to see if it is lacking in any way, or not
working properly for any specific users (like yourself.)

Sound good?

thanks,

greg k-h

      reply	other threads:[~2009-02-11 23:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 18:01 [staging] High level Comedi feedback Shawn Bohrer
2009-02-10  3:38 ` Frank Mori Hess
2009-02-11 23:17   ` Shawn Bohrer
2009-02-11 23:34     ` Greg KH [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=20090211233411.GA21860@suse.de \
    --to=gregkh@suse.de \
    --cc=abbotti@mev.co.uk \
    --cc=ds@schleef.org \
    --cc=fmhess@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn.bohrer@ni.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox