On Wed, 2010-02-17 at 09:57 -0800, Greg KH wrote: > On Tue, Feb 16, 2010 at 10:36:21PM -0800, Dan Williams wrote: > > On Tue, 2010-02-16 at 20:54 -0800, Greg KH wrote: > > > On Tue, Feb 16, 2010 at 06:39:26PM -0800, Dan Williams wrote: > > > > Hi, > > > > > > > > This short series adds some device IDs for CDMA/EVDO devices that are > > > > normally driven by CDC-ACM, but also provide an additional serial port > > > > that talks a proprietary Qualcomm protocol, QCDM. We now know enough of > > > > QCDM to start using these ports for radio status and signal strength > > > > when the CDC-ACM port is being used for PPP. > > > > > > Great, but how are we going to keep these devices from binding to the > > > cdc-acm module if it is loaded first? Do we need to blacklist them in > > > that driver at the same time? > > > > I don't think we care. The CDC-ACM part will be driven by cdc-acm, and > > the QCDM part gets driven by option.ko in parallel with the CDC-ACM. > > With these patches applied, you have both /dev/ttyACM0 (AT capable) > > and /dev/ttyUSB0 (QCDM capable). Somewhat like how the Ericsson "mbm" > > modems are concurrently driven by the cdc-wdm, cdc-ether, and cdc-acm > > class drivers all at the same time. > > Ah, ok, that makes sense. I'll go queue up the patches in a few hours. Actually just keep #1, but drop 2 - 4. I'll follow Oliver's suggestion and do a smaller moto-modem-like driver for QCDM ports on these devices. Dan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
