Hi,
On Sat, Aug 17, 2013 at 03:47:48PM +0200, Oleksij Rempel wrote:
> Am 17.08.2013 14:53, schrieb Forest Bond:
> >Hi,
> >
> >On Thu, Aug 15, 2013 at 03:31:40PM -0500, Dan Williams wrote:
> >>On Thu, 2013-08-15 at 10:47 -0500, Peter Hyman wrote:
> >>>
MA 1xEV-DO CnS
Reference" under a Creative Commons license. It has since disappeared from the
Internet, but private copies exist. ;) There are a large number of specifics
not covered by this document, but it does cover the basics of speaking CnS.
Actually, I recall you mentioning this docu
On Wed, Nov 07, 2012 at 03:02:39PM +0100, Jiri Kosina wrote:
> On Wed, 7 Nov 2012, Forest Bond wrote:
>
> > > /*
> > > * bla
> > > * bla
> > > */
> > >
> > > WBR, Sergei
> >
> > Thanks for the feedback. I had scanned t
Hi Sergei,
On Wed, Nov 07, 2012 at 03:29:16PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 06-11-2012 22:41, Forest Bond wrote:
>
> >From: Forest Bond
>
> >Previously, both usbhid and usbtouchscreen would bind to D-WAV devices
> >with class HID and protocol
From: Forest Bond
Previously, both usbhid and usbtouchscreen would bind to D-WAV devices
with class HID and protocol None, so they would be claimed by whichever
driver was loaded first. Some of these devices do in fact work with
usbhid, but not all of them do. OTOH they all work with
Hi Jiri,
On Mon, Nov 05, 2012 at 03:19:34PM +0100, Jiri Kosina wrote:
> On Fri, 2 Nov 2012, Forest Bond wrote:
>
> > We have some eGalax devices with class HID and protocol None that both
> > usbhid and usbtouchscreen will bind to, but we only want them bound to
> > us
blacklist these devices in usbhid to avoid binding to it if it is
loaded first. But usbhid should continue to handle eGalax devices with class
HID and protocol other than None (e.g. Mouse). They all have the same vendor
and product IDs, so we need to be able to blacklist on (VID, PID,
Hi Dmitry,
On Tue, Sep 04, 2012 at 11:07:04PM -0700, Dmitry Torokhov wrote:
> On Mon, Sep 03, 2012 at 01:33:50PM -0400, Forest Bond wrote:
> > From: Forest Bond
> >
> > Certain eGalax devices expose an interface with class HID and protocol
> > None. Some work wit
From: Forest Bond
Certain eGalax devices expose an interface with class HID and protocol
None. Some work with usbhid and some work with usbtouchscreen, but
there is no easy way to differentiate. Sending an eGalax diagnostic
packet seems to kick them all into using the right protocol for
From: Forest Bond
Certain eGalax devices expose an interface with class HID and protocol
None. Some work with usbhid and some work with usbtouchscreen, but
there is no easy way to differentiate. Sending an eGalax diagnostic
packet seems to kick them all into using the right protocol for
Hi Dmitry,
On Fri, Aug 31, 2012 at 04:10:47PM -0700, Dmitry Torokhov wrote:
> On Fri, Aug 31, 2012 at 06:53:53PM -0400, Forest Bond wrote:
> > Hi,
> >
> > On Fri, Aug 31, 2012 at 04:04:58PM -0400, Alan Stern wrote:
> > > On Fri, 31 A
X_PKT_TYPE_MASK) != EGALAX_PKT_TYPE_REPT)
@@ -1056,6 +1091,7 @@ static struct usbtouch_device_info usbtouch_dev_info[] = {
.process_pkt= usbtouch_process_multi,
.get_pkt_len= egalax_get_pkt_len,
.read_data = egalax_read_data,
+ .init = egalax_init,
},
#endif
Thanks,
Forest
--
Forest Bond
http://www.alittletooquiet.net
http://www.rapidrollout.com
signature.asc
Description: Digital signature
usb_rcvctrlpipe. Is this transfer meant to be IN or OUT?
The primary issue is that I'm a USB newb working on a deadline. ;)
My intention with this call was to send those three bytes out to the device. I
tested this in Python using a libusb binding. Oddly enough, the code as written
does in
From: Forest Bond
Certain eGalax devices expose an interface with class HID and protocol
None. Some work with usbhid and some work with usbtouchscreen, but
there is no easy way to differentiate. Sending an eGalax diagnostic
packet seems to kick them all into using the right protocol for
14 matches
Mail list logo
