Fwd: Re: Driver for LEDs on Logitech MX610
sorry, I forgot to cc the list. Since I just got the welcome to the - u...@freebsd.org Mailinglist, this mess should stop now Christof -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments --- Begin Message --- Hello, > Have you looked at libusb? I had not looked at it. I have to admit that I made a mistake concerning the device names. This is what the kernel finds when plugging in the device: ugen0.3: at usbus0 ums0: on usbus0 ums0: 16 buttons and [XYZ] coordinates ID=0 uhid0: on usbus0 so the led-device gets recognized as uhid0. Maybe that is why that your sample code from http://archive.netbsd.se/?ml=freebsd-usb&a=2008-12&t=9232208 never returns from a libusb20_dev_wait_process in do_io()? Now I am unsure whether I should stick with hid or fully get rid of it :) Considering the fact that the author of libusb seems to be willing to help & considering the state of the usbhid documentation I am tempted to get rid of it. In that case I would have to convince the kernel that this is not a hid drive and create different device class. How would I go about that? After all I would find it cool if it worked for *my* mouse but it would be much cooler if other people could use that software too. Please be easy on me if this is a beginners question - but that is what I am as this is my first attempt for doing some FreeBSD-specific coding. > what version of FreeBSD are you using? This is a 8_RELENG system. Regards Christof -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments signature.asc Description: This is a digitally signed message part. --- End Message --- signature.asc Description: This is a digitally signed message part.
Re: Driver for LEDs on Logitech MX610
Hello Hans, > > Have you looked at libusb? Not yet but I will have a look at libusb2 maybe that will be a little clearer > What version of FreeBSD are you using? this is a RELENG_8 -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments signature.asc Description: This is a digitally signed message part.
Re: usb/143620: the module if_cdce doesn't support my Openmoko Neo FreeRunner anymore
The following reply was made to PR usb/143620; it has been noted by GNATS. From: Christian Neugum To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@freebsd.org Subject: Re: usb/143620: the module if_cdce doesn't support my Openmoko Neo FreeRunner anymore Date: Wed, 10 Feb 2010 16:46:55 +0100 On 02/07/10 09:13, Hans Petter Selasky wrote: > On Sunday 07 February 2010 00:38:31 Christian Neugum wrote: >>> Number: 143620 >>> Category: usb >>> Synopsis: the module if_cdce doesn't support my Openmoko Neo >>> FreeRunner anymore Confidential: no >>> Severity: non-critical >>> Priority: medium >>> Responsible:freebsd-usb >>> State: open >>> Quarter: >>> Keywords: >>> Date-Required: >>> Class: sw-bug >>> Submitter-Id: current-users >>> Arrival-Date: Sat Feb 06 23:40:01 UTC 2010 >>> Closed-Date: >>> Last-Modified: >>> Originator: Christian Neugum >>> Release:8.0-stable >>> Organization: >> >> private person >> >>> Environment: >> >> FreeBSD Chris 8.0-STABLE FreeBSD 8.0-STABLE #1: Sun Jan 10 21:27:41 CET >> 2010 r...@chris:/usr/obj/usr/src/sys/WORKSTATION i386 >> >>> Description: >> >> I've installed FreeBSD 8.0 on my computer and I cannot get my Openmoko Neo >> FreeRunner working with if_cdce. With FreeBSD 7.2 it worked well. After >> loading the if_cdce kernel module I plugged in my FreeRunner but no cdce* >> device is shown in /dev. I've tried different usb ports and loaded the >> module at boottime but the result is the same. >> >>> How-To-Repeat: >> >> $ kldstat >> Id Refs AddressSize Name >> 1 18 0xc040 612ca4 kernel >> 21 0xc0a13000 14f10snd_emu10kx.ko >> 33 0xc0a28000 55730sound.ko >> 41 0xc0a7e000 7551b4 nvidia.ko >> 52 0xc11d4000 2c8d4linux.ko >> $ sudo kldload if_cdce >> $ kldstat >> Id Refs AddressSize Name >> 1 26 0xc040 612ca4 kernel >> 21 0xc0a13000 14f10snd_emu10kx.ko >> 33 0xc0a28000 55730sound.ko >> 41 0xc0a7e000 7551b4 nvidia.ko >> 52 0xc11d4000 2c8d4linux.ko >> 61 0xc8b9b000 6000 if_cdce.ko >> 71 0xc7108000 3000 uether.ko >> <<<--- plugged in my FreeRuner >> $ dmesg >> [...] >> ugen1.2: at usbus1 >> $ ls /dev | grep c >> acd0 >> acd1 >> acpi >> console >> consolectl >> ctty >> devctl >> geom.ctl >> mdctl >> nfslock >> nvidiactl >> pci >> ttyvc >> usbctl >> >>> Fix: > > You need to execute, due to the way the Linux guys designed it. Alternativly > you can add a quirk to the quirks table to do this automatically. > > usbconfig -u 1 a 2 set_config 1 > > --HPS Hi HPS, can you provide me with some more details? I'm not so familiar with this usb stuff. I got it working with the command you mentioned above. But it is limited to the specific usb port, isn't it? You also mentioned a quirk table. Can you provide me with a small howto or a website showing how to add an entry to the quirk table? I haven't found anything in Google. If I've added my device to this table. Do I have to redo those steps after upgrading my system to a newer FreeBSD version? I'm building the new world and kernel from the sources. Hope my questions don't annoy you, but I've no clue where to find the information I need. Regards, Chris ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/143620: the module if_cdce doesn't support my Openmoko Neo FreeRunner anymore
On 02/07/10 09:13, Hans Petter Selasky wrote: > On Sunday 07 February 2010 00:38:31 Christian Neugum wrote: >>> Number: 143620 >>> Category: usb >>> Synopsis: the module if_cdce doesn't support my Openmoko Neo >>> FreeRunner anymore Confidential: no >>> Severity: non-critical >>> Priority: medium >>> Responsible:freebsd-usb >>> State: open >>> Quarter: >>> Keywords: >>> Date-Required: >>> Class: sw-bug >>> Submitter-Id: current-users >>> Arrival-Date: Sat Feb 06 23:40:01 UTC 2010 >>> Closed-Date: >>> Last-Modified: >>> Originator: Christian Neugum >>> Release:8.0-stable >>> Organization: >> >> private person >> >>> Environment: >> >> FreeBSD Chris 8.0-STABLE FreeBSD 8.0-STABLE #1: Sun Jan 10 21:27:41 CET >> 2010 r...@chris:/usr/obj/usr/src/sys/WORKSTATION i386 >> >>> Description: >> >> I've installed FreeBSD 8.0 on my computer and I cannot get my Openmoko Neo >> FreeRunner working with if_cdce. With FreeBSD 7.2 it worked well. After >> loading the if_cdce kernel module I plugged in my FreeRunner but no cdce* >> device is shown in /dev. I've tried different usb ports and loaded the >> module at boottime but the result is the same. >> >>> How-To-Repeat: >> >> $ kldstat >> Id Refs AddressSize Name >> 1 18 0xc040 612ca4 kernel >> 21 0xc0a13000 14f10snd_emu10kx.ko >> 33 0xc0a28000 55730sound.ko >> 41 0xc0a7e000 7551b4 nvidia.ko >> 52 0xc11d4000 2c8d4linux.ko >> $ sudo kldload if_cdce >> $ kldstat >> Id Refs AddressSize Name >> 1 26 0xc040 612ca4 kernel >> 21 0xc0a13000 14f10snd_emu10kx.ko >> 33 0xc0a28000 55730sound.ko >> 41 0xc0a7e000 7551b4 nvidia.ko >> 52 0xc11d4000 2c8d4linux.ko >> 61 0xc8b9b000 6000 if_cdce.ko >> 71 0xc7108000 3000 uether.ko >> <<<--- plugged in my FreeRuner >> $ dmesg >> [...] >> ugen1.2: at usbus1 >> $ ls /dev | grep c >> acd0 >> acd1 >> acpi >> console >> consolectl >> ctty >> devctl >> geom.ctl >> mdctl >> nfslock >> nvidiactl >> pci >> ttyvc >> usbctl >> >>> Fix: > > You need to execute, due to the way the Linux guys designed it. Alternativly > you can add a quirk to the quirks table to do this automatically. > > usbconfig -u 1 a 2 set_config 1 > > --HPS Hi HPS, can you provide me with some more details? I'm not so familiar with this usb stuff. I got it working with the command you mentioned above. But it is limited to the specific usb port, isn't it? You also mentioned a quirk table. Can you provide me with a small howto or a website showing how to add an entry to the quirk table? I haven't found anything in Google. If I've added my device to this table. Do I have to redo those steps after upgrading my system to a newer FreeBSD version? I'm building the new world and kernel from the sources. Hope my questions don't annoy you, but I've no clue where to find the information I need. Regards, Chris ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Huawei E1752 under FreeBSD
Hi, I got this 3G modem, it is not recognised under FreeBSD (tested with fresh 9-CURRENT). I found no relevant information googling for "huawei e1752 freebsd", but "huawei e1752 linux" got me http://www.blogcatalog.com/blog/iwrite-2/dbbfb38ae5ef9ccef8540aad7f9edbd6 and there is part about usb modeswitch, part of config reproduced here: # Huawei E1752 # # Contributor: DefaultVendor= 0x12d1 DefaultProduct= 0x1446 TargetVendor= 0x12d1 TargetProdct= 0x1001 MessageEndpoint=0x01 MessageContent= "55534243001106" It looks like this is the message necessary for switching this device into modem mode, but I have no idea how to issue such command. Also, for my use I need to get this working under 8.0-RELEASE/STABLE. Any hint/help on this one? Regards, Milan ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb_interrupt_read blocks "forever" sometimes
On Wed, 10 Feb 2010, Hans Petter Selasky wrote: > > I have the timeout set to 100 (milliseconds?) yet I find if I > > restart the program every now and then it will get stuck on the > > first read. > > Could you enable debugging for the Host Controller responsible for > your device: > > sysctl hw.ehci.debug=15 > sysctl hw.ohci.debug=15 > sysctl hw.uhci.debug=15 OK the log is a bit big so I've put it at.. http://www.dons.net.au/~darius/wh1080-debug.txt.gz -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: usb_interrupt_read blocks "forever" sometimes
On Wednesday 10 February 2010 10:31:28 Daniel O'Connor wrote: > On Wed, 10 Feb 2010, Hans Petter Selasky wrote: > > I would not recommend using signals with libusb. It is not portable. > > Currently signals are ignored. What you would have to do, is to use > > OK. > > > the timeout argument which you are doing, and have a timekeeper > > variable somewhere, or create another thread. Still, when using the > > timeout there is a chance you can loose data. > > The problem is that the timeout seems to be ignored sometimes - that is > the only reason I was playing with alarm() at all. > > I have the timeout set to 100 (milliseconds?) yet I find if I restart > the program every now and then it will get stuck on the first read. > Could you enable debugging for the Host Controller responsible for your device: sysctl hw.ehci.debug=15 sysctl hw.ohci.debug=15 sysctl hw.uhci.debug=15 --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb_interrupt_read blocks "forever" sometimes
On Wed, 10 Feb 2010, Hans Petter Selasky wrote: > I would not recommend using signals with libusb. It is not portable. > Currently signals are ignored. What you would have to do, is to use OK. > the timeout argument which you are doing, and have a timekeeper > variable somewhere, or create another thread. Still, when using the > timeout there is a chance you can loose data. The problem is that the timeout seems to be ignored sometimes - that is the only reason I was playing with alarm() at all. I have the timeout set to 100 (milliseconds?) yet I find if I restart the program every now and then it will get stuck on the first read. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: usb_interrupt_read blocks "forever" sometimes
On Wednesday 10 February 2010 08:08:08 Daniel O'Connor wrote: > I am trying to talk to my WH1080 weather station and I find that > sometimes when I start the program it will stall forever in > usb_interrupt_read even though the timeout specified is 50 milliseconds. > > I also tried using alarm() but that doesn't cause the transfer to abort > (it appears the libusb code loops and doesn't check for EINTR). > Hi, I would not recommend using signals with libusb. It is not portable. Currently signals are ignored. What you would have to do, is to use the timeout argument which you are doing, and have a timekeeper variable somewhere, or create another thread. Still, when using the timeout there is a chance you can loose data. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Driver for LEDs on Logitech MX610
On Wednesday 10 February 2010 01:59:49 Christof Schulze wrote: > Hello everyone, > > currently I own a logitech mx610 which is a mouse that registers as two > separate USB devices (lsusb -vvv output [3]). One for the regular mouse > usage, > the other for controlling the LEDs that are on the mouse. They do register > as ugen and ums device on FreeBSD. Since I find it cool I would like to > use those > LEDs for various notification purposes. > There is a hack to make use of these LEDs on Linux available [1] which is > not written with portability in mind from what I can tell. So I would like > to get this working on FreeBSD and looked into the matter. It seems like I > want to control those LEDs using usbhid. The manpage however is quite > sketchy and I cannot make heads or tails of it. > I would greatly appreciate some help in getting this to work. I'd like to > know > what I have to do to the device to send the commands needed which are > represented by the control char array given in [1]. > > Thank you very much in advance. > > [1] http://www.kdedevelopers.org/node/2029 > [2] http://lists.alioth.debian.org/pipermail/nut-upsdev/2008- > January/002820.html > [3] http://pastebin.com/f1c76b219 > > kind regards > > Christof > Have you looked at libusb? What version of FreeBSD are you using? --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
