projects
/
pub
/
USBasp.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Update author information.
[pub/USBasp.git]
/
LUFA
/
Drivers
/
USB
/
USB.h
diff --git
a/LUFA/Drivers/USB/USB.h
b/LUFA/Drivers/USB/USB.h
index
c7c60c2
..
35b285c
100644
(file)
--- a/
LUFA/Drivers/USB/USB.h
+++ b/
LUFA/Drivers/USB/USB.h
@@
-7,7
+7,7
@@
*/
/*
*/
/*
- Copyright 201
1
Dean Camera (dean [at] fourwalledcubicle [dot] com)
+ Copyright 201
2
Dean Camera (dean [at] fourwalledcubicle [dot] com)
Permission to use, copy, modify, distribute, and sell this
software and its documentation for any purpose is hereby granted
Permission to use, copy, modify, distribute, and sell this
software and its documentation for any purpose is hereby granted
@@
-158,9
+158,6
@@
* before the class driver is used. Each Device mode Class driver typically contains a set of configuration parameters
* for the endpoint size/number of the associated logical USB interface, plus any class-specific configuration parameters.
*
* before the class driver is used. Each Device mode Class driver typically contains a set of configuration parameters
* for the endpoint size/number of the associated logical USB interface, plus any class-specific configuration parameters.
*
- * \note The \c State section of the \c USB_ClassInfo_* structures are designed to be controlled by the Class Drivers only
- * for maintaining the Class Driver instance's state, and should not normally be altered by the user application.
- *
* The following is an example of a properly initialized instance of the Audio Class Driver structure:
*
* \code
* The following is an example of a properly initialized instance of the Audio Class Driver structure:
*
* \code
@@
-258,9
+255,6
@@
* before the class driver is used. Each Device mode Class driver typically contains a set of configuration parameters
* for the endpoint size/number of the associated logical USB interface, plus any class-specific configuration parameters.
*
* before the class driver is used. Each Device mode Class driver typically contains a set of configuration parameters
* for the endpoint size/number of the associated logical USB interface, plus any class-specific configuration parameters.
*
- * \note The \c State section of the \c USB_ClassInfo_* structures are designed to be controlled by the Class Drivers only
- * for maintaining the Class Driver instance's state, and should not normally be altered by the user application.
- *
* The following is an example of a properly initialized instance of the MIDI Host Class Driver structure:
*
* \code
* The following is an example of a properly initialized instance of the MIDI Host Class Driver structure:
*
* \code