Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
lufa
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Erik Strand
lufa
Commits
33a81bff
Commit
33a81bff
authored
Mar 5, 2011
by
Dean Camera
Browse files
Options
Downloads
Patches
Plain Diff
Minor documentation updates.
parent
c1c94fe5
No related branches found
No related tags found
No related merge requests found
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
LUFA/ManPages/ChangeLog.txt
+4
-1
4 additions, 1 deletion
LUFA/ManPages/ChangeLog.txt
LUFA/ManPages/LUFAvsAtmelStack.txt
+10
-4
10 additions, 4 deletions
LUFA/ManPages/LUFAvsAtmelStack.txt
LUFA/ManPages/WhyUseLUFA.txt
+2
-5
2 additions, 5 deletions
LUFA/ManPages/WhyUseLUFA.txt
with
16 additions
and
10 deletions
LUFA/ManPages/ChangeLog.txt
+
4
−
1
View file @
33a81bff
...
...
@@ -14,7 +14,7 @@
* - Added a new general RingBuff.h miscellaneous ring buffer library driver header
* - Added new GCC_FORCE_POINTER_ACCESS() macro to correct GCC's mishandling of struct pointer accesses
* - Added basic driver example use code to the library documentation
* - Added new Endpoint_Null_Stream() and Pipe_Null_
s
tream() functions
* - Added new Endpoint_Null_Stream() and Pipe_Null_
S
tream() functions
* - Added new ADC_GET_CHANNEL_MASK() convenience macro
* - Added new HID report item macros (with HID_RI_ prefix) to allow for easy creation and editing of HID report descriptors
* - Added new HID_DESCRIPTOR_MOUSE, HID_DESCRIPTOR_KEYBOARD, HID_DESCRIPTOR_JOYSTICK and HID_DESCRIPTOR_VENDOR macros
...
...
@@ -80,6 +80,9 @@
* error code enum (thanks to Daniel Seibert)
* - Fixed ReportID not being removed from the feature/out report data array in the HID class driver when Report IDs are used
* - Fixed incorect BUTTONS_BUTTON1 definition for the Minimus board
* - Fixed Still Image Host class driver exiting the descriptor search routine prematurely if the data pipes (but not event pipe)
* is found
* - Fixed missing call to Pipe_SetInfiniteINRequests() in the Pipe_ConfigurePipe() routine
* - Library Applications:
* - Fixed Benito project discarding incoming data from the USB virtual serial port when the USART is busy
* - Fixed broken DFU bootloader, added XPLAIN support for bootloader start when XCK jumpered to ground
...
...
This diff is collapsed.
Click to expand it.
LUFA/ManPages/LUFAvsAtmelStack.txt
+
10
−
4
View file @
33a81bff
...
...
@@ -5,11 +5,11 @@
*/
/**
* \page Page_LUFAvsAtmelStack LUFA vs the Atmel Stack
* \page Page_LUFAvsAtmelStack LUFA vs the Atmel
8-bit USB AVR
Stack
*
* Atmel offers an official USB AVR stack, which may be incorporated into user projects and products. As LUFA and the Atmel
* stack aims to give roughly the same functionality to a design, it is often asked what advantages LUFA carries over the
*
official
Atmel USB stack. Below are just some of the advantages to choosing LUFA over the official stack.
* Atmel offers an official
8-bit
USB AVR stack, which may be incorporated into user projects and products. As LUFA and the Atmel
* stack aims to give roughly the same functionality to a design, it is often asked what advantages LUFA carries over the
official
* Atmel USB stack
for the 8-bit USB AVRs
. Below are just some of the advantages to choosing LUFA over the official
Atmel
stack.
*
* - <b>Licensing:</b>
* LUFA is released under a very permissive MIT license (see \ref Page_LicenseInfo), while the Atmel stack carries several
...
...
@@ -42,5 +42,11 @@
* - <b>Better Library Support:</b>
* As many people are now using LUFA, there is a community being built around it. You can get answers to your LUFA related questions
* quickly by either emailing the library author (subject to author's schedule) or by posting to the official LUFA support mailing list.
*
* - <b>More Compact Code:</b>
* LUFA is written from the ground up to compile optimally, using clean code and good design. Two demos giving the same functionality -
* the LUFA Low Level API Mouse Demo vs. the Atmel AVR270 HID Mouse application note shows LUFA to be the clear size winner *.
*
* * <i>LUFA Low Level Mouse Demo: 3510 bytes, Atmel AVR270 Mouse Application Note: 4222 bytes, using an identical build environment.</i>
*/
This diff is collapsed.
Click to expand it.
LUFA/ManPages/WhyUseLUFA.txt
+
2
−
5
View file @
33a81bff
...
...
@@ -32,15 +32,12 @@
* seconds each time a new release is made.
*
* - <b>Size:</b>
* Not just requiring less code to make complex USB devices, LUFA
(under most case
s wit
h the correct compile options)
*
requires less FLASH space than Atmel's stack, meaning more space for the user application*
.
* Not just requiring less code to make complex USB devices, LUFA
i
s w
r
it
ten to compile down as much as possible into
*
optimal code, to occupy only a small space for its feature set
.
*
* - <b>Support:</b>
* Since many people are now using LUFA in their own projects, you can take advantage of other's knowledge when you run
* into difficulties or need some advice. In addition, you can also email the library author to receive personalized
* support when you need it (subject to author's schedule).
*
* <small>* Atmel Stack Mouse Device Demo 4218 bytes, LUFA Mouse Low Level Device Demo 3526 bytes, under identical build
* environments</small>
*/
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
sign in
to comment