Re: static usb device configuration

2010-12-13 Thread Hans Petter Selasky
On Monday 13 December 2010 08:58:15 Emanuel Haupt wrote:
 Hans Petter Selasky hsela...@c2i.net wrote:
  On Sunday 12 December 2010 19:49:24 Emanuel Haupt wrote:
   Is there any way I can make sure that the following device:
   
   ugen1.3: product 0x6001 vendor 0x0403 at usbus1, cfg=0 md=HOST
   spd=FULL (12Mbps) pwr=ON
   
 bLength = 0x0012
 bDescriptorType = 0x0001
 bcdUSB = 0x0200
 bDeviceClass = 0x
 bDeviceSubClass = 0x
 bDeviceProtocol = 0x
 bMaxPacketSize0 = 0x0008
 idVendor = 0x0403
 idProduct = 0x6001
 bcdDevice = 0x0400
 iManufacturer = 0x  no string
 iProduct = 0x  no string
 iSerialNumber = 0x0003  Reader 195
 bNumConfigurations = 0x0001
   
   Is always registered as:
   
   /dev/usb/1.3.0
  
  No, this is currently not possible unless you find the USB port which
  is enumerated first (I.E. has the lowest second number.)
 
 When you say 'currently', is there something like that planed?

No.

--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: Lego NXT brick communication error with libusb

2010-12-13 Thread Hans Petter Selasky
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?

What is output from usbconfig -d X.Y dump_device_desc dump_curr_config_desc

--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


Current problem reports assigned to freebsd-usb@FreeBSD.org

2010-12-13 Thread FreeBSD bugmaster
Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker  Resp.  Description

o usb/152892   usbNot updating /etc files in installer FreeBSD-8.2-BETA1
o usb/152075   usb[usb8] [ehci] Add quirk for CS5536 USB
o usb/150989   usb[patch] Add Netgear WG111V2_2 support to upgt(4)
o usb/150892   usb[zyd] Whenever network contacted in any shape, way or 
p usb/150546   usblibusb(3) libusb_control_transfer() prototype is incor
o usb/150401   usb[umass] [usb8] Errors from USB drives mixed between UF
o usb/150189   usb[run] [usb8] [patch] if_run appears to corrupt IP traf
p usb/149934   usb[patch] [usb8] Transcend JetFlash V85 poor performance
o usb/149900   usb[uftdi] [patch] FreeBSD 8.1 uftdi patch to support usb
p usb/149764   usb[u3g] [patch] usbdevs update: Huawei K3765 3G modem
o usb/149675   usb[uftdi] [usb_serial] doesn't react to break properly
o usb/149528   usb[zyd] Wireless USB stick not detected - vendor id 0x08
o usb/149283   usb[uftdi] avrdude unable to talk to Arduino board (via u
o usb/149162   usb[ural] ASUS WL-167g doesn't work in 8.1 (continue of 1
s usb/148702   usb[usb8] [request] IO DATA USB-RSAQ5 support on FreeBSD-
o usb/148080   usbusbconfig(8) sometimes does not turn off the device
o usb/147516   usb[umass] [usb67] kernel unable to deal with Olympus USB
o i386/147475  usb[install] FreeBSD 8.x does not install on ASUS K8N4-E 
p usb/146871   usb[usbdevs] [usb8] [patch] provide descriprive string fo
o usb/146840   usb[hang] FreeBSD 7.2 / 7.3 / 8.0 hang at startup after e
o usb/146153   usb[axe] [usb8] Hosts in network doesn't receive any pack
o usb/146054   usb[urtw] [usb8] urtw driver potentially out of date
f usb/145513   usb[usb8] New USB stack: no new devices after forced usb 
p usb/145455   usb[usb8] [patch] USB debug support cannot be disabled
o usb/145415   usb[umass] [usb8] USB card reader does not create slices 
a usb/145184   usbGENERIC can't mount root from USB on Asus EEE
o usb/145165   usb[keyboard] [usb8] ukbd_set_leds_callback: error=USB_ER
f kern/144938  usb[keyboard] [boot] Boot Failure with Apple (MB869LL/A) 
o usb/144387   usb[run] [panic] if_run panic
o usb/144043   usb[umass] [usb8] USB DLT tape drive throws random errors
a usb/143790   usb[boot] [cam] can not boot from usb hdd
f usb/143620   usb[cdce] [usb8] the module if_cdce doesn't support my Op
f usb/143294   usb[usb8] copying process stops at some time (10 - 50 sec
o usb/143286   usb[ukbd] [usb8] [boot] boot failures on RELENG_8 system 
p usb/143186   usb[usbdevs] [usb8] [patch] add USB device IDs for Google
a usb/143139   usb[umass] [usb8] [patch] Quirk for Century EX35SW4_SB4 J
o usb/143045   usb[umass] [usb8] [patch] mounting Fujitsu 2600Z camera d
o usb/142991   usb[uftdi] [usb67] [patch] Patch to add Crystalfontz 533 
f usb/142989   usb[usb8] canon eos 50D attaches but detaches after few s
f usb/142957   usb[umass] [usb8] [patch] patch for USB disk SYNCHRONIZE 
o usb/142719   usb[urtw] [usb8] AirLive WL-1600USB (RTL8187L chipset) fa
o usb/142713   usb[usb67] [panic] Kernel Panik when connecting an IPhone
f usb/142276   usb[umass] [usb8] Cache Synchronization Error with Olympu
o usb/142229   usb[ums] [usb8] [hang] connecting a USB mouse to a Dell P
o usb/141777   usb[usb8] [usbdevs] [rum] [patch] Support usbdevs / rum(4
f usb/141680   usb[uath] [usb8] Netgear WG111T not working with uath dri
o usb/141664   usb[pcm] [usb8] Logitech USB microphone failure [regressi
o usb/141474   usb[boot] [usb8] FreeBSD 8.0 can not install from USB CDR
o usb/141327   usb[ukbd] [usb67] USB kbd not working with 7.1+PAE on IBM
o usb/141212   usb[ukbd] [usb8] ukbd_set_leds_callback:700: error=USB_ER
o kern/141011  usb[usb8] Encrypted root, geli password at boot; enter ke
o usb/140920   usb[install] [usb8] USB based install fails on 8.0-RELEAS
o usb/140893   usb[urtw] [usb8] WPA2 not working on rtl8187b
o kern/140849  usb[ums] [usb8] USB mouse doesn't work under FreeBSD 8.0-
a usb/140810   usb[uftdi] [usb8] 8.X copy and paste problem / tty overfl
o usb/140477   usb[umass] [usb8] [patch] allow boot-time attachment of d
o usb/140236   usb[msdosfs] [usb8] Labels wiped on external Journaled US
o usb/140160   usb[usb8] [acpi] USB ports are no longer active after A

Re: 8.2-PRERELESE ifconfig_bridge has no members unless run from rc.local

2010-12-13 Thread Kim Culhan
On Wed, Dec 8, 2010 at 12:58 PM, John Baldwin j...@freebsd.org wrote:

  On Wednesday, December 08, 2010 11:29:49 am Kim Culhan wrote:
  On Wed, Dec 8, 2010 at 9:23 AM, John Baldwin j...@freebsd.org wrote:
 
On Tuesday, December 07, 2010 5:17:30 pm Kim Culhan wrote:
Had been running a wireless bridge for some months in rc.conf:
   
ifconfig_bridge0=addm wlan0 addm re1 up
   
Updated to 8.2-PRERELEASE 2 days ago and when the machine boots
the bridge has no members.
   
Reversing the order of the members results in the bridge having just
the re1 member.
   
Running the above command from a shell works and running from
an rc.local file also works.
   
FWIW, running from a shell there is about a 3 second delay after hit
   enter
before it returns the shell prompt, members are then present.
   
The lines in rc.conf:
   
cloned_interfaces=bridge0
ifconfig_wlan0=inet 192.168.1.50/24 channel 11
wlans_rum0=wlan0
create_args_wlan0=wlanmode hostap mode 11g
ifconfig_bridge0=addm wlan0 addm re1 up
   
Tried replacing the re device with em, no change.
   
Any help is very greatly appreciated.
  
   Most likely the bridge0 device is created by /etc/rc.d/netif before the
   wlan0
   device is created, so when the system startup tries to configure
 bridge0,
   the
   ifconfig statement fails.
  
   What does 'ifconfig -l' show after you have booted?
  
  It shows:
 
  re0 em0 plip0 lo0 bridge0
 
  On the console at boot there is, after the file partition status and
 setting
  the hostname:
  ifconfig: BRDGADD wlan0: No such file or directory
 
  Following this is:
 
  Starting Network: lo0 re0 em0 bridge0
 
  Which is followed by output the same as from ifconfig -a including
 bridge0
  which
  has no members.
 
  Next is:
 
  Starting Network: rum0
  rum0: flags=8843UP, BROADCAST  etc

 Hmm, I wonder why rum0 shows up so late.  Do you not plug it in until after
 boot, or does it depend on devd loading firmware into the device, etc.?

Working with Freebsd 8.2-BETA1 it was found:

The rum0 device can be made to show up just after:
Mounting local file systems:.
With the bridge having members present also depending on whether
a mouse or keyboard is attached, which usb port it is attached to and
to which usb port the rum device is attached.

Since this appears to be a usb issue I can move this to the usb list.

thanks
-kim
___
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: static usb device configuration

2010-12-13 Thread Peter Jeremy
On 2010-Dec-13 08:56:51 +0100, Emanuel Haupt eha...@freebsd.org wrote:
Unfortunately the program in question uses libusb and the configuration
only allows to define the device by specifying busnum:devaddr and
there are multiple identical devices around with only iSerialNumber
being different from each other. Somehow I need to make sure the
devices in the USB hub are always recognized in the same order.

The standard approach seems to be to iterate through all available USB
devices until you find the one that matches your specifications.

-- 
Peter Jeremy


pgp0B07afpudf.pgp
Description: PGP signature


Re: Lego NXT brick communication error with libusb

2010-12-13 Thread Rene Ladan
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
-- 
http://www.rene-ladan.nl/

GPG fingerprint = ADBC ECCD EB5F A6B4 549F  600D 8C9E 647A E564 2BFC
(subkeys.pgp.net)
ugen3.2: product 0x0002 vendor 0x0694 at usbus3, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x 
  bDeviceSubClass = 0x 
  bDeviceProtocol = 0x 
  bMaxPacketSize0 = 0x0008 
  idVendor = 0x0694 
  idProduct = 0x0002 
  bcdDevice = 0x 
  iManufacturer = 0x  no string
  iProduct = 0x  no string
  iSerialNumber = 0x0001  0016530CA81C
  bNumConfigurations = 0x0001 


 Configuration index 0

bLength = 0x0009 
bDescriptorType = 0x0002 
wTotalLength = 0x0020 
bNumInterfaces = 0x0001 
bConfigurationValue = 0x0001 
iConfiguration = 0x  no string
bmAttributes = 0x00c0 
bMaxPower = 0x 

Interface 0
  bLength = 0x0009 
  bDescriptorType = 0x0004 
  bInterfaceNumber = 0x 
  bAlternateSetting = 0x 
  bNumEndpoints = 0x0002 
  bInterfaceClass = 0x00ff 
  bInterfaceSubClass = 0x00ff 
  bInterfaceProtocol = 0x00ff 
  iInterface = 0x  no string

 Endpoint 0
bLength = 0x0007 
bDescriptorType = 0x0005 
bEndpointAddress = 0x0001  OUT
bmAttributes = 0x0002  BULK
wMaxPacketSize = 0x0040 
bInterval = 0x 
bRefresh = 0x 
bSynchAddress = 0x 

 Endpoint 1
bLength = 0x0007 
bDescriptorType = 0x0005 
bEndpointAddress = 0x0082  IN
bmAttributes = 0x0002  BULK
wMaxPacketSize = 0x0040 
bInterval = 0x 
bRefresh = 0x 
bSynchAddress = 0x 



___
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: Lego NXT brick communication error with libusb

2010-12-13 Thread Hans Petter Selasky
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?

--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: Lego NXT brick communication error with libusb

2010-12-13 Thread Rene Ladan
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)
___
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