[avr-libc-dev] [bug #28574] Xmega D ADC struct missing registers

2010-04-15 Thread Anitha Boyapati
Update of bug #28574 (project avr-libc): Status: In Progress => Fixed Percent Complete: 0% => 100% ___ Reply to this item at:

[avr-libc-dev] RE: [bug #28574] Xmega D ADC struct missing registers

2010-04-15 Thread Weddington, Eric
> -Original Message- > From: Anitha Boyapati [mailto:invalid.nore...@gnu.org] > Sent: Thursday, April 15, 2010 10:08 AM > To: Boyapati, Anitha; Olivier Gay; Aksel Jensen; Galen Seitz; > Joerg Wunsch; Weddington, Eric; avr-libc-dev@nongnu.org > Subject: [bug #28574] Xmega D ADC struct m

[avr-libc-dev] [bug #28574] Xmega D ADC struct missing registers

2010-04-15 Thread Anitha Boyapati
Follow-up Comment #11, bug #28574 (project avr-libc): Proper patch with Changelog and News entries generated for revision 2121. Build verified. (file #20229) ___ Additional Item Attachment: File name: bug28574.patch Size:9

[avr-libc-dev] RE: [bug #28574] Xmega D ADC struct missing registers

2010-04-15 Thread Weddington, Eric
> -Original Message- > From: Joerg Wunsch [mailto:invalid.nore...@gnu.org] > Sent: Thursday, April 15, 2010 7:59 AM > To: Boyapati, Anitha; Olivier Gay; Aksel Jensen; Galen Seitz; > Joerg Wunsch; Weddington, Eric; avr-libc-dev@nongnu.org > Subject: [bug #28574] Xmega D ADC struct missi

[avr-libc-dev] [bug #28574] Xmega D ADC struct missing registers

2010-04-15 Thread Joerg Wunsch
Follow-up Comment #10, bug #28574 (project avr-libc): As these reserved locations are part of a C struct, you cannot have "holes" in them, so the C struct definition must necessarily differ from the XML description (which can simply omit the unused IO registers). Filling these holes with "reserv

[avr-libc-dev] [bug #28574] Xmega D ADC struct missing registers

2010-04-15 Thread Anitha Boyapati
Follow-up Comment #9, bug #28574 (project avr-libc): I have reviewed Oliver's patch. The modifications in the patch match are compared with corresponding xml files. 1. Changes for ADC_T match xml device files. They appear fine. 2. Changes for EVSYS donot match xml device files. For e.g., the pat