avr-libc-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Weddington, Eric
Subject: RE: [avr-libc-dev] avr-lib-c-extentions library
Date: Wed, 2 Jan 2008 14:36:34 -0700

 

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Joerg Wunsch
> Sent: Wednesday, January 02, 2008 2:13 PM
> To: address@hidden
> Subject: Re: [avr-libc-dev] avr-lib-c-extentions library
> 
> 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.  Stuff from myself I'd consider candidate for
> inclusion in such a library contains:
> 
> . The LCD code from the stdiodemo example.  It's been living in my
>   private tree for a couple of years, and when I published it as part
>   of stdiodemo, I cleaned it up a good bit, and generalized it through
>   macros so it ought to be fairly easy adaptable for other hardware as
>   it is now.  It has been subsequently improved based on user
>   feedback.
> 
> . The one-shot timer code from:
> 
>   http://www.sax.de/~joerg/avr-timer/
> 

This is definitely good stuff to have in such a library. And it doesn't
conflict with future internal projects that I'll be doing.


> . 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 LGPL license.

Eric




reply via email to

[Prev in Thread] Current Thread [Next in Thread]