From a5849bb91060284dc6a7c3cd536ff2210662020e Mon Sep 17 00:00:00 2001 From: patacongo Date: Fri, 27 Jan 2012 21:03:20 +0000 Subject: Most USB Composite device debug git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4344 42af7a65-404d-4744-a932-0658087f49c3 --- nuttx/Documentation/NuttxPortingGuide.html | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) (limited to 'nuttx/Documentation') diff --git a/nuttx/Documentation/NuttxPortingGuide.html b/nuttx/Documentation/NuttxPortingGuide.html index 9c1dd07c9..9b0c60ce7 100644 --- a/nuttx/Documentation/NuttxPortingGuide.html +++ b/nuttx/Documentation/NuttxPortingGuide.html @@ -4940,6 +4940,15 @@ build unique and contiguous. When used with the Mass Storage driver, the correct value for this offset is zero. +
  • + CONFIG_CDCACM_STRBASE: + If the CDC driver is part of a composite device, then this may need to + be defined to offset the CDC/ACM string numbers so that they are + unique and contiguous. When used with the Mass Storage driver, the + correct value for this offset is four (this value actuallly only needs + to be defined if names are provided for the Notification interface, + CONFIG_CDCACM_NOTIFSTR, or the data interface, CONFIG_CDCACM_DATAIFSTR). +
  • CONFIG_CDCACM_EP0MAXPACKET: Endpoint 0 max packet size. Default 64.
  • @@ -5010,6 +5019,14 @@ build correct value for this offset is two (because of the two CDC/ACM interfaces that will precede it). +
  • + CONFIG_USBMSC_STRBASE: + If the CDC driver is part of a composite device, then this may need to + be defined to offset the mass storage string numbers so that they are + unique and contiguous. When used with the CDC/ACM driver, the + correct value for this offset is four (or perhaps 5 or 6, depending + on if CONFIG_CDCACM_NOTIFSTR or CONFIG_CDCACM_DATAIFSTR are defined). +
  • CONFIG_USBMSC_EP0MAXPACKET: Max packet size for endpoint 0 -- cgit v1.2.3