public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lauri Niskanen <ape@ape3000.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: misc: Add driver for ALVA Nanoface
Date: Tue, 11 Nov 2014 17:03:44 +0900	[thread overview]
Message-ID: <20141111080344.GA18131@kroah.com> (raw)
In-Reply-To: <5461B7EF.2090308@ape3000.com>

On Tue, Nov 11, 2014 at 09:17:03AM +0200, Lauri Niskanen wrote:
> On 11/11/14 09:07, Greg Kroah-Hartman wrote:
> >Any reason this can't be a simple userspace program that writes the
> >needed command to the device using libusb instead of being a kernel
> >driver?  This seems like overkill for a kernel driver to me.
> 
> You are probably right. It indeed should be possible to do this in
> userspace. I thought that having a kernel driver would still be benefical
> since it adds plug-and-play availability for all Linux users without having
> to deal with userspace driver programs.

You can do that by just providing a package that adds a udev rule to run
your program when the device is seen.

Yes, it's not as "easy" as being in the main kernel tree, but we do like
to keep things out of the kernel that don't have to be in the kernel.
We removed a number of drivers like this about 10 years go for that very
reaason.

> You are far more experienced with these things than me, so I am happy to let
> you make the decision about whether to have a kernel driver or not.

I think a userspace program would be best.

sorry,

greg k-h

      reply	other threads:[~2014-11-11  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11  7:05 [PATCH] usb: misc: Add driver for ALVA Nanoface Lauri Niskanen
2014-11-11  7:07 ` Greg Kroah-Hartman
2014-11-11  7:17   ` Lauri Niskanen
2014-11-11  8:03     ` Greg Kroah-Hartman [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=20141111080344.GA18131@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ape@ape3000.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox