On 10/14/2015 3:35 PM, Gedare Bloom wrote:
I don't have a problem on the surface of it, but can we get a clear
statement of the licensing for the included code?
The patch is huge but includes the license in pdf and rtf format.
Based on the one source file I looked at, the license is BSD
w/advertising. I am not sure if this is the same with all files.
This is a cut and paste from a file added:
+ * <h2><center>© COPYRIGHT(c) 2015 STMicroelectronics</center></h2>
+ *
+ * Redistribution and use in source and binary forms, with or without
modification,
+ * are permitted provided that the following conditions are met:
+ * 1. Redistributions of source code must retain the above copyright
notice,
+ * this list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright
notice,
+ * this list of conditions and the following disclaimer in the
documentation
+ * and/or other materials provided with the distribution.
+ * 3. Neither the name of STMicroelectronics nor the names of its
contributors
+ * may be used to endorse or promote products derived from this
software
+ * without specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS"
+ * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE
+ * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR
+ * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER
+ * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY,
+ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE
+ * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ *
On Mon, Sep 28, 2015 at 4:25 PM, Isaac Gutekunst
<isaac.guteku...@vecna.com> wrote:
Hi Devel,
As mentioned earlier, Vecna has developed two BSP families using the HAL
code provide by ST as a foundation. The code isn't perfect, but it let us
get up to speed very fast, and provides a consistent abstraction across a
number of processors.
I formatted a giant patch with all the relevant files needed for the new
BSP
that will be arriving later. The plan is to get this code approved and
merged, and then add the BSP piece by piece to reduce the amount of code
coming in at once.
This includes some HAL files that we aren't using in the BSP just yet.
Let
me know if we should remove them. It's a rather absurd amount of code :)
As before, I can't get git-send-email to work. In addition, the patches
are
giant, so I've inserted links to files in Google Drive.
https://drive.google.com/open?id=0BxaqNLUoI5onZ3lUUDNrYXlyX1U
https://drive.google.com/open?id=0BxaqNLUoI5onM3JsenRJRkotWm8
--
Isaac Gutekunst
Embedded Systems Software Engineer
isaac.guteku...@vecna.com
www.vecna.com
Cambridge Research Laboratory
Vecna Technologies, Inc.
36 Cambridge Park Drive
Cambridge, MA 02140
Office: (617) 864-0636 x3069
Fax: (617) 864-0638
http://vecna.com
Better Technology, Better World (TM)
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherr...@oarcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
