Re: [avr-libc-dev] avr-lib-c-extentions library

2008-01-07 Thread David Bourgeois
Hi folks, On Wed, 02 Jan 2008 22:12:37 +0100, Joerg Wunsch [EMAIL PROTECTED] wrote: My major criteria for inclusion would be: . general usability (i.e. covers at least a good number of AVRs if not all of them) . same license as avr-libc to improve re-usability in closed source projects

RE: [avr-libc-dev] avr-lib-c-extentions library

2008-01-07 Thread Weddington, Eric
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] org] On Behalf Of David Bourgeois Sent: Monday, January 07, 2008 9:33 AM To: avr-libc-dev@nongnu.org Subject: Re: [avr-libc-dev] avr-lib-c-extentions library Hi folks, On Wed, 02 Jan 2008 22:12:37 +0100

Re: [avr-libc-dev] avr-lib-c-extentions library

2008-01-07 Thread Rick Altherr
On Jan 7, 2008, at 10:27 AM, Weddington, Eric wrote: - a circular buffer (I spent quite some time on this one to get it clean and optimized.) I also have a ring buffer implementation that's been tested. - an I2C library (I made one inspired from Procyon AVRlib but want to rebuild a new one

Re: [avr-libc-dev] avr-lib-c-extentions library

2008-01-04 Thread David Brown
Weddington, Eric wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] org] On Behalf Of David Brown Sent: Thursday, January 03, 2008 1:30 AM To: avr-libc-dev@nongnu.org Subject: Re: [avr-libc-dev] avr-lib-c-extentions library Weddington, Eric wrote: . same

RE: [avr-libc-dev] avr-lib-c-extentions library

2008-01-03 Thread Weddington, Eric
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] org] On Behalf Of David Brown Sent: Thursday, January 03, 2008 1:30 AM To: avr-libc-dev@nongnu.org Subject: Re: [avr-libc-dev] avr-lib-c-extentions library Weddington, Eric wrote: . same license as avr

Re: [avr-libc-dev] avr-lib-c-extentions library

2008-01-03 Thread Joerg Wunsch
As Weddington, Eric wrote: You're going to have to back up your claims on this one. I have never seen, nor heard of such a limitation. It's also what I recall from my last reading of the LGPL (which has arguably been quite some time ago). The official reasoning for the requirement to ship

RE: [avr-libc-dev] avr-lib-c-extentions library

2008-01-03 Thread Weddington, Eric
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] org] On Behalf Of Joerg Wunsch Sent: Thursday, January 03, 2008 12:12 PM To: avr-libc-dev@nongnu.org Subject: Re: [avr-libc-dev] avr-lib-c-extentions library FYI, the libgcc library that ships with GCC

Re: [avr-libc-dev] avr-lib-c-extentions library

2008-01-03 Thread Joerg Wunsch
As Weddington, Eric wrote: Thanks for the reminder; you're right it's GPL+exception. Then I would be OK with a library having such a license. I find it quite complicated, compared to the plain old BSD-style license we've been using for avr-libc for years now. Is there any specific reason you

RE: [avr-libc-dev] avr-lib-c-extentions library

2008-01-03 Thread Weddington, Eric
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] org] On Behalf Of Joerg Wunsch Sent: Thursday, January 03, 2008 12:42 PM To: avr-libc-dev@nongnu.org Subject: Re: [avr-libc-dev] avr-lib-c-extentions library As Weddington, Eric wrote: Thanks

Re: [avr-libc-dev] avr-lib-c-extentions library

2008-01-02 Thread Joerg Wunsch
As Weddington, Eric wrote: Dean Camera wrote: What sort of contributions did you have in mind? Would the util library code be moved over to the new library? How would you imagine it structured? I really thought of things that are currently available in libraries like Procyon AVRlib.

RE: [avr-libc-dev] avr-lib-c-extentions library

2008-01-02 Thread Weddington, Eric
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] org] On Behalf Of Joerg Wunsch Sent: Wednesday, January 02, 2008 2:13 PM To: avr-libc-dev@nongnu.org Subject: Re: [avr-libc-dev] avr-lib-c-extentions library As Weddington, Eric wrote: Dean Camera

RE: [avr-libc-dev] avr-lib-c-extentions library

2008-01-02 Thread Rich Teer
On Wed, 2 Jan 2008, Weddington, Eric wrote: I'm open to having the LGPL license on such a library project. (Definitely not the GPL, though.) I can be persuaded to either the BSD or LGPL license. There's another (I'd argue, better) alternative: the CDDL. Certianly worth evaluating... --

RE: [avr-libc-dev] avr-lib-c-extentions library

2008-01-02 Thread Weddington, Eric
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] org] On Behalf Of Joerg Wunsch Sent: Wednesday, January 02, 2008 3:00 PM To: avr-libc-dev@nongnu.org Subject: Re: [avr-libc-dev] avr-lib-c-extentions library As Rich Teer wrote: There's another (I'd

Re: [avr-libc-dev] avr-lib-c-extentions library

2008-01-02 Thread David Brown
Weddington, Eric wrote: . same license as avr-libc to improve re-usability in closed source projects (that's the major distinction from Procyon AVRlib) I'm open to having the LGPL license on such a library project. (Definitely not the GPL, though.) I can be persuaded to either the BSD or

Re: [avr-libc-dev] avr-lib-c-extentions library

2008-01-02 Thread Joerg Wunsch
As Rich Teer wrote: ... In other words, under BSD, someone could take the AVRlibC code and change it, but not be obliged to return those changes back to the community. And this is exactly intentional for our purpose. In the embedded world, people can quickly become nervous if they even feel