diff options
| author | Dean Camera <dean@fourwalledcubicle.com> | 2010-12-24 17:05:41 +0000 |
|---|---|---|
| committer | Dean Camera <dean@fourwalledcubicle.com> | 2010-12-24 17:05:41 +0000 |
| commit | ec537fd84d6ad3fd0dfa1b55efa2c2d554c1db48 (patch) | |
| tree | 96ae5d0bfaaf096456f83504322dd0ac782793b9 /LUFA/ManPages/CompileTimeTokens.txt | |
| parent | a57287a59f51c53e888068be954f4d8a3f04f52a (diff) | |
| download | lufa-ec537fd84d6ad3fd0dfa1b55efa2c2d554c1db48.tar.gz lufa-ec537fd84d6ad3fd0dfa1b55efa2c2d554c1db48.tar.bz2 lufa-ec537fd84d6ad3fd0dfa1b55efa2c2d554c1db48.zip | |
Re-add in old Endpoint/Pipe workaround for unordered pipes - add new ORDERED_EP_CONFIG compile time option to override the workaround and use the previous behaviour that imposes correct Endpoint/Pipe ordering but produces smaller compiled code.
Diffstat (limited to 'LUFA/ManPages/CompileTimeTokens.txt')
| -rw-r--r-- | LUFA/ManPages/CompileTimeTokens.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/LUFA/ManPages/CompileTimeTokens.txt b/LUFA/ManPages/CompileTimeTokens.txt index 28b7cfc6b..b120617e0 100644 --- a/LUFA/ManPages/CompileTimeTokens.txt +++ b/LUFA/ManPages/CompileTimeTokens.txt @@ -77,6 +77,11 @@ * \section Sec_SummaryUSBTokens General USB Driver Related Tokens * This section describes compile tokens which affect USB driver stack as a whole in the LUFA library. * + * <b>ORDERED_EP_CONFIG</b> - ( \ref Group_EndpointManagement , \ref Group_PipeManagement )\n + * The USB AVRs do not allow for Endpoints and Pipes to be configured out of order; they <i>must</i> be configured in an ascending order to + * prevent data corruption issues. However, by default LUFA employs a workaround to allow for unordered Endpoint/Pipe initialisation. This compile + * time token may be used to restrict the intialisation order to ascending indexes only in exchange for a smaller compiled binary size. + * * <b>NO_STREAM_CALLBACKS</b> - ( \ref Group_EndpointPacketManagement , \ref Group_PipePacketManagement )\n * Both the endpoint and the pipe driver code contains stream functions, allowing for arrays of data to be sent to or from the * host easily via a single function call (rather than complex routines worrying about sending full packets, waiting for the endpoint/ |