From owner-freebsd-usb@FreeBSD.ORG Sun Jun 8 14:44:17 2008 Return-Path: Delivered-To: FreeBSD-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C21A8106564A for ; Sun, 8 Jun 2008 14:44:17 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail7.sea5.speakeasy.net (mail7.sea5.speakeasy.net [69.17.117.9]) by mx1.freebsd.org (Postfix) with ESMTP id 98DD98FC0A for ; Sun, 8 Jun 2008 14:44:17 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: (qmail 24355 invoked from network); 8 Jun 2008 14:44:17 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail7.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 8 Jun 2008 14:44:17 -0000 Message-ID: <484BEE1C.8040903@telenix.org> Date: Sun, 08 Jun 2008 10:35:08 -0400 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: Hans Petter Selasky X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD USB List Subject: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 14:44:17 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hans, this is the big question, requires more thought, so if you don't have enough time on hand, give this a skip for a while. I'm CC'ing this to the FreeBSD-USB list, it's conceivable that I might get lucky there, too. This replaces my last usb question, because (even though I think the answer to that one confirms the utter insanity of the people who wrote the USB-HID spec), I have absolute confirmation of the fact that I cannot, in situations where the report descriptor has multiple sections ID'd by multiple report IDs, force the USB peripheral to send me the report ID that makes the best sense, and I must be satisfied with whatever the device sends me. That's ridiculous, but I wrote down the reference, just so I could look back at it and confirm to myself that I wasn't dreaming any of this. As a better illustration of that, my tablet has report IDs 7, 8, and 9. ID# 7 is the only one that matches well, but the device manufacturer has set it up to respond ONLY with report ID# 9. If I _could_ change that, I surely would, and I spent a LOT of time investigating until I absolutely found hard confirmation of the fact that I can't. If you get lucky and have a mfr sending all of the report ID's, you then can toss out the ones you don't like, but if they only send one (as in my case), well, you're screwed. What a stupid spec! My question now regards parsing of the input data using FreeBSD-supplied functions (which seems to me to mean things in libusbhid). Even though I can get hid_get_item and then hid_locate() to work for me, it's only by ignoring incorrect return values. Past that, the final point would be to use hid_get_data() to select and scale the data (which I gather through a read() of a scanned-for device such as uhid0) EXCEPT that I cannot get anything but a integer zero to return to me. Darn hid_get_data() just doesn't work. I'm probably missing some code assumption that didn't get illustrated in the man page. The only example I can get for it (the kernel code) is in dev/usb/ums.c, using the code in sys/dev/usb/hid.c, BUT the proto for this kernel code just looks _really_ different than the proto for the libusbhid functions. Headers and declarations are set up to make it really evil to try to use the kernel code in the user-mode code. I'm possibly going to have to adapt the kernel code to see if it can be forced to run in usermode. Does the libusbhid stuff work? Is there any sort of example, anywhere? Or, should I copy and adapt the kernel code? I could do the 3rd item, but it also seems like a really bad way to go. What's the right path here? Am I being stupid in missing the obvious? There's even one other question ... I'd heard some while back that someone else was preparing a separate implementation of the hid code. Do you know of anything like that, anything I could maybe replace the libusbhid code with? I really don't want to completely roll my own here, but so far, that's the only path open to me. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIS+4cz62J6PPcoOkRAgSXAJ9FQ8H2HvTBx95S6w0eP2vqdfm5JwCfenrR wOa4RxEDdbmj6+kAGohLaf0= =8pCH -----END PGP SIGNATURE----- From owner-freebsd-usb@FreeBSD.ORG Sun Jun 8 16:55:14 2008 Return-Path: Delivered-To: FreeBSD-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11689106564A for ; Sun, 8 Jun 2008 16:55:14 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.7]) by mx1.freebsd.org (Postfix) with ESMTP id D45AC8FC15 for ; Sun, 8 Jun 2008 16:55:13 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: (qmail 19318 invoked from network); 8 Jun 2008 16:55:13 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 8 Jun 2008 16:55:13 -0000 Message-ID: <484C0CCD.6060102@telenix.org> Date: Sun, 08 Jun 2008 12:46:05 -0400 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: FreeBSD USB List X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: libusbhid type bias X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 16:55:14 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been very slowly reading (and trying to run thru gdb) the item parsing and fetching/scaling code in libusbhid. I have to admit I have not yet fully figured out what's happening, but what I have seen, so far, are a couple of different comments that the spec isn't clear about the type (signed or unsigned) of the data. reading from /usr/src/lib/libusbhid/parse.c:209, "The spec is unclear if the data is signed or unsigned." That's only one of the comments I found, all saying about the same thing. Least I remember 2 of them. Well, let me first admit, right away, this is the spec from hell, and anyone saying this is a good spec (and I have seen such on the web) are just declaring themselves as not having enough experience reading specs. This IS the spec from hell. Nevertheless, it IS pretty clear about the type of data. I refer you to page 38 of the spec, top paragraph on the page: _HID spec excerpt, page 38 top: "Main items are used to either define or group certain types of data fields within a Report descriptor. There are two types of Main items: data and non-data. Data-type Main items are used to create a field within a report and include Input, Output, and Feature. Other items do not create fields and are subsequently referred to as non-data Main items." (end spec excerpt) At least for my data, all the data is definitely unsigned, and it's very important that this be followed. I don't think libusbhid is doing this (although I haven't yet been able to get hid_get_data() to return anything except 0 so far). However, realize (like I said) this is a horrible spec, and one could not blame anyone at all for misreading it. Even me. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFITAzNz62J6PPcoOkRAljKAJ9dWxTRN1EgKaTR4bEe48cG01UkiQCZAVCv j8bYvjYWGuvQ92TCMH5XM0o= =g59X -----END PGP SIGNATURE----- From owner-freebsd-usb@FreeBSD.ORG Sun Jun 8 19:31:24 2008 Return-Path: Delivered-To: FreeBSD-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 448F0106564A; Sun, 8 Jun 2008 19:31:24 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id 677DB8FC15; Sun, 8 Jun 2008 19:31:23 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=UlUzKLwsL7l1WSYqPADo3w==:17 a=sIWp1DIkpb0L2ECTMsIA:9 a=JC3dhOkaaBjt-6gSLAEA:7 a=ZS2F4cMFTkmgrsm7HRpPDvY_gk8A:4 a=50e4U0PicR4A:10 Received: from [62.113.132.30] (account mc467741@c2i.net [62.113.132.30] verified) by mailfe02.swip.net (CommuniGate Pro SMTP 5.1.13) with ESMTPA id 969191626; Sun, 08 Jun 2008 21:31:21 +0200 From: Hans Petter Selasky To: Chuck Robey Date: Sun, 8 Jun 2008 21:32:50 +0200 User-Agent: KMail/1.9.7 References: <484BEE1C.8040903@telenix.org> In-Reply-To: <484BEE1C.8040903@telenix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806082132.51357.hselasky@c2i.net> Cc: markus@freebsd.org, FreeBSD USB List Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 19:31:24 -0000 Hi Chuck, On Sunday 08 June 2008, Chuck Robey wrote: > Hans, this is the big question, requires more thought, so if you don't have > enough time on hand, give this a skip for a while. I'm CC'ing this to the > FreeBSD-USB list, it's conceivable that I might get lucky there, too. > > This replaces my last usb question, because (even though I think the answer > to that one confirms the utter insanity of the people who wrote the USB-HID > spec), I have absolute confirmation of the fact that I cannot, in > situations where the report descriptor has multiple sections ID'd by > multiple report IDs, force the USB peripheral to send me the report ID that > makes the best sense, and I must be satisfied with whatever the device > sends me. That's ridiculous, but I wrote down the reference, just so I > could look back at it and confirm to myself that I wasn't dreaming any of > this. > > As a better illustration of that, my tablet has report IDs 7, 8, and 9. > ID# 7 is the only one that matches well, but the device manufacturer has > set it up to respond ONLY with report ID# 9. If I _could_ change that, I > surely would, and I spent a LOT of time investigating until I absolutely > found hard confirmation of the fact that I can't. If you get lucky and > have a mfr sending all of the report ID's, you then can toss out the ones > you don't like, but if they only send one (as in my case), well, you're > screwed. What a stupid spec! You mean if you can set another USB configuration ? > > My question now regards parsing of the input data using FreeBSD-supplied > functions (which seems to me to mean things in libusbhid). Even though I > can get hid_get_item and then hid_locate() to work for me, it's only by > ignoring incorrect return values. Past that, the final point would be to > use hid_get_data() to select and scale the data (which I gather through a > read() of a scanned-for device such as uhid0) EXCEPT that I cannot get > anything but a integer zero to return to me. Have you looked into "hid_get_data()" and stepped through it? > > Darn hid_get_data() just doesn't work. I'm probably missing some code > assumption that didn't get illustrated in the man page. The only example I > can get for it (the kernel code) is in dev/usb/ums.c, using the code in > sys/dev/usb/hid.c, BUT the proto for this kernel code just looks _really_ > different than the proto for the libusbhid functions. Headers and > declarations are set up to make it really evil to try to use the kernel > code in the user-mode code. I'm possibly going to have to adapt the kernel > code to see if it can be forced to run in usermode. > > Does the libusbhid stuff work? Is there any sort of example, anywhere? > Or, should I copy and adapt the kernel code? I could do the 3rd item, but > it also seems like a really bad way to go. I never used it. I probably will one day and it seems like there are some bugs that needs to be fixed according to you :-) > > What's the right path here? Am I being stupid in missing the obvious? > > > There's even one other question ... I'd heard some while back that someone > else was preparing a separate implementation of the hid code. Do you know > of anything like that, anything I could maybe replace the libusbhid code > with? That was "Markus Brueffer" I think. > > I really don't want to completely roll my own here, but so far, that's the > only path open to me. --HPS From owner-freebsd-usb@FreeBSD.ORG Sun Jun 8 21:02:50 2008 Return-Path: Delivered-To: FreeBSD-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10C031065680 for ; Sun, 8 Jun 2008 21:02:50 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail7.sea5.speakeasy.net (mail7.sea5.speakeasy.net [69.17.117.9]) by mx1.freebsd.org (Postfix) with ESMTP id DC4EA8FC27 for ; Sun, 8 Jun 2008 21:02:49 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: (qmail 13303 invoked from network); 8 Jun 2008 21:02:49 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail7.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 8 Jun 2008 21:02:49 -0000 Message-ID: <484C46D6.6050908@telenix.org> Date: Sun, 08 Jun 2008 16:53:42 -0400 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: Hans Petter Selasky References: <484BEE1C.8040903@telenix.org> <200806082132.51357.hselasky@c2i.net> In-Reply-To: <200806082132.51357.hselasky@c2i.net> X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: markus@freebsd.org, FreeBSD USB List Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 21:02:50 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hans Petter Selasky wrote: > Hi Chuck, > > On Sunday 08 June 2008, Chuck Robey wrote: >> Hans, this is the big question, requires more thought, so if you don't have >> enough time on hand, give this a skip for a while. I'm CC'ing this to the >> FreeBSD-USB list, it's conceivable that I might get lucky there, too. >> >> This replaces my last usb question, because (even though I think the answer >> to that one confirms the utter insanity of the people who wrote the USB-HID >> spec), I have absolute confirmation of the fact that I cannot, in >> situations where the report descriptor has multiple sections ID'd by >> multiple report IDs, force the USB peripheral to send me the report ID that >> makes the best sense, and I must be satisfied with whatever the device >> sends me. That's ridiculous, but I wrote down the reference, just so I >> could look back at it and confirm to myself that I wasn't dreaming any of >> this. >> >> As a better illustration of that, my tablet has report IDs 7, 8, and 9. >> ID# 7 is the only one that matches well, but the device manufacturer has >> set it up to respond ONLY with report ID# 9. If I _could_ change that, I >> surely would, and I spent a LOT of time investigating until I absolutely >> found hard confirmation of the fact that I can't. If you get lucky and >> have a mfr sending all of the report ID's, you then can toss out the ones >> you don't like, but if they only send one (as in my case), well, you're >> screwed. What a stupid spec! > > You mean if you can set another USB configuration ? That's what I'm saying SHOULD be possible, but it isn't. Why have report ID's if you can't use them? That's why I say it's loony. The general response I have had is, sometimes multiple reports are sent, but that's contradicted by most of the stuff I've read, so I disbelieve it... hid reports are limited to 8 bytes, so thinking that more than one report is to be sent sounds wrong. I was so incensed when I found the truth, I memorized the page I read it in, so if you feel like checking me, do you have a copy of that pdf book USB_Complete_3rdEdition.pdf ?? If you don't, you really should, I could send you a copy, it's freely available on the net. Anyhow, the stuff on page 363 is what I finally tripped over. It took me quite a while to find it, and it says flatly that the transmitted report (if more than 1 is defined in the report descriptor) can't be changed. Mine always reports ID#9, and since my ID#7 is far better, I wanted that one, but I guess I can live with it. >> My question now regards parsing of the input data using FreeBSD-supplied >> functions (which seems to me to mean things in libusbhid). Even though I >> can get hid_get_item and then hid_locate() to work for me, it's only by >> ignoring incorrect return values. Past that, the final point would be to >> use hid_get_data() to select and scale the data (which I gather through a >> read() of a scanned-for device such as uhid0) EXCEPT that I cannot get >> anything but a integer zero to return to me. > > Have you looked into "hid_get_data()" and stepped through it? >> Darn hid_get_data() just doesn't work. I'm probably missing some code >> assumption that didn't get illustrated in the man page. The only example I >> can get for it (the kernel code) is in dev/usb/ums.c, using the code in >> sys/dev/usb/hid.c, BUT the proto for this kernel code just looks _really_ >> different than the proto for the libusbhid functions. Headers and >> declarations are set up to make it really evil to try to use the kernel >> code in the user-mode code. I'm possibly going to have to adapt the kernel >> code to see if it can be forced to run in usermode. >> >> Does the libusbhid stuff work? Is there any sort of example, anywhere? >> Or, should I copy and adapt the kernel code? I could do the 3rd item, but >> it also seems like a really bad way to go. > > I never used it. I probably will one day and it seems like there are some bugs > that needs to be fixed according to you :-) I don't trust myself, I do make silly errors. My test program is so completely screwed up because I have experimented rather freely, I would really be embarrassed to show it to you, but I can get nothing returned excepting a zero from hid_locate (although it DOES seem to work anyhow) and nothing except zero from hid_get_data(), but since that's where it's supposed to return data, it is more than a little upsetting. Beyond that (as I recently posted on the usb list) I have found what looks to me to be another oddity of libusbhid: there are some comments about the type of data (signed or unsigned) being uncertain, however, looking at the HID spec, top paragraph of page 38, the type of data is clearly delineated. The libusbhid seems to have a bias toward signed, but all the data in my device is unsigned. Last item is that using hid_locate to grab the hid_item_t for each item, and so I looked at the "pos" field which is supposed to return the bit offset of the data. In using pure inspection, I have determined that the first byte has 3 bits in the bottom given to buttons, the rest there are fillers, then the following 3 byte pairs (shorts) are each X, Y, and tip pressure. This doesn't agree with the stuff returned in the pos field, so I can't even cheat and read the data, and use it myself... What I think I can, must do, is to use the libusbhid to parse the report descriptor, and use that data directly to derive my own bit offsets, and use my own functions to parse out and scale the data. I would rather use the stuff in libusbhid, but I can't get anywhere with it. That's unless I can get someone to clue me in. You say Markus Brueffer is writing another libusbhid? Hmm, ok, I appreciate your CC'ing him.... or, I really suspect I've bothered, overly bothered, enough folks at this point, and maybe what I need to write at this point is small enough so that I could just figure it out myself. It won't look TOO ugly now that I have the real problem, tha parsing, really taken care of. Anyhow, if you don't really have any experience with libusbhid, or maybe could tell me I'm wrong about being able to set the report ID, then I really guess I have to be happy with where I'm at. Thanks for listening to me. > >> What's the right path here? Am I being stupid in missing the obvious? >> >> >> There's even one other question ... I'd heard some while back that someone >> else was preparing a separate implementation of the hid code. Do you know >> of anything like that, anything I could maybe replace the libusbhid code >> with? > > That was "Markus Brueffer" I think. > >> I really don't want to completely roll my own here, but so far, that's the >> only path open to me. > > --HPS -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFITEbWz62J6PPcoOkRAgXgAJsHrYdP6Pxr6qei9cvHmgg6dCysdACgpHBz 92MwqpKRQl4ge3rwi0GaTcQ= =XiZQ -----END PGP SIGNATURE----- From owner-freebsd-usb@FreeBSD.ORG Sun Jun 8 21:09:38 2008 Return-Path: Delivered-To: FreeBSD-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 101C9106566C; Sun, 8 Jun 2008 21:09:38 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id B03818FC20; Sun, 8 Jun 2008 21:09:36 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=UlUzKLwsL7l1WSYqPADo3w==:17 a=OjL5efmLpeUuAzQxxMQA:9 a=LqE2GmgLi8lQSo1KvhwA:7 a=Qw_YYm2e8Jokuysy-0mJSCIgbrsA:4 a=LY0hPdMaydYA:10 Received: from [62.113.132.30] (account mc467741@c2i.net [62.113.132.30] verified) by mailfe02.swip.net (CommuniGate Pro SMTP 5.1.13) with ESMTPA id 969261740; Sun, 08 Jun 2008 23:09:26 +0200 From: Hans Petter Selasky To: Chuck Robey Date: Sun, 8 Jun 2008 23:10:55 +0200 User-Agent: KMail/1.9.7 References: <484BEE1C.8040903@telenix.org> <200806082132.51357.hselasky@c2i.net> <484C46D6.6050908@telenix.org> In-Reply-To: <484C46D6.6050908@telenix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806082310.56920.hselasky@c2i.net> Cc: markus@freebsd.org, FreeBSD USB List Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 21:09:38 -0000 On Sunday 08 June 2008, Chuck Robey wrote: > Hans Petter Selasky wrote: > > Hi Chuck, > > > > On Sunday 08 June 2008, Chuck Robey wrote: > >> Hans, this is the big question, requires more thought, so if you don't > >> have enough time on hand, give this a skip for a while. I'm CC'ing this > >> to the FreeBSD-USB list, it's conceivable that I might get lucky there, > >> too. > >> > >> This replaces my last usb question, because (even though I think the > >> answer to that one confirms the utter insanity of the people who wrote > >> the USB-HID spec), I have absolute confirmation of the fact that I > >> cannot, in situations where the report descriptor has multiple sections > >> ID'd by multiple report IDs, force the USB peripheral to send me the > >> report ID that makes the best sense, and I must be satisfied with > >> whatever the device sends me. That's ridiculous, but I wrote down the > >> reference, just so I could look back at it and confirm to myself that I > >> wasn't dreaming any of this. > >> > >> As a better illustration of that, my tablet has report IDs 7, 8, and 9. > >> ID# 7 is the only one that matches well, but the device manufacturer has > >> set it up to respond ONLY with report ID# 9. If I _could_ change that, > >> I surely would, and I spent a LOT of time investigating until I > >> absolutely found hard confirmation of the fact that I can't. If you get > >> lucky and have a mfr sending all of the report ID's, you then can toss > >> out the ones you don't like, but if they only send one (as in my case), > >> well, you're screwed. What a stupid spec! > > > > You mean if you can set another USB configuration ? > > That's what I'm saying SHOULD be possible, but it isn't. There will soon be a utility that can do this, so that you can run: usbconfig -u ugen0 -c 1 for example to select configuration index 1 for your device. Please note that there will be one ugen device for every USB device present in the future! And I'm in the future :-) --HPS From owner-freebsd-usb@FreeBSD.ORG Sun Jun 8 23:40:03 2008 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA1CA10656AD for ; Sun, 8 Jun 2008 23:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B54FD8FC30 for ; Sun, 8 Jun 2008 23:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m58Ne3wQ070871 for ; Sun, 8 Jun 2008 23:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m58Ne3gc070870; Sun, 8 Jun 2008 23:40:03 GMT (envelope-from gnats) Date: Sun, 8 Jun 2008 23:40:03 GMT Message-Id: <200806082340.m58Ne3gc070870@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Tim McCormick Cc: Subject: Re: usb/123509: [umass] continuous reset Samsung SGH-G600 phone X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tim McCormick List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 23:40:04 -0000 The following reply was made to PR usb/123509; it has been noted by GNATS. From: Tim McCormick To: bug-followup@freebsd.org, tim@pcbsd.org Cc: Subject: Re: usb/123509: [umass] continuous reset Samsung SGH-G600 phone Date: Mon, 9 Jun 2008 00:06:15 +0100 This is fixed in 7.0-STABLE. This bug report can be closed :) From owner-freebsd-usb@FreeBSD.ORG Mon Jun 9 02:02:54 2008 Return-Path: Delivered-To: FreeBSD-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 903031065677 for ; Mon, 9 Jun 2008 02:02:54 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.5]) by mx1.freebsd.org (Postfix) with ESMTP id 693828FC20 for ; Mon, 9 Jun 2008 02:02:54 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: (qmail 17055 invoked from network); 9 Jun 2008 02:02:53 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 9 Jun 2008 02:02:53 -0000 Message-ID: <484C8D2B.40404@telenix.org> Date: Sun, 08 Jun 2008 21:53:47 -0400 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: Hans Petter Selasky References: <484BEE1C.8040903@telenix.org> <200806082132.51357.hselasky@c2i.net> <484C46D6.6050908@telenix.org> <200806082310.56920.hselasky@c2i.net> In-Reply-To: <200806082310.56920.hselasky@c2i.net> X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: markus@freebsd.org, FreeBSD USB List Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 02:02:54 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hans Petter Selasky wrote: > On Sunday 08 June 2008, Chuck Robey wrote: >> Hans Petter Selasky wrote: >>> Hi Chuck, >>> >>> On Sunday 08 June 2008, Chuck Robey wrote: >>>> Hans, this is the big question, requires more thought, so if you don't >>>> have enough time on hand, give this a skip for a while. I'm CC'ing this >>>> to the FreeBSD-USB list, it's conceivable that I might get lucky there, >>>> too. >>>> >>>> This replaces my last usb question, because (even though I think the >>>> answer to that one confirms the utter insanity of the people who wrote >>>> the USB-HID spec), I have absolute confirmation of the fact that I >>>> cannot, in situations where the report descriptor has multiple sections >>>> ID'd by multiple report IDs, force the USB peripheral to send me the >>>> report ID that makes the best sense, and I must be satisfied with >>>> whatever the device sends me. That's ridiculous, but I wrote down the >>>> reference, just so I could look back at it and confirm to myself that I >>>> wasn't dreaming any of this. >>>> >>>> As a better illustration of that, my tablet has report IDs 7, 8, and 9. >>>> ID# 7 is the only one that matches well, but the device manufacturer has >>>> set it up to respond ONLY with report ID# 9. If I _could_ change that, >>>> I surely would, and I spent a LOT of time investigating until I >>>> absolutely found hard confirmation of the fact that I can't. If you get >>>> lucky and have a mfr sending all of the report ID's, you then can toss >>>> out the ones you don't like, but if they only send one (as in my case), >>>> well, you're screwed. What a stupid spec! >>> You mean if you can set another USB configuration ? >> That's what I'm saying SHOULD be possible, but it isn't. > > There will soon be a utility that can do this, so that you can run: > > usbconfig -u ugen0 -c 1 > > for example to select configuration index 1 for your device. Please note that > there will be one ugen device for every USB device present in the future! And > I'm in the future :-) Most likely possibility: you (like one other person already) is misinterpreting what I'm talking about. Being that I tend to be a bit loose about terminology sometimes (and sometimes too often) it's likely my fault. Just to see if I can run over what the other person meant, I'm very much NOT talking about the thing that the USB HID spec calls a "report type", one example being the input type, or feature, etc. I am talking about a subset of HID report descriptors that are written with multiple "report ID" fields (see HID spec page 36), like the one with my UC-Logic graphic tablet, which is written with report IDs 7, 8, and 9. Most HID devices (and only HID devices have these report descriptors anyhow) have only a single report ID, and so they don't actually have the explicit report ID line (they let it default to zero). Other devices, which DO have multiple report ID's, have small enough reports to have multiple reports fit in a single data report (those are limited by spec to 8 bytes). The report ID, for ones with multiple ID's, forms the first byte of the data report. My tablet reports 0x09 as the first byte, I wish it would report a 0x07. The reference I gave you is unmistably clear in saying that it is not possible to cause a device to change the report ID's it sends. My device needs 7 data bytes, 8 with the leading report ID, which is VERY unfortunately an 0x09, not the 0x07 which would really be optimal. Another possibility occurs, though: my reference, the USB Complete book, page 363, is just plain wrong. That possibility is what fuels this email. Maybe there IS a way ... God knows, the USB HID spec is such an incredible POS that getting it wrong can't even be blamed on an otherwise very good programmer. I have read many specs in my life, never seen one even close to being as bad as that one (although I admit most of the specs I have dealt with were communications oriented, I was mostly a commuications engr.) If you have any reference to any method which might exist to send any data pattern at all to a USB HID device, to cause it to change the report ID coding (scaling, etc) that it follows, I sure would appreciate you telling me that. Don't even need to tell me how, I will read myself (although I would like that, I am so desperate to get such, I would really appreciate it in any form I could get it, whatsoever). > > --HPS > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFITI0rz62J6PPcoOkRAoK6AKCPJJX0SJWjS/5grGbPSYg6tCBqZACfR5wY 8XasXa0B86VIMP4A/rBjR7A= =0CBd -----END PGP SIGNATURE----- From owner-freebsd-usb@FreeBSD.ORG Mon Jun 9 04:00:39 2008 Return-Path: Delivered-To: FreeBSD-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6F8A1065677 for ; Mon, 9 Jun 2008 04:00:39 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 9327C8FC16 for ; Mon, 9 Jun 2008 04:00:39 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 30CF31A4D82; Sun, 8 Jun 2008 20:42:52 -0700 (PDT) Date: Sun, 8 Jun 2008 20:42:52 -0700 From: Alfred Perlstein To: Hans Petter Selasky Message-ID: <20080609034252.GT48790@elvis.mu.org> References: <484BEE1C.8040903@telenix.org> <200806082132.51357.hselasky@c2i.net> <484C46D6.6050908@telenix.org> <200806082310.56920.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200806082310.56920.hselasky@c2i.net> User-Agent: Mutt/1.4.2.3i Cc: markus@freebsd.org, FreeBSD USB List Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 04:00:39 -0000 * Hans Petter Selasky [080608 14:09] wrote: > > > > > > You mean if you can set another USB configuration ? > > > > That's what I'm saying SHOULD be possible, but it isn't. > > There will soon be a utility that can do this, so that you can run: > > usbconfig -u ugen0 -c 1 > > for example to select configuration index 1 for your device. Please note that > there will be one ugen device for every USB device present in the future! And > I'm in the future :-) > This is so exciting!!! :) Multi-function usb devices?!?! :) Sending printer controls through ugen to ulpt!:) -- - Alfred Perlstein From owner-freebsd-usb@FreeBSD.ORG Mon Jun 9 05:31:50 2008 Return-Path: Delivered-To: FreeBSD-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A74011065676 for ; Mon, 9 Jun 2008 05:31:50 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.7]) by mx1.freebsd.org (Postfix) with ESMTP id 8037D8FC26 for ; Mon, 9 Jun 2008 05:31:50 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: (qmail 2838 invoked from network); 9 Jun 2008 05:31:49 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 9 Jun 2008 05:31:49 -0000 Message-ID: <484CBE24.5030704@telenix.org> Date: Mon, 09 Jun 2008 01:22:44 -0400 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: Alfred Perlstein References: <484BEE1C.8040903@telenix.org> <200806082132.51357.hselasky@c2i.net> <484C46D6.6050908@telenix.org> <200806082310.56920.hselasky@c2i.net> <20080609034252.GT48790@elvis.mu.org> In-Reply-To: <20080609034252.GT48790@elvis.mu.org> X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: markus@freebsd.org, FreeBSD USB List Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 05:31:50 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alfred Perlstein wrote: > * Hans Petter Selasky [080608 14:09] wrote: >>>> You mean if you can set another USB configuration ? >>> That's what I'm saying SHOULD be possible, but it isn't. >> There will soon be a utility that can do this, so that you can run: >> >> usbconfig -u ugen0 -c 1 >> >> for example to select configuration index 1 for your device. Please note that >> there will be one ugen device for every USB device present in the future! And >> I'm in the future :-) >> > > This is so exciting!!! :) Multi-function usb devices?!?! :) > Sending printer controls through ugen to ulpt!:) I do admit to be extremely curious about it. Since my own current focus is HID, if I assume you weren't talking HID that whole time, then what you were saying was more than a little bit great. In my own direction, I have finally decided to neaten up all of my experimental code, and I found while digging about here and there, that if you excuse some error returns as being wrong, it's only the actual data functions that are wacky, so I've begun rewriting itfor my own project, which means it takes a struct data_item and basically performs a hid_locate (finding the code section for each particular item, and the last piece (hid_get_data() is supposed to used that generated data, and yield the actual data items for use in performing screen acrobatics. The part I need to supply, I can't see any reason I could supply a part that looks very much like what was therer to begin with (excepting it works). You need to realize me coding religion, biasing me terrifically toward safer, more easily to troubleshoot code. To me, it's _WAY_ more important that your code be obvious in function, rather than fast or elegant. My own personal mantra is "Maintainability above all else". I actually think I'm going to be able to do that this time, and nice people have let me do this, not undercut me (and when you go this slowly, I really, really appreciate not being coded into extinction. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFITL4kz62J6PPcoOkRAu1GAKCj4Vz1kCHiIXrZS336C3bGumwvAwCgl7lP KxsGdaPIoK+cnhT0ccYGmAk= =AHH2 -----END PGP SIGNATURE----- From owner-freebsd-usb@FreeBSD.ORG Mon Jun 9 05:37:45 2008 Return-Path: Delivered-To: FreeBSD-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49213106566C for ; Mon, 9 Jun 2008 05:37:45 +0000 (UTC) (envelope-from xiaofanc@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by mx1.freebsd.org (Postfix) with ESMTP id 18D4E8FC0A for ; Mon, 9 Jun 2008 05:37:45 +0000 (UTC) (envelope-from xiaofanc@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2322231rvf.43 for ; Sun, 08 Jun 2008 22:37:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=XuVHbGmbpNnq+8bTvTBXEFsTvmbVZy+NfbHPVSRkPys=; b=bZsG3FW+43GpQJ3k2/mq/F259dnms3djXpIVL+TYjndUfGW77luMJEVVW/xbHF/Ov9 ZMt4BCy1Z1KQLU/rrrr2r5joF4G/+++4ZDrH5yPUC0u9vSxzdrsDeOFyU19buY7fZxwx 4Xt8qzSmoVZCWm5Nl+5KcECS+1rLRmxuEh+Is= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=JNLNMK+al7TTMVYI/eUjGuYApmJCGJgzTzXr7xplnD3SZtv4k3IOV/z1TqUdsDYhNV v5dxXv3ae94J88gzo07nt5CBJynrhFJ3F3oECQi7H5a2EbmopoeFOLOlU9RaEbpZgguB utpK56gK4sY2Ex1aqF0EXCGDHf2SFnH585Je4= Received: by 10.140.249.20 with SMTP id w20mr1812874rvh.21.1212988245741; Sun, 08 Jun 2008 22:10:45 -0700 (PDT) Received: by 10.141.113.12 with HTTP; Sun, 8 Jun 2008 22:10:45 -0700 (PDT) Message-ID: Date: Mon, 9 Jun 2008 13:10:45 +0800 From: "Xiaofan Chen" To: "Hans Petter Selasky" In-Reply-To: <200806082310.56920.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <484BEE1C.8040903@telenix.org> <200806082132.51357.hselasky@c2i.net> <484C46D6.6050908@telenix.org> <200806082310.56920.hselasky@c2i.net> Cc: FreeBSD USB List Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 05:37:45 -0000 On 6/9/08, Hans Petter Selasky wrote: > There will soon be a utility that can do this, so that you can run: > > usbconfig -u ugen0 -c 1 > > for example to select configuration index 1 for your device. Please note that > there will be one ugen device for every USB device present in the future! And > I'm in the future :-) That would be great. In that case, you might want to look at the new libusb-1.0 and ported it to FreeBSD. The new libusb-1.0 supports isochronous transfer and asynchronous I/O. Right now it only works under Linux. It is under beta now but the API should be mostly stable alreay. http://www.reactivated.net/weblog/archives/2008/05/libusb-10-enters-beta/ http://libusb.sourceforge.net/api-1.0/ Xiaofan From owner-freebsd-usb@FreeBSD.ORG Mon Jun 9 11:07:08 2008 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 772F91065670 for ; Mon, 9 Jun 2008 11:07:08 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 526078FC1A for ; Mon, 9 Jun 2008 11:07:08 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m59B78nQ070919 for ; Mon, 9 Jun 2008 11:07:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m59B77Hh070915 for freebsd-usb@FreeBSD.org; Mon, 9 Jun 2008 11:07:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 Jun 2008 11:07:07 GMT Message-Id: <200806091107.m59B77Hh070915@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-usb@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 11:07:08 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa o usb/91629 usb usbd_abort_pipe() may result in infinite loop 2 problems total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/46371 usb USB controller cannot be initialized on IBM Netfinity o bin/57255 usb usbd(8) and multi-function devices o usb/63621 usb [umass] [panic] USB MemoryStick Reader stalls/crashes o usb/69006 usb [usbdevs] [patch] Apple Cinema Display hangs USB ports o usb/71155 usb [ulpt] misbehaving usb-printer hangs processes, causes o usb/73307 usb [panic] Kernel panics on USB disconnect o usb/74771 usb [umass] [hang] mounting write-protected umass device a o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o usb/75797 usb [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c o usb/76395 usb [uhci] USB printer does not work, usbdevs says "addr 0 o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa a usb/79656 usb [ehci] RHSC interrupts lost o usb/79722 usb [ehci] wrong alignments in ehci.h o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80829 usb [modules] [panic] possible panic when loading USB-modu o usb/80862 usb [patch] USB locking issues: missing some Giant calls o usb/82350 usb [ucom] [panic] null pointer dereference in USB stack o usb/82520 usb [udbp] [reboot] Reboot when USL101 connected s usb/82569 usb [umass] [panic] USB mass storage plug/unplug causes sy o usb/82660 usb [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic o usb/83504 usb [kernel] [patch] SpeedTouch USB stop working on recent o usb/83563 usb [umass] [panic] Page Fault while detaching Mpman Usb d o usb/83677 usb [usb] [request] usb controller often not detected (Sun o usb/83756 usb [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/86767 usb [umass] [patch] bogus "slice starts beyond end of the o usb/88743 usb [hang] [regression] USB makes kernel hang at boot (reg s usb/89003 usb [request] LaCie Firewire drive not properly supported o usb/89954 usb [umass] [panic] USB Disk driver race condition? o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas o usb/91238 usb [umass] USB tape unit fails to write a second tape fil o usb/91283 usb [boot] [regression] booting very slow with usb devices o usb/91538 usb [ulpt] [patch] Unable to print to EPSON CX3500 o usb/91906 usb [ehci] [hang] FreeBSD hangs while booting with USB leg o usb/92052 usb [ulpt] usbd causes defunct process with busy file-hand o usb/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92142 usb [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w o usb/93408 usb [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes o usb/93828 usb [ohci] [panic] ohci causes panic on boot (HP Pavillion o usb/94384 usb [panic] kernel panic with usb2 hardware o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94897 usb [panic] Kernel Panic when cleanly unmounting USB disk s usb/95348 usb [keyboard] USB keyboard unplug causes noise on screen o usb/95562 usb [umass] Write Stress in USB Mass drive causes "vinvalb s usb/95636 usb [umass] [boot] 5 minute delay at boot when using VT620 s usb/96120 usb [ums] [request] USB mouse not always detected o usb/96224 usb [usb] [msdosfs] mount_msdosfs cause page fault in sync o usb/96457 usb [umass] [panic] fatback on umass = reboot s usb/97286 usb [mouse] [request] MS Wireless Intellimouse Explorer 2. o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar o usb/101096 usb [ural] [panic] USB WLAN occasionally causes kernel-pan o usb/101448 usb [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O o usb/101752 usb [umass] [panic] 6.1-RELEASE kernel panic on usb device o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work f usb/102096 usb [patch] usbd(8) does not handle multiple devices in on o usb/103025 usb [uhub] [panic] wrong detection of USB device for FreeB o usb/104292 usb [umass] [hang] system lockup on forced umount of usb-s o usb/104830 usb [umass] system crashes when copying data to umass devi o usb/105186 usb [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106648 usb [umass] [hang] USB Floppy on D1950 10 min Hang on Inse s usb/106832 usb USB HP printer is not detected by kernel when ACPI ena o usb/107248 usb [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP o usb/107446 usb [umass] umass problems (usb and fw disks) o usb/107827 usb [ohci] [panic] ohci_add_done addr not found o usb/107848 usb [umass] [request] cannot access Samsung flash disk o usb/107924 usb [patch] usbd(8) does not call detach o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/109397 usb [panic] on boot from USB flash o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110988 usb [umass] [patch] Handling of quirk IGNORE_RESIDUE is um o usb/111753 usb [uhid] [panic] Replicable system panic involving UHID s usb/112568 usb [umass] [request] USB mode may wrong when mounting Pla o usb/112631 usb [panic] Problem with SONY DSC-S80 camera on umount o usb/112640 usb [usb] [hang] Kernel freezes when writing a file to an s usb/113629 usb [ukbd] Dropped USB keyboard events on Dell Latitude D6 o usb/113672 usb [ehci] [panic] Kernel panic with AEWIN CB6971 s usb/113977 usb [request] Need a way to set mode of USB disk's write c o usb/114310 usb [libusb] [patch] [panic] USB hub attachment panics ker o usb/114682 usb [umass] generic USB media-card reader unusable o kern/114780 usb [uplcom] [panic] Panics while stress testing the uplco o usb/115298 usb [ulpt] [panic] Turning off USB printer panics kernel o usb/116561 usb [umodem] [panic] RELENG_6 umodem panic "trying to slee o usb/116699 usb [usbhid] USB HID devices do not initialize at system b o usb/116947 usb [ukbd] [patch] enable boot protocol on the USB keyboar o usb/117200 usb [ugen] ugen0 prints strange string on attach if detach o usb/117313 usb [umass] [panic] panic on usb camera insertion o usb/117613 usb [uhci] [irq] uhci interrupt storm & USB leaked memory o usb/117946 usb [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE o usb/117955 usb [umass] [panic] inserting minolta dimage a2 crashes OS o usb/118140 usb [ucom] [patch] quick hack for ucom to get it behave wi o usb/118141 usb [ucom] usb serial and nokia phones ucomreadcb ucomread o usb/118353 usb [panic] [ppp] repeatable kernel panic during ppp(4) se o usb/118391 usb [usbdevs] [patch] Add uscanner ID for Epson CX4800 o usb/118480 usb [umass] Timeout in USB mass storage freezes vfs layer o usb/119201 usb [cam] [patch] Quirks for Olympus FE-210 camera, LG and o usb/119481 usb [hang] FreeBSD not responding after connecting USB-Mas o usb/119509 usb USB flaky on Dell Optiplex 755 o usb/119513 usb [irq] inserting dlink dwl-g630 wireless card results i o usb/119977 usb [ums] Mouse does not work in a Cherry-USB keyboard/mou o usb/120017 usb [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk o usb/120034 usb [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 o usb/120283 usb [panic] Automation reboot with wireless keyboard & mou o usb/120321 usb [hang] System hangs when transferring data to WD MyBoo o usb/120729 usb [panic] fault while in kernel mode with connecting USB o usb/120786 usb Kernel panic when forced umount of a dettached USB Har f usb/120873 usb [zyd] [panic] if_zyd and if_rum panic in usb_transfer_ o usb/121232 usb remove PCCARD rebooted system o usb/121275 usb [boot] FreeBSD fails to boot with usb legacy support e o usb/121474 usb [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard o usb/121708 usb [keyboard] nforce 650i mobo w/ usb keyboard infinite k o usb/121734 usb [ugen] ugen HP1022 printer device not working since up o usb/121755 usb [ohci] [patch] Fix panic after ohci/uhub cardbus devic o usb/121861 usb [keyboard] Don't work Fn keys on USB Microsoft Natural o usb/122483 usb [panic] [ulpt] Repeatable panic in 7.0-STABLE o usb/122539 usb [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci o usb/122905 usb [ubsa] [patch] add Huawei E220 to ubsa o kern/123510 usb [ums] Mouse Wheel Fails to Work [regression] o usb/123690 usb Panic on USB device insertion when usb loaded as a mod o usb/123714 usb Panic when hald-storage-probe runs with umass device i 130 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem o usb/40948 usb [umass] [request] USB HP CDW8200 does not work s usb/51958 usb [urio] [patch] update for urio driver s usb/52026 usb [usb] [request] umass driver support for InSystem ISD2 o usb/59698 usb [keyboard] [patch] Rework of ukbd HID to AT code trans s usb/62257 usb [umass] [request] card reader UCR-61S2B is only half-s o usb/66547 usb [ucom] Palm Tungsten T USB does not initialize correct o usb/68232 usb [ugen] [patch] ugen(4) isochronous handling correction o usb/70523 usb [umct] [patch] umct sending/receiving wrong characters o usb/71280 usb [aue] aue0 device (linksys usb100tx) doesn't work in 1 o usb/71416 usb [ugen] Cryptoflex e-gate USB token (ugen0) detach is n o usb/71417 usb [ugen] Cryptoflex e-gate USB token (ugen0) communicati o usb/71455 usb [umass] Slow USB umass performance of 5.3 s usb/72733 usb [ucom] [request] Kyocera 7135 Palm OS connection probl o usb/74211 usb [umass] USB flash drive causes CAM status 0x4 on 4.10R a usb/74453 usb [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75800 usb [ucom] ucom1: init failed STALLED error in time of syn s usb/75928 usb [umass] [request] Cytronix SmartMedia card (SMC) reade o usb/76461 usb [umass] disklabel of umass(4)-CAM(4)-da(4) not used by o usb/76653 usb [umass] [patch] Problem with Asahi Optical usb device o usb/76732 usb Mouse problems with USB KVM Switch o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/80774 usb [patch] have "usbd_find_desc" in line with the other " s usb/80776 usb [udav] [request] UDAV device driver shouldn't use usb_ s usb/80777 usb [request] usb_rem_task() should wait for callback to c o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80935 usb [uvisor] [patch] uvisor.c is not work with CLIE TH55. o usb/81621 usb [ehci] [hang] external hd hangs under load on ehci o usb/83863 usb [ugen] Communication problem between opensc/openct via s usb/85067 usb [uscanner] Cannot attach ScanJet 4300C to usb device o usb/86298 usb [mouse] Known good USB mouse won't work with correct s o usb/87224 usb Cannot mount USB Zip750 o usb/87648 usb [mouse] Logitech USB-optical mouse problem. o usb/88408 usb [axe] axe0 read PHY failed o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91811 usb [umass] Compact Flash in HP Photosmart 2610 return " o usb/91896 usb camcontrol(8): Serial Number of USB Memory Sticks is n o usb/92852 usb [ums] [patch] Vertical scroll not working properly on o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93872 usb [cam] [patch] SCSI quirk required for ELTA 8061 OL USB o usb/95037 usb [umass] USB disk not recognized on hot-plug. o usb/96381 usb [cam] [patch] add a quirk table entry for a flash ram o usb/97175 usb [umass] [hang] USB cardreader hangs system o usb/97472 usb [cam] [patch] add support for Olympus C150,D390 o usb/98343 usb [boot] BBB reset failed errors with Creative Muvo MP3 o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/100746 usb [keyboard] system does not boot due to USB keyboard pr o usb/101761 usb [usb] [patch] [request] usb.h: increase maximal size o o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/102678 usb [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not o usb/102976 usb [panic] Casio Exilim Digital Camera causes panic on in o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103289 usb [request] USB 2.0 problems on AMD LX-800 CPU and CS-55 o usb/103418 usb [usbhidctl] [patch] [request] usbhidctl: add ability t o usb/103917 usb [uhub] USB driver reports "Addr 0 should never happen" o usb/104290 usb [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto o usb/104352 usb [ural] [patch] ural driver doesnt work o usb/104645 usb [umass] [request] Rave C-201 MP3 player does not commu o usb/105065 usb [ata] SATA - USB Bridge o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/106041 usb [usb] [request] FreeBSD does not recognise Mustek Bear o usb/106621 usb [axe] [patch] DLINK DUB-E100 support broken o usb/106861 usb [usbdevs] [patch]: usbdevs update: Add product ACER Ze o usb/107243 usb [cam] [patch] Apacer USB Flash Drive quirk o usb/107388 usb [patch] [request] new driver: add utoppy device from N o usb/107496 usb [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [ o usb/107665 usb [usbdevs] [patch] uscanner support for epson stylus DX o usb/107935 usb [uplcom] [panic] panic while accessing /dev/cuaU0 o usb/108056 usb [ohci] Mouse gets powered off during device probe when s usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC s usb/110991 usb [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends o usb/112461 usb [ehci] [request] ehci USB 2.0 doesn't work on nforce4 o usb/112463 usb [umass] problem with Samsung USB DVD writer, libscg an o usb/112944 usb [ulpt] [patch] Bi-directional access to HP LaserJet 10 o usb/113060 usb [usbdevs] [patch] Samsung printer not working in bidir o usb/113432 usb [ucom] WARNING: attempt to net_add_domain(netgraph) af o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff o usb/114068 usb [umass] [patch] Problems with connection of the umass o usb/114916 usb [umass] [patch] USB Maxtor drive (L300RO) requires qui o usb/115080 usb [usbdevs] [patch] allow using a Hercules HWGUSB2-54-V2 o usb/115400 usb [ehci] Problem with EHCI on ASUS M2N4-SLI o usb/115933 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/115935 usb [usbdevs] [patch] kernel counterproductively attaches o usb/116282 usb [ulpt] Cannot print on USB HP LJ1018 or LJ1300 o usb/117075 usb [scsi_da] [patch] quirk: USB Samsung YP-U3 MP3 o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a o usb/117185 usb [umodem] [patch] Add support for UNION interface descr o usb/117205 usb [uscanner] [patch] uscanner support for HP ScanJet 447 o usb/117546 usb [usbdevs] [patch] Add MaxStream ZigBee product ID to u o usb/117598 usb [uaudio] [patch] Not possible to record with Plantroni o usb/117893 usb [umass] Lacie USB DVD writing failing o usb/117911 usb [ums] [request] Mouse Gembird MUSWC not work o usb/117938 usb [ums] [patch] Adding support for MS WL Natural and MS o usb/118098 usb [umass] 6th gen iPod causes problems when disconnectin o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround o usb/118686 usb [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei o usb/119150 usb [usbdevs] [patch] new usbdevs for CDMA 1xEVDO devices o usb/119227 usb [ubsa] [patch] ubsa buffer is too small; should be tun o usb/119389 usb [umass] Sony DSC-W1 CBI reset failed, STALLED [regress o usb/119633 usb [umass] umass0: BBB reset failed, IOERROR [regression] o usb/119653 usb [cam] [patch] iriver s7 player sync cache error patch o usb/119981 usb [usbdevs] [patch] add support for LOGITEC LAN-GTJ/U2 g o usb/120572 usb [umass] [patch] quirk to support ASUS P535 as umass (a o usb/121045 usb [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS o usb/121052 usb [ums] Microsoft Notebook Optical Mouse 3000 (model 104 o usb/121169 usb [umass] Issues with usb mp3 player o usb/121184 usb [uipaq] [patch] add ids from linux ipaq driver (plus a o usb/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/122025 usb [patch] uscanner does not attach to Epson RX620 printe o usb/122119 usb [umass] umass device causes creation of daX but not da o usb/122547 usb [ehci] USB Printer not being recognized after reboot p usb/122610 usb Add Verizon v740 support to ubsa(4) o usb/122621 usb [patch] [request] New driver for Sierra Wireless 3G US o usb/122712 usb [usbdevs] [patch] Sony Vaio RF keyboard/mouse receiver o usb/122813 usb [udbp] [request] udbp driver should be removed in favo o usb/122819 usb Patch to provide dynamic additions to the usb quirks t o usb/122936 usb [ucom][ubsa] Device does not receive interrupt o usb/122956 usb Support for Novatel Wireless XU870 3G Card o usb/122992 usb MotoROKR Z6 Phone not recognised by umass as USB disk. p usb/123148 usb [usbdevs] [patch] Epson DX8400/50 needs uscanner to sc o usb/123211 usb [udav] if_udav driver doesn't support Davicom 9601 USB o kern/123224 usb [ums] Scroll wheel breakage w/ USB MS Wireless Intelli o usb/123351 usb Add Reiner SCT cyberJack, Omnikey [26]020, Fujitsu Sie o usb/123352 usb Add Option GTMAX3.6/7.2 and Quallcomm MMC module devic o usb/123509 usb [umass] continuous reset Samsung SGH-G600 phone o usb/123611 usb [usb] BBB reset failed, STALLED from Imation/Mitsumi U o usb/123691 usb usbd(8): usbd hangs o usb/123959 usb [ums] add support for Razer Lachesis 4000dpi usb mouse o usb/123969 usb Supermicro H8SMi-2 usb problem 132 problems total. From owner-freebsd-usb@FreeBSD.ORG Mon Jun 9 12:36:55 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DD3D1065671 for ; Mon, 9 Jun 2008 12:36:55 +0000 (UTC) (envelope-from markus@freebsd.org) Received: from mail-in-17.arcor-online.net (mail-in-17.arcor-online.net [151.189.21.57]) by mx1.freebsd.org (Postfix) with ESMTP id 857148FC1B for ; Mon, 9 Jun 2008 12:36:52 +0000 (UTC) (envelope-from markus@freebsd.org) Received: by mail-in-17.arcor-online.net (Postfix, from userid 51) id 261E82BCB8B; Mon, 9 Jun 2008 15:24:56 +0200 (CEST) Received: from mail-in-04-z2.arcor-online.net (mail-in-04-z2.arcor-online.net [151.189.8.16]) by mail-in-17.arcor-online.net (Postfix) with ESMTP id DD2EB2BC809; Mon, 9 Jun 2008 14:24:53 +0200 (CEST) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mail-in-04-z2.arcor-online.net (Postfix) with ESMTP id C5140AF5F5; Mon, 9 Jun 2008 14:24:53 +0200 (CEST) Received: from galaxy.homeunix.org (dslb-084-061-031-181.pools.arcor-ip.net [84.61.31.181]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id 7F7AE104FE5; Mon, 9 Jun 2008 14:24:53 +0200 (CEST) Received: from cheops.phoenix (cheops.phoenix [192.168.1.3]) by galaxy.homeunix.org (Postfix) with ESMTPA id 0FA053F50A; Mon, 9 Jun 2008 14:23:21 +0200 (CEST) From: Markus Brueffer To: freebsd-usb@freebsd.org Date: Mon, 9 Jun 2008 14:24:37 +0200 User-Agent: KMail/1.9.7 References: <484BEE1C.8040903@telenix.org> <200806082132.51357.hselasky@c2i.net> <484C46D6.6050908@telenix.org> In-Reply-To: <484C46D6.6050908@telenix.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1548941.RjrWY61epo"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806091424.38147.markus@freebsd.org> X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on mail-in-01.arcor-online.net X-Virus-Status: Clean Cc: Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 12:36:55 -0000 --nextPart1548941.RjrWY61epo Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Sonntag, 8. Juni 2008 22:53:42 schrieb Chuck Robey: > Hans Petter Selasky wrote: > > Hi Chuck, > > > > On Sunday 08 June 2008, Chuck Robey wrote: > >> Hans, this is the big question, requires more thought, so if you don't > >> have enough time on hand, give this a skip for a while. I'm CC'ing th= is > >> to the FreeBSD-USB list, it's conceivable that I might get lucky there, > >> too. > >> > >> This replaces my last usb question, because (even though I think the > >> answer to that one confirms the utter insanity of the people who wrote > >> the USB-HID spec), I have absolute confirmation of the fact that I > >> cannot, in situations where the report descriptor has multiple sections > >> ID'd by multiple report IDs, force the USB peripheral to send me the > >> report ID that makes the best sense, and I must be satisfied with > >> whatever the device sends me. That's ridiculous, but I wrote down the > >> reference, just so I could look back at it and confirm to myself that I > >> wasn't dreaming any of this. > >> > >> As a better illustration of that, my tablet has report IDs 7, 8, and 9. > >> ID# 7 is the only one that matches well, but the device manufacturer h= as > >> set it up to respond ONLY with report ID# 9. If I _could_ change that, > >> I surely would, and I spent a LOT of time investigating until I > >> absolutely found hard confirmation of the fact that I can't. If you g= et > >> lucky and have a mfr sending all of the report ID's, you then can toss > >> out the ones you don't like, but if they only send one (as in my case), > >> well, you're screwed. What a stupid spec! > > > > You mean if you can set another USB configuration ? > > That's what I'm saying SHOULD be possible, but it isn't. Why have report > ID's if you can't use them? That's why I say it's loony. The general > response I have had is, sometimes multiple reports are sent, but that's > contradicted by most of the stuff I've read, so I disbelieve it... hid > reports are limited to 8 bytes, so thinking that more than one report is = to > be sent sounds wrong. They are not, see chapter 8.4 in the HID spec for constraints of reports. > I was so incensed when I found the truth, I=20 > memorized the page I read it in, so if you feel like checking me, do you > have a copy of that pdf book > USB_Complete_3rdEdition.pdf ?? If you don't, you really should, I could > send you a copy, it's freely available on the net. Anyhow, the stuff on > page 363 is what I finally tripped over. It took me quite a while to find > it, and it says flatly that the transmitted report (if more than 1 is > defined in the report descriptor) can't be changed. > > Mine always reports ID#9, and since my ID#7 is far better, I wanted that > one, but I guess I can live with it. > > >> My question now regards parsing of the input data using FreeBSD-suppli= ed > >> functions (which seems to me to mean things in libusbhid). Even though > >> I can get hid_get_item and then hid_locate() to work for me, it's only > >> by ignoring incorrect return values. Past that, the final point would > >> be to use hid_get_data() to select and scale the data (which I gather > >> through a read() of a scanned-for device such as uhid0) EXCEPT that I > >> cannot get anything but a integer zero to return to me. > > > > Have you looked into "hid_get_data()" and stepped through it? > > > >> Darn hid_get_data() just doesn't work. I'm probably missing some code > >> assumption that didn't get illustrated in the man page. The only > >> example I can get for it (the kernel code) is in dev/usb/ums.c, using > >> the code in sys/dev/usb/hid.c, BUT the proto for this kernel code just > >> looks _really_ different than the proto for the libusbhid functions.=20 > >> Headers and declarations are set up to make it really evil to try to u= se > >> the kernel code in the user-mode code. I'm possibly going to have to > >> adapt the kernel code to see if it can be forced to run in usermode. > >> > >> Does the libusbhid stuff work? Is there any sort of example, anywhere? > >> Or, should I copy and adapt the kernel code? I could do the 3rd item, > >> but it also seems like a really bad way to go. > > > > I never used it. I probably will one day and it seems like there are so= me > > bugs that needs to be fixed according to you :-) > > I don't trust myself, I do make silly errors. > > My test program is so completely screwed up because I have experimented > rather freely, I would really be embarrassed to show it to you, but I can > get nothing returned excepting a zero from hid_locate (although it DOES > seem to work anyhow) and nothing except zero from hid_get_data(), but sin= ce > that's where it's supposed to return data, it is more than a little > upsetting. > > Beyond that (as I recently posted on the usb list) I have found what looks > to me to be another oddity of libusbhid: there are some comments about the > type of data (signed or unsigned) being uncertain, however, looking at the > HID spec, top paragraph of page 38, the type of data is clearly delineate= d. > The libusbhid seems to have a bias toward signed, but all the data in my > device is unsigned. This is one of the numerous bugs in libusbhid which will be fixed by the ne= w=20 HID code I'm working on. Markus --nextPart1548941.RjrWY61epo Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iEYEABECAAYFAkhNIQYACgkQ1I0Qcnj4qNQTvgCeJOpc7nspokSSSHxoz52Mk2DK 0J0AoOzhbJ61BkhbE7OSaHuJPlwV4A8l =pRXd -----END PGP SIGNATURE----- --nextPart1548941.RjrWY61epo-- From owner-freebsd-usb@FreeBSD.ORG Mon Jun 9 13:38:47 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 847541065678 for ; Mon, 9 Jun 2008 13:38:47 +0000 (UTC) (envelope-from markus@FreeBSD.org) Received: from mail-in-07.arcor-online.net (mail-in-07.arcor-online.net [151.189.21.47]) by mx1.freebsd.org (Postfix) with ESMTP id 0CDD98FC15 for ; Mon, 9 Jun 2008 13:38:46 +0000 (UTC) (envelope-from markus@FreeBSD.org) Received: from mail-in-01-z2.arcor-online.net (mail-in-01-z2.arcor-online.net [151.189.8.13]) by mail-in-07.arcor-online.net (Postfix) with ESMTP id E76AD24AE29; Mon, 9 Jun 2008 14:24:38 +0200 (CEST) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mail-in-01-z2.arcor-online.net (Postfix) with ESMTP id D859D2BF96C; Mon, 9 Jun 2008 14:24:38 +0200 (CEST) Received: from galaxy.homeunix.org (dslb-084-061-031-181.pools.arcor-ip.net [84.61.31.181]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id 9C896104F1C; Mon, 9 Jun 2008 14:24:38 +0200 (CEST) Received: from cheops.phoenix (cheops.phoenix [192.168.1.3]) by galaxy.homeunix.org (Postfix) with ESMTPA id 40B0C3F4D8; Mon, 9 Jun 2008 14:23:06 +0200 (CEST) From: Markus Brueffer To: freebsd-usb@freebsd.org Date: Mon, 9 Jun 2008 14:24:17 +0200 User-Agent: KMail/1.9.7 References: <484BEE1C.8040903@telenix.org> In-Reply-To: <484BEE1C.8040903@telenix.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1391206.TanApH1FDV"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806091424.23154.markus@FreeBSD.org> X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on mail-in-01.arcor-online.net X-Virus-Status: Clean Cc: Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 13:38:47 -0000 --nextPart1391206.TanApH1FDV Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Sonntag, 8. Juni 2008 16:35:08 schrieb Chuck Robey: > This replaces my last usb question, because (even though I think the answ= er > to that one confirms the utter insanity of the people who wrote the USB-H= ID > spec), I have absolute confirmation of the fact that I cannot, in > situations where the report descriptor has multiple sections ID'd by > multiple report IDs, force the USB peripheral to send me the report ID th= at > makes the best sense, and I must be satisfied with whatever the device > sends me. That's ridiculous, but I wrote down the reference, just so I > could look back at it and confirm to myself that I wasn't dreaming any of > this. > > As a better illustration of that, my tablet has report IDs 7, 8, and 9.=20 > ID# 7 is the only one that matches well, but the device manufacturer has > set it up to respond ONLY with report ID# 9. If I _could_ change that, I > surely would, and I spent a LOT of time investigating until I absolutely > found hard confirmation of the fact that I can't. If you get lucky and > have a mfr sending all of the report ID's, you then can toss out the ones > you don't like, but if they only send one (as in my case), well, you're > screwed. What a stupid spec! Just because you don't understand the reasoning behind this part of the spe= c,=20 it doesn't make it ridiculous automatically, so please stop bashing the spe= c=20 as it doesn't help in any way. In your case the report IDs directly correspond to 3 different top level=20 application collections: ID 7: Digitizer Pen ID 8: Mouse (relative coordinates) ID 9: Mouse (absolute coordinates) This way, each application collection can be handled by a generic driver=20 instead of requireing a special driver for the whole device or interface.=20 This isn't supported by our HID code, yet, but it will be (I'm working on=20 that part). If your tablet only uses report ID 9 regardless of what device (pen or mous= e)=20 you use on it, this is certainly the vendor's fault but not the fault of th= e=20 HID spec. > My question now regards parsing of the input data using FreeBSD-supplied > functions (which seems to me to mean things in libusbhid). Even though I > can get hid_get_item and then hid_locate() to work for me, it's only by > ignoring incorrect return values. Past that, the final point would be to > use hid_get_data() to select and scale the data (which I gather through a > read() of a scanned-for device such as uhid0) EXCEPT that I cannot get > anything but a integer zero to return to me. As I told you before in private mail, see the source of usbhidctl(1) for =20 examples on how to use libusbhid functions. hid_get_data() is being used=20 there as well. > Darn hid_get_data() just doesn't work. I'm probably missing some code > assumption that didn't get illustrated in the man page. The only example= I > can get for it (the kernel code) is in dev/usb/ums.c, using the code in > sys/dev/usb/hid.c, BUT the proto for this kernel code just looks _really_ > different than the proto for the libusbhid functions. Headers and > declarations are set up to make it really evil to try to use the kernel > code in the user-mode code. I'm possibly going to have to adapt the kern= el > code to see if it can be forced to run in usermode. The kernel has its own HID functions which are mostly, but not entirely, th= e=20 same than the counterparts in libusbhid. > Does the libusbhid stuff work? Is there any sort of example, anywhere?=20 > Or, should I copy and adapt the kernel code? I could do the 3rd item, but > it also seems like a really bad way to go. > > What's the right path here? Am I being stupid in missing the obvious? > > > There's even one other question ... I'd heard some while back that someone > else was preparing a separate implementation of the hid code. Do you know > of anything like that, anything I could maybe replace the libusbhid code > with? That would be me. Markus --nextPart1391206.TanApH1FDV Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iEYEABECAAYFAkhNIPcACgkQ1I0Qcnj4qNQccQCgqFqFIME++IP6IjWiJsABwmb+ +IYAn0wqFifeWnC0X7HPZePfGqsPlcBa =8bex -----END PGP SIGNATURE----- --nextPart1391206.TanApH1FDV-- From owner-freebsd-usb@FreeBSD.ORG Mon Jun 9 13:38:47 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4C72106564A for ; Mon, 9 Jun 2008 13:38:47 +0000 (UTC) (envelope-from markus@freebsd.org) Received: from mail-in-05.arcor-online.net (mail-in-05.arcor-online.net [151.189.21.45]) by mx1.freebsd.org (Postfix) with ESMTP id 3E4FD8FC16 for ; Mon, 9 Jun 2008 13:38:47 +0000 (UTC) (envelope-from markus@freebsd.org) Received: from mail-in-05-z2.arcor-online.net (mail-in-05-z2.arcor-online.net [151.189.8.17]) by mail-in-05.arcor-online.net (Postfix) with ESMTP id 1A95D1837A8; Mon, 9 Jun 2008 14:25:02 +0200 (CEST) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mail-in-05-z2.arcor-online.net (Postfix) with ESMTP id 0942732A6C4; Mon, 9 Jun 2008 14:25:02 +0200 (CEST) Received: from galaxy.homeunix.org (dslb-084-061-031-181.pools.arcor-ip.net [84.61.31.181]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id 46FDB105063; Mon, 9 Jun 2008 14:25:01 +0200 (CEST) Received: from cheops.phoenix (cheops.phoenix [192.168.1.3]) by galaxy.homeunix.org (Postfix) with ESMTPA id 2AF843F57C; Mon, 9 Jun 2008 14:23:28 +0200 (CEST) From: Markus Brueffer To: freebsd-usb@freebsd.org Date: Mon, 9 Jun 2008 14:24:44 +0200 User-Agent: KMail/1.9.7 References: <484BEE1C.8040903@telenix.org> <200806082310.56920.hselasky@c2i.net> <484C8D2B.40404@telenix.org> In-Reply-To: <484C8D2B.40404@telenix.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1817618.jOfArEqI5v"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806091424.45235.markus@freebsd.org> X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on mail-in-01.arcor-online.net X-Virus-Status: Clean Cc: Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 13:38:47 -0000 --nextPart1817618.jOfArEqI5v Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Montag, 9. Juni 2008 03:53:47 schrieb Chuck Robey: > Hans Petter Selasky wrote: > > On Sunday 08 June 2008, Chuck Robey wrote: > >> Hans Petter Selasky wrote: > >>> Hi Chuck, > >>> > >>> On Sunday 08 June 2008, Chuck Robey wrote: > >>>> Hans, this is the big question, requires more thought, so if you don= 't > >>>> have enough time on hand, give this a skip for a while. I'm CC'ing > >>>> this to the FreeBSD-USB list, it's conceivable that I might get lucky > >>>> there, too. > >>>> > >>>> This replaces my last usb question, because (even though I think the > >>>> answer to that one confirms the utter insanity of the people who wro= te > >>>> the USB-HID spec), I have absolute confirmation of the fact that I > >>>> cannot, in situations where the report descriptor has multiple > >>>> sections ID'd by multiple report IDs, force the USB peripheral to se= nd > >>>> me the report ID that makes the best sense, and I must be satisfied > >>>> with whatever the device sends me. That's ridiculous, but I wrote > >>>> down the reference, just so I could look back at it and confirm to > >>>> myself that I wasn't dreaming any of this. > >>>> > >>>> As a better illustration of that, my tablet has report IDs 7, 8, and > >>>> 9. ID# 7 is the only one that matches well, but the device > >>>> manufacturer has set it up to respond ONLY with report ID# 9. If I > >>>> _could_ change that, I surely would, and I spent a LOT of time > >>>> investigating until I absolutely found hard confirmation of the fact > >>>> that I can't. If you get lucky and have a mfr sending all of the > >>>> report ID's, you then can toss out the ones you don't like, but if > >>>> they only send one (as in my case), well, you're screwed. What a > >>>> stupid spec! > >>> > >>> You mean if you can set another USB configuration ? > >> > >> That's what I'm saying SHOULD be possible, but it isn't. > > > > There will soon be a utility that can do this, so that you can run: > > > > usbconfig -u ugen0 -c 1 > > > > for example to select configuration index 1 for your device. Please note > > that there will be one ugen device for every USB device present in the > > future! And I'm in the future :-) > > Most likely possibility: you (like one other person already) is > misinterpreting what I'm talking about. Being that I tend to be a bit > loose about terminology sometimes (and sometimes too often) it's likely my > fault. Just to see if I can run over what the other person meant, I'm ve= ry > much NOT talking about the thing that the USB HID spec calls a "report > type", one example being the input type, or feature, etc. I am talking > about a subset of HID report descriptors that are written with multiple > "report ID" fields (see HID spec page 36), like the one with my UC-Logic > graphic tablet, which is written with report IDs 7, 8, and 9. Most HID > devices (and only HID devices have these report descriptors anyhow) have > only a single report ID, and so they don't actually have the explicit > report ID line (they let it default to zero). Actually they don't let it default to 0 as 0 is not allowed for a report ID= =2E=20 They just don't specify a report id which is a subtle, but important=20 difference. If a report id is specified (regardless if only one or more), t= he=20 report is prefixed by one byte which specifies the id. If no report id fiel= d=20 is in the report descriptor, the report is not prefixed with such a report = id=20 byte. > Other devices, which DO have=20 > multiple report ID's, have small enough reports to have multiple reports > fit in a single data report (those are limited by spec to 8 bytes). It is not limited by 8 bytes (see my other mail). Furthermore, no device=20 reports several reports in a single data report, unless it is horribly=20 broken. Maybe you mean something different here, if so, please stick to the= =20 nomenclature as defined in the HID spec. > The=20 > report ID, for ones with multiple ID's, forms the first byte of the data > report. My tablet reports 0x09 as the first byte, I wish it would report= a > 0x07. The reference I gave you is unmistably clear in saying that it is > not possible to cause a device to change the report ID's it sends. My > device needs 7 data bytes, 8 with the leading report ID, which is VERY > unfortunately an 0x09, not the 0x07 which would really be optimal. > > Another possibility occurs, though: my reference, the USB Complete book, > page 363, is just plain wrong. That possibility is what fuels this email= =2E=20 > Maybe there IS a way ... God knows, the USB HID spec is such an incredible > POS that getting it wrong can't even be blamed on an otherwise very good > programmer. I have read many specs in my life, never seen one even close > to being as bad as that one (although I admit most of the specs I have > dealt with were communications oriented, I was mostly a commuications > engr.) > > If you have any reference to any method which might exist to send any data > pattern at all to a USB HID device, to cause it to change the report ID > coding (scaling, etc) that it follows, I sure would appreciate you telling > me that. Don't even need to tell me how, I will read myself (although I > would like that, I am so desperate to get such, I would really appreciate > it in any form I could get it, whatsoever). I have commented on this in detail already in private mail some time ago, s= o I=20 won't repeat it here. Markus --nextPart1817618.jOfArEqI5v Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iEYEABECAAYFAkhNIQ0ACgkQ1I0Qcnj4qNTh3ACfeTwe7lbu//Eu0cPB2a9u/0Bv uJUAn3qGus9A29zFZ2ZAX5BLGsKa9Oo7 =re2F -----END PGP SIGNATURE----- --nextPart1817618.jOfArEqI5v-- From owner-freebsd-usb@FreeBSD.ORG Mon Jun 9 17:58:53 2008 Return-Path: Delivered-To: FreeBSD-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC0EC1065670 for ; Mon, 9 Jun 2008 17:58:53 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id 551498FC0A for ; Mon, 9 Jun 2008 17:58:52 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=UlUzKLwsL7l1WSYqPADo3w==:17 a=3oFxPOZCAAAA:8 a=FP58Ms26AAAA:8 a=DW9zHcg8J5pHq0ceKUMA:9 a=VGTuqqYtDM0zEZU7uaxzK298wqwA:4 a=9aOQ2cSd83gA:10 a=LY0hPdMaydYA:10 Received: from [62.113.132.30] (account mc467741@c2i.net [62.113.132.30] verified) by mailfe07.swip.net (CommuniGate Pro SMTP 5.1.13) with ESMTPA id 967611834; Mon, 09 Jun 2008 19:58:51 +0200 From: Hans Petter Selasky To: "Xiaofan Chen" Date: Mon, 9 Jun 2008 20:00:22 +0200 User-Agent: KMail/1.9.7 References: <484BEE1C.8040903@telenix.org> <200806082310.56920.hselasky@c2i.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806092000.23097.hselasky@c2i.net> Cc: FreeBSD USB List Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 17:58:53 -0000 On Monday 09 June 2008, Xiaofan Chen wrote: > On 6/9/08, Hans Petter Selasky wrote: > > There will soon be a utility that can do this, so that you can run: > > > > usbconfig -u ugen0 -c 1 > > > > for example to select configuration index 1 for your device. Please note > > that there will be one ugen device for every USB device present in the > > future! And I'm in the future :-) > > That would be great. In that case, you might want to look at the new > libusb-1.0 and ported it to FreeBSD. The new libusb-1.0 supports > isochronous > transfer and asynchronous I/O. Right now it only works under Linux. > It is under beta now but the API should be mostly stable alreay. > http://www.reactivated.net/weblog/archives/2008/05/libusb-10-enters-beta/ > http://libusb.sourceforge.net/api-1.0/ > Thanks Xiafan, I will do that. --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Jun 10 17:05:23 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0ECB4106564A for ; Tue, 10 Jun 2008 17:05:23 +0000 (UTC) (envelope-from starbuck797@yahoo.es) Received: from web26307.mail.ukl.yahoo.com (web26307.mail.ukl.yahoo.com [217.146.176.18]) by mx1.freebsd.org (Postfix) with SMTP id 6C36A8FC1A for ; Tue, 10 Jun 2008 17:05:22 +0000 (UTC) (envelope-from starbuck797@yahoo.es) Received: (qmail 38140 invoked by uid 60001); 10 Jun 2008 17:05:21 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.es; h=Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=LkmkGVI5WsI2qqF803aYoCu7l5XKtyvgsKUJlc4IpvrPl/Abt9PKbHG6pYocmIb9yWx2q4tU31IZep78aDl5SU5UxygLbsmkDMdXhfBGr/CefOiWCxJIpFwojVgFihQF/k53VOq7ToBJO3yIvj9jgaI/R0/Iq8rnZrE/V6Jwc3Q=; Received: from [190.76.42.0] by web26307.mail.ukl.yahoo.com via HTTP; Tue, 10 Jun 2008 17:05:20 GMT X-Mailer: YahooMailRC/975.45 YahooMailWebService/0.7.199 Date: Tue, 10 Jun 2008 17:05:20 +0000 (GMT) From: =?iso-8859-1?Q?Miguel_V=E1squez=2E?= To: freebsd-usb@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <150442.38124.qm@web26307.mail.ukl.yahoo.com> Subject: Problem with Usb Modem CMOTECH CCU-550 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2008 17:05:23 -0000 Hello Everybody.=0A=0A=0AI am a novice in FreeBSD, I use FreeBSD 7.0 in a A= cer Aspire=0A5570z laptop, I have tried to use my modem CMOTECH CCU550 but = I have not=0Asuccessful, Can you Help me??=0A=0A=0AUntil now, I did the fol= lowing thing:=0AI executed,=0A#kldload ucom=0A#kldload umodem=0Aplug my mod= em and the system display:=0A=0A*******************************************= ***********************************=0Aucom0: on uhub2=0Aucom0: iclass = 2/2=0Aucom0: data interface 1, has CM over data, has break=0Aucom0: status = change notification available=0A*******************************************= ******************************=0A=0Aafter this, i tried to configure KPPP b= ut, i can not to get to connect, =0Awhat is wrong??=0A=0AI want to adapt my= service of Internet for FreeBSD 7.0, =0Abut, i can not make work my modem.= =0A=0AIs necessary this patch? http://lists.freebsd.org/pipermail/freebsd-u= sb/2007-June/003400.html=0A=0AIs necessary to load uplcom?=0A=0ACan i use K= PPP ?? <--- KDE(ppp)=0A=0A=0AI hope you can help me.=0ANote: My English is = not good, i speak spanish.=0A=0ABest regards,=0AMiguel.=0A=0A=0A _____= _________________________________________ =0AEnviado desde Correo Yahoo! La= bandeja de entrada m=E1s inteligente. From owner-freebsd-usb@FreeBSD.ORG Tue Jun 10 18:39:02 2008 Return-Path: Delivered-To: usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25C66106567D; Tue, 10 Jun 2008 18:39:02 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id AD9118FC18; Tue, 10 Jun 2008 18:39:00 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7cd5.q.ppp-pool.de [89.53.124.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 6136412883F; Tue, 10 Jun 2008 20:12:58 +0200 (CEST) Received: from cesar.sz.vwsoft.com (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id D3EB990427; Tue, 10 Jun 2008 20:12:01 +0200 (CEST) Message-ID: <484EC402.9060200@vwsoft.com> Date: Tue, 10 Jun 2008 20:12:18 +0200 From: Volker User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: usb@freebsd.org X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit MailScanner-NULL-Check: 1213726335.47834@b0xGWcLprNsc//ABGtd1pA X-MailScanner-ID: D3EB990427.B8830 X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: Subject: WIP: usb touchscreen drivers X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2008 18:39:02 -0000 Hi everybody! I'm taking the chance and cross-posting this to the exciting, hopefully soon becoming busy, shiny new mailing list (freebsd-wip-status@ bcc'd, for those not already aware). Currently I'm working under contract for developing FreeBSD drivers for USB touchscreen devices. Before coding started, I've figured out the possible solutions to get a touchscreen device running under FreeBSD / X11 but haven't found much. We currently don't have any specialized drivers (but ums and uhid). More than worse: By default the ums driver is attaching to the device by default which has no support for devices reporting zero buttons and absolute coordinates. Currently OpenBSD has support for touchscreen devices but I found it difficult (or at least too much work) to port over wscons and replace syscons with that. Current touchscreen xf86-input drivers do partly support USB devices under Linux and I don't like to have the Xinput driver parse the USB protocol itself. Using a specialized kernel driver has some advantages IMO. Currently I'm having a basic, working driver (hence: WIP!), at kernel level (utouch) and a corresponding xf86-input-utouch driver. The first device supported is a Generaltouch ST6101U. So far, the device is working, the X pointer is following touches and button clicks are reported to X. Axis scaling is currently sub-optimal but I think I'll rework the scaling once more. What I would love to see: If you're having a USB connected touchscreen device laying around, I would love to see a krepdump [1] of that device to see how other devices are reporting. Especially, if you're having a multi-touch device, I would strongly love to see how this device reports data! BTW, it shouldn't be too difficult to enhance my driver infrastructure to also support tablet devices (also reporting absolute coordinates but also reporting button presses and some more functionality). As this work is under contract, I need to get approval to release the code but I'm pretty sure to get approval (BSD-licensed, of course). If you're interested in seeing USB touchscreen support for FreeBSD this way and have a device laying around, please contact me directly and I'll see how to support your device. Thanks! Volker [1] http://people.freebsd.org/~kaiw/tools/krepdump.tgz From owner-freebsd-usb@FreeBSD.ORG Wed Jun 11 12:22:04 2008 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C69DD1065671; Wed, 11 Jun 2008 12:22:04 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9A6F58FC30; Wed, 11 Jun 2008 12:22:04 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5BCM4jG030202; Wed, 11 Jun 2008 12:22:04 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5BCM4qT030198; Wed, 11 Jun 2008 12:22:04 GMT (envelope-from gavin) Date: Wed, 11 Jun 2008 12:22:04 GMT Message-Id: <200806111222.m5BCM4qT030198@freefall.freebsd.org> To: gavin@FreeBSD.org, skr.bek@centrum.cz, gavin@FreeBSD.org, freebsd-usb@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: usb/121861: [keyboard] Don't work Fn keys on USB Microsoft Natural Ergonomic Keyboard 4000 7.0-RELEASE [regression] X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2008 12:22:04 -0000 Synopsis: [keyboard] Don't work Fn keys on USB Microsoft Natural Ergonomic Keyboard 4000 7.0-RELEASE [regression] State-Changed-From-To: open->closed State-Changed-By: gavin State-Changed-When: Wed Jun 11 12:21:29 UTC 2008 State-Changed-Why: Close, as a duplicate of usb/116947 (which contains a patch that at least works around the issue) http://www.freebsd.org/cgi/query-pr.cgi?pr=121861 From owner-freebsd-usb@FreeBSD.ORG Wed Jun 11 12:39:11 2008 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B59371065670; Wed, 11 Jun 2008 12:39:11 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 88F798FC0C; Wed, 11 Jun 2008 12:39:11 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5BCdBqt034383; Wed, 11 Jun 2008 12:39:11 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5BCdBiF034379; Wed, 11 Jun 2008 12:39:11 GMT (envelope-from gavin) Date: Wed, 11 Jun 2008 12:39:11 GMT Message-Id: <200806111239.m5BCdBiF034379@freefall.freebsd.org> To: oliver@akephalos.de, gavin@FreeBSD.org, freebsd-usb@FreeBSD.org, kaiw@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: usb/121052: [ums] Microsoft Notebook Optical Mouse 3000 (model 1049) doesn't work X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2008 12:39:11 -0000 Synopsis: [ums] Microsoft Notebook Optical Mouse 3000 (model 1049) doesn't work State-Changed-From-To: open->patched State-Changed-By: gavin State-Changed-When: Wed Jun 11 12:37:14 UTC 2008 State-Changed-Why: This is fixed in HEAD Responsible-Changed-From-To: freebsd-usb->kaiw Responsible-Changed-By: gavin Responsible-Changed-When: Wed Jun 11 12:37:14 UTC 2008 Responsible-Changed-Why: Give to kaiw@ as a reminder that this needs to be MFC'd http://www.freebsd.org/cgi/query-pr.cgi?pr=121052 From owner-freebsd-usb@FreeBSD.ORG Wed Jun 11 12:45:59 2008 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3AC71065671; Wed, 11 Jun 2008 12:45:59 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A734B8FC23; Wed, 11 Jun 2008 12:45:59 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5BCjxgI035332; Wed, 11 Jun 2008 12:45:59 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5BCjxBM035328; Wed, 11 Jun 2008 12:45:59 GMT (envelope-from gavin) Date: Wed, 11 Jun 2008 12:45:59 GMT Message-Id: <200806111245.m5BCjxBM035328@freefall.freebsd.org> To: giffunip@tutopia.com, gavin@FreeBSD.org, freebsd-usb@FreeBSD.org, remko@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: usb/118391: [usbdevs] [patch] Add uscanner ID for Epson CX4800 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2008 12:45:59 -0000 Synopsis: [usbdevs] [patch] Add uscanner ID for Epson CX4800 State-Changed-From-To: open->patched State-Changed-By: gavin State-Changed-When: Wed Jun 11 12:44:27 UTC 2008 State-Changed-Why: This has been fixed in HEAD (uscanner.c 1.92) Responsible-Changed-From-To: freebsd-usb->remko Responsible-Changed-By: gavin Responsible-Changed-When: Wed Jun 11 12:44:27 UTC 2008 Responsible-Changed-Why: Over to remko@ as an MFC reminder http://www.freebsd.org/cgi/query-pr.cgi?pr=118391 From owner-freebsd-usb@FreeBSD.ORG Thu Jun 12 10:30:04 2008 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CBC01065674 for ; Thu, 12 Jun 2008 10:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 43B568FC0A for ; Thu, 12 Jun 2008 10:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5CAU476029242 for ; Thu, 12 Jun 2008 10:30:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5CAU4MG029238; Thu, 12 Jun 2008 10:30:04 GMT (envelope-from gnats) Date: Thu, 12 Jun 2008 10:30:04 GMT Message-Id: <200806121030.m5CAU4MG029238@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: "=?KOI8-R?B?6czY0SD7ydDJw8nO?=" Cc: Subject: Re: usb/93155: [ulpt] /dev/ulpt0: device busy, USB printer does not work X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?KOI8-R?B?6czY0SD7ydDJw8nO?= List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2008 10:30:04 -0000 The following reply was made to PR usb/93155; it has been noted by GNATS. From: "=?KOI8-R?B?6czY0SD7ydDJw8nO?=" To: bug-followup@FreeBSD.org Cc: stevedav@sonic.net Subject: Re: usb/93155: [ulpt] /dev/ulpt0: device busy, USB printer does not work Date: Thu, 12 Jun 2008 16:02:23 +0600 ------=_Part_28148_24192114.1213264943522 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline this PR can be closed, after upgrading to 7-stable it disappeared ------=_Part_28148_24192114.1213264943522 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline this PR can be closed, after upgrading to 7-stable it disappeared
------=_Part_28148_24192114.1213264943522-- From owner-freebsd-usb@FreeBSD.ORG Thu Jun 12 21:10:04 2008 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5DCC1065672 for ; Thu, 12 Jun 2008 21:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9343E8FC2C for ; Thu, 12 Jun 2008 21:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5CLA42C019704 for ; Thu, 12 Jun 2008 21:10:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5CLA4V5019703; Thu, 12 Jun 2008 21:10:04 GMT (envelope-from gnats) Date: Thu, 12 Jun 2008 21:10:04 GMT Message-Id: <200806122110.m5CLA4V5019703@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Per olof Ljungmark Cc: Subject: Re: usb/122905: [ubsa] [patch] add Huawei E220 to ubsa X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Per olof Ljungmark List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2008 21:10:04 -0000 The following reply was made to PR usb/122905; it has been noted by GNATS. From: Per olof Ljungmark To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/122905: [ubsa] [patch] add Huawei E220 to ubsa Date: Thu, 12 Jun 2008 22:49:25 +0200 This is a multi-part message in MIME format. --------------070608070005050702060808 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit The attached patch for 6.3-STABLE as of June 12th. are courtesy bg@sics.se. --------------070608070005050702060808 Content-Type: text/plain; name="e220-patch-6.3" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="e220-patch-6.3" KioqIHN5cy9kZXYvdXNiL3VzYmRldnMub3JpZwkyMDA4LTA0LTA4IDE4OjM2OjQ5LjAwMDAw MDAwMCArMDIwMAotLS0gc3lzL2Rldi91c2IvdXNiZGV2cwkyMDA4LTA2LTEyIDE4OjAzOjMx LjAwMDAwMDAwMCArMDIwMAoqKioqKioqKioqKioqKioKKioqIDEwNDYsMTA1MSAqKioqCi0t LSAxMDQ2LDEwNTIgLS0tLQogIAogIC8qIEhVQVdFSSBwcm9kdWN0cyAqLwogIHByb2R1Y3Qg SFVBV0VJIE1PQklMRQkJMHgxMDAxCUh1YXdlaSBNb2JpbGUKKyBwcm9kdWN0IEhVQVdFSSBF MjIwICAgICAgICAgICAgIDB4MTAwMyAgSHVhd2VpIEUyMjAgRzMgTW9kZW0KICAKICAvKiBJ Qk0gQ29ycG9yYXRpb24gKi8KICBwcm9kdWN0IElCTSBVU0JDRFJPTURSSVZFCTB4NDQyNwlV U0IgQ0QtUk9NIERyaXZlCioqKiBzeXMvZGV2L3VzYi91YnNhLmMub3JpZwkyMDA4LTA0LTA4 IDE4OjM2OjQ5LjAwMDAwMDAwMCArMDIwMAotLS0gc3lzL2Rldi91c2IvdWJzYS5jCTIwMDgt MDYtMTIgMTg6MDQ6MzUuMDAwMDAwMDAwICswMjAwCioqKioqKioqKioqKioqKgoqKiogMjMy LDIzNyAqKioqCi0tLSAyMzIsMjM4IC0tLS0KICAJeyBVU0JfVkVORE9SX09QVElPTiwgVVNC X1BST0RVQ1RfT1BUSU9OX0dUM0dRVUFEIH0sCiAgCS8qIEh1YXdlaSBNb2JpbGUgKi8KICAJ eyBVU0JfVkVORE9SX0hVQVdFSSwgVVNCX1BST0RVQ1RfSFVBV0VJX01PQklMRSB9LAorIAl7 IFVTQl9WRU5ET1JfSFVBV0VJLCBVU0JfUFJPRFVDVF9IVUFXRUlfRTIyMCB9LAogIAkvKiBR dWFsY29tbSwgSW5jLiBaVEUgQ0RNQSAqLwogIAl7IFVTQl9WRU5ET1JfUVVBTENPTU1JTkMs IFVTQl9QUk9EVUNUX1FVQUxDT01NSU5DX0NETUFfTVNNIH0sCiAgCXsgMCwgMCB9CioqKiBz eXMvZGV2L3VzYi91c2JfcXVpcmtzLmgub3JpZwkyMDA2LTEyLTEyIDE2OjQ0OjEzLjAwMDAw MDAwMCArMDEwMAotLS0gc3lzL2Rldi91c2IvdXNiX3F1aXJrcy5oCTIwMDgtMDYtMTIgMTg6 MDU6NDkuMDAwMDAwMDAwICswMjAwCioqKioqKioqKioqKioqKgoqKiogNTQsNTkgKioqKgot LS0gNTQsNjAgLS0tLQogICNkZWZpbmUgVVFfQVVfSU5QX0FTWU5DCTB4MDgwMAkvKiBpbnB1 dCBpcyBhc3luYyBkZXNwaXRlIGNsYWltIG9mIGFkYXB0aXZlICovCiAgI2RlZmluZSBVUV9B U1NVTUVfQ01fT1ZFUl9EQVRBIDB4MTAwMCAvKiBtb2RlbSBkZXZpY2UgYnJlYWtzIG9uIGNt IG92ZXIgZGF0YSAqLwogICNkZWZpbmUgVVFfQlJPS0VOX0JJRElSCTB4MjAwMAkvKiBwcmlu dGVyIGhhcyBicm9rZW4gYmlkaXIgbW9kZSAqLworICNkZWZpbmUgVVFfRkVBVFVSRTIgICAg IDB4NDAwMCAgLyogcmVxdWlyZXMgdGhlIGVuYWJsaW5nIG9mIGZlYXR1cmUgMiAqLwogICNk ZWZpbmUgVVFfSElEX0lHTk9SRQkweDgwMDAJLyogZGV2aWNlIHNob3VsZCBiZSBpZ25vcmVk IGJ5IGhpZCBjbGFzcyAqLwogICNkZWZpbmUgVVFfS0JEX0lHTk9SRSAgMHgxODAwMAkvKiBk ZXZpY2Ugc2hvdWxkIGJlIGlnbm9yZWQgYnkgYm90aCBrYmQgYW5kIGhpZCBjbGFzcyAqLwog IAkJCQkJCioqKiBzeXMvZGV2L3VzYi91c2JfcXVpcmtzLmMub3JpZwkyMDA3LTA0LTI4IDIy OjMxOjMwLjAwMDAwMDAwMCArMDIwMAotLS0gc3lzL2Rldi91c2IvdXNiX3F1aXJrcy5jCTIw MDgtMDYtMTIgMTg6MDU6NDkuMDAwMDAwMDAwICswMjAwCioqKioqKioqKioqKioqKgoqKiog MTMxLDEzNiAqKioqCi0tLSAxMzEsMTM4IC0tLS0KICAgLyogRGV2aWNlcyB3aGljaCBzaG91 bGQgYmUgaWdub3JlZCBieSBib3RoIHVrYmQgYW5kIHVoaWQgKi8KICAgeyBVU0JfVkVORE9S X0NZUFJFU1MsIFVTQl9QUk9EVUNUX0NZUFJFU1NfV0lTUFksCiAgCUFOWSwgeyBVUV9LQkRf SUdOT1JFIH19LAorICB7IFVTQl9WRU5ET1JfSFVBV0VJLCBVU0JfUFJPRFVDVF9IVUFXRUlf RTIyMCwKKyAJQU5ZLCB7IFVRX0ZFQVRVUkUyIH19LAogICB7IDAsIDAsIDAsIHsgMCB9IH0K ICB9OwogIAoqKiogc3lzL2Rldi91c2IvdXNiX3N1YnIuYy5vcmlnCTIwMDYtMDMtMDEgMDI6 NTk6MDUuMDAwMDAwMDAwICswMTAwCi0tLSBzeXMvZGV2L3VzYi91c2Jfc3Vici5jCTIwMDgt MDYtMTIgMTg6MDU6NDkuMDAwMDAwMDAwICswMjAwCioqKioqKioqKioqKioqKgoqKiogNTM4 LDU0MyAqKioqCi0tLSA1MzgsNTU2IC0tLS0KICB9CiAgCiAgU3RhdGljIHVzYmRfc3RhdHVz CisgdXNiZF9zZXRfZmVhdHVyZSh1c2JkX2RldmljZV9oYW5kbGUgZGV2LCBpbnQgZmVhdHVy ZSkKKyB7CisgCXVzYl9kZXZpY2VfcmVxdWVzdF90IHJlcTsKKyAKKyAJcmVxLmJtUmVxdWVz dFR5cGUgPSBVVF9XUklURTsKKyAJcmVxLmJSZXF1ZXN0ID0gVVJfU0VUX0ZFQVRVUkU7Cisg CVVTRVRXKHJlcS53VmFsdWUsIDEpOworIAlVU0VUVyhyZXEud0luZGV4LCBmZWF0dXJlKTsK KyAJVVNFVFcocmVxLndMZW5ndGgsIDApOworIAlyZXR1cm4gKHVzYmRfZG9fcmVxdWVzdChk ZXYsICZyZXEsIDApKTsKKyB9CisgCisgU3RhdGljIHVzYmRfc3RhdHVzCiAgdXNiZF9zZXRf Y29uZmlnKHVzYmRfZGV2aWNlX2hhbmRsZSBkZXYsIGludCBjb25mKQogIHsKICAJdXNiX2Rl dmljZV9yZXF1ZXN0X3QgcmVxOwoqKioqKioqKioqKioqKioKKioqIDk4Miw5ODggKioqKgot LS0gOTk1LDEwMDggLS0tLQogIAkgKiBXZSBqdXN0IGRpZCBub3QgZmluZCBhbnkgZHJpdmVy cywgdGhhdCdzIGFsbC4gIFRoZSBkZXZpY2UgaXMKICAJICogZnVsbHkgb3BlcmF0aW9uYWwg YW5kIG5vdCBoYXJtaW5nIGFueW9uZS4KICAJICovCisgCiAgCURQUklOVEYoKCJ1c2JkX3By b2JlX2FuZF9hdHRhY2g6IGdlbmVyaWMgYXR0YWNoIGZhaWxlZFxuIikpOworIAkKKyAJaWYg KGRldi0+cXVpcmtzLT51cV9mbGFncyAmIFVRX0ZFQVRVUkUyKSB7CisgCQlwcmludGYoIiVz OiBFbmFibGluZyBmZWF0dXJlIFVIRl9QT1JUX1NVU1BFTkRcbiIsIGRldmljZV9nZXRfbmFt ZXVuaXQocGFyZW50KSk7CisgCQl1c2JkX3NldF9mZWF0dXJlKGRldiwgVUhGX1BPUlRfU1VT UEVORCk7CisgCX0KKyAKICAgCXJldHVybiAoVVNCRF9OT1JNQUxfQ09NUExFVElPTik7CiAg fQ== --------------070608070005050702060808-- From owner-freebsd-usb@FreeBSD.ORG Sat Jun 14 19:20:04 2008 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FEEF106566B for ; Sat, 14 Jun 2008 19:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 10ACD8FC1A for ; Sat, 14 Jun 2008 19:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5EJK30B031467 for ; Sat, 14 Jun 2008 19:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5EJK3UQ031466; Sat, 14 Jun 2008 19:20:03 GMT (envelope-from gnats) Date: Sat, 14 Jun 2008 19:20:03 GMT Message-Id: <200806141920.m5EJK3UQ031466@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: "Mars G Miro" Cc: Subject: Re: usb/118686: [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei E220 G3 Modem X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mars G Miro List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jun 2008 19:20:04 -0000 The following reply was made to PR usb/118686; it has been noted by GNATS. From: "Mars G Miro" To: bug-followup@FreeBSD.org, "Edwin Groothuis" , "Erwin Lansing" , "Tomoyuki Sakurai" Cc: Subject: Re: usb/118686: [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei E220 G3 Modem Date: Sun, 15 Jun 2008 03:13:54 +0800 Greetz, I've tried the patch above on FreeBSD/7.X. It works OK, but it doesn't give me HSDPA speeds, only 3G. I know this because I have a dual-boot system where my XP can go up to 1.XX Mbps speeds. I think the NetBSD/OpenBSD drivers are worth looking/porting into. Thanks. -- cheers mars