public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: James Lamanna <jamesl@appliedminds.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Remove Phidget Blacklist if kernel driver is not selected
Date: Sun, 5 Sep 2004 17:20:23 -0700	[thread overview]
Message-ID: <20040906002023.GB16840@kroah.com> (raw)
In-Reply-To: <auto-000000530333@appliedminds.com>

On Sun, Aug 29, 2004 at 03:21:06PM -0700, James Lamanna wrote:
> This patch (compile-tested not runtime tested yet)
> is to remove the blacklisting of Phidgets 
> if the PhidgetServo kernel driver is not included
> in the kernel.
> (Right now it gets rid of all Phidget Blacklists, as more
> drivers are added I would expect they would be per-driver
> segmented).
> 
> It gets quite annoying to have to patch recent kernels 
> everytime to use userspace tools (libhid + libphidgets)
> as opposed to using the kernel driver, which cannot be
> used because of the HID blacklist.
> 
> I don't understand why a kernel driver for the
> PhidgetServo was included in the kernel. Wasn't the
> point of the HID layer to be able to present HID devices
> to userspace so that kernel drivers don't have to be 
> written for each and every device?
> It seems to be that the way to control a fairly simple
> device like the PhidgetServo is through userspace and
> the kernel shouldn't be bothered with the device control
> details.

Yes, you are correct.  I'm going to rip out the in-kernel version (Oh
no! Not again...) because this can all be done better and safer from
userspace.

But the hid blacklist is still correct, even when using the userspace
library, as the hid driver should never bind to these devices.

thanks,

greg k-h

      reply	other threads:[~2004-09-06  2:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-29 22:21 Remove Phidget Blacklist if kernel driver is not selected James Lamanna
2004-09-06  0:20 ` 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=20040906002023.GB16840@kroah.com \
    --to=greg@kroah.com \
    --cc=jamesl@appliedminds.com \
    --cc=linux-kernel@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