> Then why would you make this CDC ACM, instead of just using a custom > interface that you control completely?
Couple reasons: This is chip is a drop in replacement on our hardware and won't require any adjustments to the firmware running on the device. Also, I didn't have much influence on the decision. > How are you going to avoid specifying a COM port across platforms? Not sure how to take this. Sounds a bit cynical. I'm currently using libusb/WinUSB on Windows to communicate with my device w/o specifying a COM port. Considering COM ports are in general a Windows only topic, I guess this is already accomplished. But as I'm not yet a 'Software Wizard' and admittedly very ignorant on this entire subject, I welcome any insight those with more experience than myself can offer. I've come to realize that CDC ACM is meant for networking devices, for which mine is not. However, I do appear to be able to accomplish what I want using bulk transfers via Libusbx. Are there major issues with this that I'm not aware of? ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
