As Stu Bell wrote:
Would importing the code (in any form) into avr-libc violate GPLv2
by putting the code (modified though it will be) under the somewhat
more restrictive LGPL?
avr-libc is covered by the BSD license. Yes, porting GPLed code to
the BSD license is impossible because the GPL
Stu Bell wrote:
Hi all,
I have started looking at porting the relatively simple byteorder
routines from Linux to avr-libc as requested in AVRFreaks. The question
I have is that all Linux code is covered by the GPLv2, while (I believe)
avr-libc is covered by the LGPL.
avr-libc uses a BSD
Hi all,
I have started looking at porting the relatively simple byteorder
routines from Linux to avr-libc as requested in AVRFreaks. The question
I have is that all Linux code is covered by the GPLv2, while (I believe)
avr-libc is covered by the LGPL.
Would importing the code (in any form) into
Hi All,
Because of an avr-libc bug (#21410), a GCC bug (#31644), and IIRC, the
fact that the EEPROM API does not work on at least 2 AVR devices, I have
taken a stab at rewriting the EEPROM API. The interface has been kept
the same, but instead of library functions, it has been rewritten as
macros
I have been having a problem the last couple of days, I'm hoping someone here
has some advice:
I am trying to write a simple interrupt handler for handling a TIMER2
comparison interrupt. I placed this at the top of my code:
ISR(TIMER2_COMP_vect)
{
PORTD ^= 0x40;
}
The Timer registers were
On 15 Jan 2008 at 20:05, Weddington, Eric wrote:
Hi All,
Because of an avr-libc bug (#21410), a GCC bug (#31644), and IIRC, the
fact that the EEPROM API does not work on at least 2 AVR devices, I have
taken a stab at rewriting the EEPROM API. The interface has been kept
the same, but
As Andrew S wrote:
Investigating this further, I found that the following corresponded
with the microcontroller running the correct interrupt handler for
the interrupt in question:
ISR(_VECTOR(8))
{ .. }
That would be TIMER1_COMPB_vect. Are you sure you are running the
correct timer? ;-)
