-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 6 Jul 2003 18:47 pm, Mike Harris wrote: > The existing ACM driver does not bind to the ACM subinterface because: > - It assumes that an ACM device will have a configuration consisting of > only two interfaces (ACM control & data) There is some better CDC parsing code available, which could be grafted onto the ACM driver. See the old cdc-ether driver.
> - It assumes the ACM interfaces are #0 and #1 in the configuration This would be trivial to fix - you can read it from the CDC descriptor. > - It assumes that the protocol will be == 1. According to the CDC_WMC10 > spec they could be 2-6 (all variants of AT command set). 3G mobiles will > implement 3gpp 27.007, which is protocol class 5. The reason for this is that people expect to use AT commands, which IIRC is the protocol 1. > I have not checked the audio driver. I guess drivers need to be written > for OBEX & other new goodies defined in the standard. Presumably you can do at least the OBEX stuff in userspace. I think that there is an project working on this (OpenOBEX?). Also, it would be worth looking at the bluetooth stuff, which is targetted at a very similar problem space, and uses at least some of the same buzzwords. Do you actually have hardware that implements the standard? Can you say what it is? Brad -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/B/EaW6pHgIdAuOMRAt9RAKCKEhwAvGD+5ZqODSjIokgQeOi8HQCePOMe hZX18tYxiC7x8lCask0/kzI= =VAzC -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
