RE: [avr-libc-dev] avr-libc 1.6.8 [was: duplicating avr-libcfromwinavr]

[Weddington, Eric]

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Weddington, Eric
> Sent: Tuesday, March 02, 2010 7:10 PM
> To: Galen Seitz
> Cc: address@hidden
> Subject: RE: [avr-libc-dev] avr-libc 1.6.8 [was: duplicating 
> avr-libcfromwinavr]
> 
>  
> 
> > -----Original Message-----
> > From: 
> > address@hidden 
> > [mailto:address@hidden
> > org] On Behalf Of Galen Seitz
> > Sent: Tuesday, March 02, 2010 6:41 PM
> > Cc: address@hidden
> > Subject: Re: [avr-libc-dev] avr-libc 1.6.8 [was: duplicating 
> > avr-libc fromwinavr]
> > 
> > Only in avr-libc-WinAVR-20100110/doc/api: unjs.pl
> > Only in avr-libc-WinAVR-20100110/include/avr: iotn10.h
> > Only in avr-libc-WinAVR-20100110/include/avr: iotn4.h
> > Only in avr-libc-WinAVR-20100110/include/avr: iotn5.h
> > Only in avr-libc-WinAVR-20100110/include/avr: iotn9.h
> > 
> > Can you explain why these include files are not part of the 
> tarball? 
> > I guess the bootstrap process removes them, since they are 
> > not present 
> > in an actual WinAVR-20100110 install, but I'd like to 
> understand why.
> 
> Those are header files for new devices. However, support for 
> these new devices has not been officially added yet to 
> avr-libc. There are many more changes that need to be made 
> before avr-libc supports those devices. Also support for 
> these devices has not been added yet to binutils or gcc. But 
> they are currently in-process, so expect to see these devices 
> in the near future. The fact that they are not in the tarball 
> should not be a concern at this point.

I will also add that support for the ATtiny20 and ATtiny40 will be added at the 
same time as the rest of these devices. The header files for these 2 devices 
has not been added yet as there have been some issues with the source XML 
device files, so header files have not been generated yet.