1  Copyright (c) 2015 Adafruit Industries
 2  
 3  Permission is hereby granted, free of charge, to any person obtaining a
 4  copy of this software and associated documentation files (the "Software"),
 5  to deal in the Software without restriction, including without limitation
 6  the rights to use, copy, modify, merge, publish, distribute, sublicense,
 7  and/or sell copies of the Software, and to permit persons to whom the
 8  Software is furnished to do so, subject to the following conditions:
 9  
10  The above copyright notice and this permission notice shall be included in
11  all copies or substantial portions of the Software.
12  
13  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
14  OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
16  THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
18  FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
19  DEALINGS IN THE SOFTWARE.
20  
21  ----------------------------------------------------------------------------
22  
23  Additional notes:
24  
25  Since we're asked pretty often: yes, you may use this code (as well as the
26  Adafruit DotStar library) in your product / Kickstarter campaign / etc.
27  provided the license terms are followed.  Please understand the "fitness"
28  and "as-is" aspects -- that your use of this code does not entitle a first-
29  in-line response to bugs, explanations or documentation, feature requests,
30  etc. before or after your product ships.
31  
32  We ask also that you not use the name "DotStar" (an Adafruit trademark) in
33  your product name or campaign -- please use the generic name "APA102" when
34  referring to the addressable LEDs.  Similarly, be mindful of Flowtoys'
35  trademarks in this field (though not involved in this software, references
36  to their components are made in the corresponding Adafruit Learning System
37  guide).
38  
39  In short: include attribution/license in distributed code, test a lot, know
40  enough C to solve problems, stay clear of trademarks and everything's cool.
41  Enjoy!  We look forward to seeing what you make of it!