+ * \note There are several major drawbacks to the CDC-ACM standard USB class, however\r
+ * it is very standardized and thus usually available as a built-in driver on\r
+ * most platforms, and so is a better choice than a proprietary serial class.\r
+ * \r
+ * One major issue with CDC-ACM is that it requires two Interface descriptors,\r
+ * which will upset most hosts when part of a multi-function "Composite" USB\r
+ * device, as each interface will be loaded into a separate driver instance. To\r
+ * conbat this, you should use the "Interface Association Descriptor" addendum to\r
+ * the USB standard which is available on most OSes when creating Composite devices.\r
+ *\r
+ * Another major oversight is that there is no mechanism for the host to notify the\r
+ * device that there is a data sink on the host side ready to accept data. This\r
+ * means that the device may try to send data while the host isn't listening, causing\r
+ * lengthy blocking timeouts in the transmission routines. To combat this, it is\r
+ * recommended that the virtual serial line DTR (Data Terminal Ready) be used where\r
+ * possible to determine if a host application is ready for data.\r
+ *\r