[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [avr-libc-dev] Adding (some) Procyon AVRlib functionality to avr-lib
From: |
Weddington, Eric |
Subject: |
RE: [avr-libc-dev] Adding (some) Procyon AVRlib functionality to avr-libc |
Date: |
Fri, 18 Sep 2009 12:30:47 -0600 |
> -----Original Message-----
> From:
> address@hidden
> [mailto:address@hidden
> org] On Behalf Of Frédéric Nadeau
> Sent: Friday, September 18, 2009 10:00 AM
> To: address@hidden
> Subject: Re: [avr-libc-dev] Adding (some) Procyon AVRlib
> functionality to avr-libc
>
> I volunteer to start the project.
>
> I suggest we open a hosting on Savannha so that we can have a separate
> mailing list and start discussion on that specific project. From there
> on we could lay out a distribution plan, compilation method, etc.
>
> I would personally name it "avr-drv". Any better name or suggestion?
>
I had started a project earlier and had called it LibAVR (or libavr). The point
being that we have libc (the C library), libm (the math library), and this
would be libavr, the AVR library. On the linker command line, it would be easy
to spot with '-lavr'. Plus it has the distinction that the name is short.
See attached .zip file for existing code for the project.
Addressing Ron's earlier comment: I would rather not do a UART driver as the
first device, mainly because there is actually a lot of code with that. I would
vote for an SPI driver, mainly because it is simpler to implement. I, of
course, also have an example of that in the libavr code attached.
Eric
libavr.zip
Description: libavr.zip
- Re: [avr-libc-dev] Adding (some) Procyon AVRlib functionality to avr-libc, (continued)
Re: [avr-libc-dev] Adding (some) Procyon AVRlib functionality to avr-libc, Ruddick Lawrence, 2009/09/17
Re: [avr-libc-dev] Adding (some) Procyon AVRlib functionality to avr-libc, David Brown, 2009/09/18
RE: [avr-libc-dev] Adding (some) Procyon AVRlib functionality to avr-libc, Ron Kreymborg, 2009/09/18
Re: [avr-libc-dev] Adding (some) Procyon AVRlib functionality to avr-libc, Frédéric Nadeau, 2009/09/18
Re: [avr-libc-dev] Adding (some) Procyon AVRlib functionality to avr-libc, Ruddick Lawrence, 2009/09/18
RE: [avr-libc-dev] Adding (some) Procyon AVRlib functionality to avr-libc,
Weddington, Eric <=
Message not availableRe: [POSSIBLE VIRUS:###] RE: [avr-libc-dev] Adding (some) Procyon AVRlib functionality toavr-libc, Ruddick Lawrence, 2009/09/18
RE: [avr-libc-dev] Adding (some) Procyon AVRlib functionality toavr-libc, Weddington, Eric, 2009/09/18
Re: [avr-libc-dev] Adding (some) Procyon AVRlib functionality toavr-libc, Joerg Wunsch, 2009/09/18
RE: [avr-libc-dev] Adding (some) Procyon AVRlib functionalitytoavr-libc, Weddington, Eric, 2009/09/18
Re: [avr-libc-dev] Adding (some) Procyon AVRlib functionalitytoavr-libc, Joerg Wunsch, 2009/09/18
RE: [avr-libc-dev] Adding (some) Procyon AVRlibfunctionalitytoavr-libc, Weddington, Eric, 2009/09/18
Re: [avr-libc-dev] Adding (some) Procyon AVRlibfunctionalitytoavr-libc, Frédéric Nadeau, 2009/09/18
RE: [avr-libc-dev] Adding (some) Procyon AVRlibfunctionalitytoavr-libc, Weddington, Eric, 2009/09/18
Re: [avr-libc-dev] Adding (some) Procyon AVRlibfunctionalitytoavr-libc, Ruddick Lawrence, 2009/09/18
Re: [avr-libc-dev] Adding (some) Procyon AVRlibfunctionalitytoavr-libc, Jan Waclawek, 2009/09/18