public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: arnaud.quette@mgeups.com
To: Greg KH <greg@kroah.com>, Paul Stewart <stewart@wetlogic.net>,
	Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org,
	linux-usb-users@lists.sourceforge.net, opensource@mgeups.com,
	"Charles Lepple" <clepple@ghz.cc>
Subject: USB/HID UPS issue (was Re: USB scanner issue)
Date: Tue, 2 Dec 2003 14:18:25 +0100	[thread overview]
Message-ID: <C1256DF0.0048D122.00@gin123.ftgin.com> (raw)



Hi folks,

I take the opportunity of the previous discussion (USB
scanner obsolescence) to relaunch the one about hidddev.


On Mon, Dec 01, 2003 at 11:21:58AM -0800, Greg KH wrote:
> ...
> Can't you use xsane without the scanner kernel driver?  I thought the
> latest versions used libusb/usbfs to talk directly to the hardware.
> Because of this, the USB scanner driver is marked to be removed from the
> kernel sometime in the near future.

I'm thinking about doing the same with hiddev
as I'm facing new problems each times we solve
one! Currently, MGE devices won't work fine with
latest kernels (2.4 and 2.6). I've identified that
config/report descriptors are queried another time
at the end of HID enumeration, but the device doesn't
have time to answer (about 1,5 sec, instead of the
standard "5 sec" timeout). I've not found the cause
after digging, so I've directly gone to the next
step.

So I've setup the libHID project [1] to allow this
HID support, only used by UPSs at the moment (I've
seen passing some comments about USB radio and
other gadgets). But others complex HID devices are
welcomed.

My last problem is that I can't succeed in deactivating
hiddev at runtime (I've tryed various form of
"alias hiddev off" in modules.conf without success).
This still cause nasty side effect to the device.

So my question is: If we have userland HID support
through libHID (in the same way as libusb), is hiddev
still needed? I obviously don't talk about hid (core),
joy/keyb/mouse which are still needed...

Your feedback about all of that is welcomed.

Arnaud

[1] http://savannah.nongnu.org/projects/libhid
http://www.ghz.cc/~clepple/libHID/doc/html/index.html



             reply	other threads:[~2003-12-02 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-02 13:18 arnaud.quette [this message]
2003-12-09 18:21 ` USB/HID UPS issue (was Re: USB scanner issue) reg

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=C1256DF0.0048D122.00@gin123.ftgin.com \
    --to=arnaud.quette@mgeups.com \
    --cc=clepple@ghz.cc \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-users@lists.sourceforge.net \
    --cc=opensource@mgeups.com \
    --cc=stewart@wetlogic.net \
    --cc=vojtech@suse.cz \
    /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