Date: Wed, 06 Oct 2004 15:30:05 +0300 From: Niki Denev <nike_d@cytexbg.com> To: hackers@freebsd.org Subject: attaching ugen(4) on multi interface USB devices Message-ID: <cone.1097065805.20394.26649.1001@niked.office.suresupport.com>
next in thread | raw e-mail | index | archive | help
This is a MIME GnuPG-signed message. If you see this text, it means that your E-mail or Usenet software does not support MIME signed messages. --=_mimegpg-niked.office.suresupport.com-26649-1097065805-0001 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Hello everyone!, The last 1-2 days i've been trying to make some userspace OBEX utilities to work with a USB based Nokia GSM phone and doing this i discovered something that confuses me a little: The phone in question is Nokia 6230 and it has an USB interface. The phone has 11 interface descriptors, 2 of them are used for the Modem and CM over data. Judging from the windows drivers it seems that four of the other interfaces are OBEX compatible. But if i kldload umodem and plug the phone it detects only one ucom(4). and if i plug the phone without any u* modules loaded the kernel attaches ugen0 only. >From what i understand it attaches the ugen0 using the info in the first interface descriptor in the device. Wouldn't it be more usefull for the kernel to attach ugen for every unknown interface in a device. For example when attaching the phone with umodem loaded, i will get the ucom(4) device and the other unrecognised interfaces will show up as ugens ? What do you think about that? P.S.: anyone know some good way to list the attached usb devices beyond usbdevs? It seems that the information that can be gathered from usbdevs is very limited. For example 'lsusb' in linux can show much more info. What do you think about that too? Thanks in advance for any info and/or flames :) --niki --=_mimegpg-niked.office.suresupport.com-26649-1097065805-0001 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBY+VNHNAJ/fLbfrkRAgpqAJ9+X03U6d7AiEjXNcx6fJ3GHu9nWQCggChE tAEZPCuEXFWEClLH44n+dCc= =+oe1 -----END PGP SIGNATURE----- --=_mimegpg-niked.office.suresupport.com-26649-1097065805-0001--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cone.1097065805.20394.26649.1001>