Date: Tue, 14 Dec 2010 08:25:19 +0100 From: Rene Ladan <rene@freebsd.org> To: Hans Petter Selasky <hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: Lego NXT brick communication error with libusb Message-ID: <4D071BDF.9010300@freebsd.org> In-Reply-To: <201012140508.09787.hselasky@c2i.net> References: <4D054F76.1080401@freebsd.org> <201012131151.25655.hselasky@c2i.net> <4D0680D7.10007@freebsd.org> <201012140508.09787.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Op 14-12-2010 05:08, Hans Petter Selasky schreef: > On Monday 13 December 2010 21:23:51 Rene Ladan wrote: >> Op 13-12-2010 11:51, Hans Petter Selasky schreef: >>> On Sunday 12 December 2010 23:40:54 Rene Ladan wrote: >>>> Hi, >>>> >>>> I am writing a port [1] to control the Lego NXT brick with ROS, but when >>>> I run a test program it fails (permissions for the USB device are 666). >>> >>>> This is on: >>> What dmesg is shown? Are other [kernel] drivers hooking into the USB >>> interfaces used by your user-land driver? >> >> dmesg shows just: >> ugen3.2: <vendor 0x0694> at usbus3 >> Vendor 0x0694 is Lego. >> >> I don't have other drivers hooking into the USB device I think: >> % kldstat -v | grep usb >> 276 usbus/uhub >> 275 uhub/usb_linux >> 273 uss820/usbus >> 272 musbotg/usbus >> 271 at91_udp/usbus >> 270 xhci/usbus >> 269 ehci/usbus >> 268 uhci/usbus >> 267 ohci/usbus >> >>> What is output from usbconfig -d X.Y dump_device_desc >>> dump_curr_config_desc >> >> Attached. >> >> Rene > > What happens if you remove that device reset line from your driver? > That does the trick, reading sensor data as user now works :) So on Linux this reset line is harmless, but on FreeBSD it has to be removed. Rene -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D071BDF.9010300>