Date: Wed, 6 Oct 2004 14:41:14 -0400 From: Brian Fundakowski Feldman <green@freebsd.org> To: Mathew Kanner <mat@cnd.mcgill.ca> Cc: hackers@freebsd.org Subject: Re: attaching ugen(4) on multi interface USB devices Message-ID: <20041006184114.GL47017@green.homeunix.org> In-Reply-To: <20041006134849.GA87467@cnd.mcgill.ca> References: <cone.1097065805.20394.26649.1001@niked.office.suresupport.com> <20041006134849.GA87467@cnd.mcgill.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 06, 2004 at 09:48:49AM -0400, Mathew Kanner wrote: > On Oct 06, Niki Denev wrote: > > 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 :) > > I seem to recall a problem with ugen that it doesn't discover > endpoints on alt-interfaces. I've posted patches to this mailing list > to work around the problem. It doesn't work when you call USB_SET_ALTINTERFACE then USB_SET_CONFIG? -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041006184114.GL47017>