[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [avr-libc-dev] Re: [bug #25300] Additional i/o port names
From: |
Weddington, Eric |
Subject: |
RE: [avr-libc-dev] Re: [bug #25300] Additional i/o port names |
Date: |
Tue, 7 Apr 2009 09:30:51 -0600 |
> -----Original Message-----
> From:
> address@hidden
> [mailto:address@hidden
> org] On Behalf Of Frédéric Nadeau
> Sent: Tuesday, April 07, 2009 6:22 AM
> To: address@hidden
> Subject: Re: [avr-libc-dev] Re: [bug #25300] Additional i/o port names
>
> Hi,
>
> So I'm back from travel, I'll be looking into those thing shortly.
>
> As for notifying Atmel of mistake/errors/inconsistencies in XML files
> I thing it will be harder than what you make it sound like. Using the
> librairy, we load the XML in ram as an object tree. When I walk the
> tree, I can find errors but I cannot relate back to the XML line.
Hmm. For now, don't worry about trying to find errors. I'll see what I can do
with your (future) updated patch.
- RE: [avr-libc-dev] Re: [bug #25300] Additional i/o port names, Weddington, Eric, 2009/04/01
- Re: [avr-libc-dev] Re: [bug #25300] Additional i/o port names, Frédéric Nadeau, 2009/04/07
- RE: [avr-libc-dev] Re: [bug #25300] Additional i/o port names,
Weddington, Eric <=
- Re: [avr-libc-dev] Re: [bug #25300] Additional i/o port names, Frédéric Nadeau, 2009/04/10
- RE: [avr-libc-dev] Re: [bug #25300] Additional i/o port names, Weddington, Eric, 2009/04/12
- Re: [avr-libc-dev] Re: [bug #25300] Additional i/o port names, Bob Paddock, 2009/04/12
- RE: [avr-libc-dev] Re: [bug #25300] Additional i/o port names, Weddington, Eric, 2009/04/12
- Re: [avr-libc-dev] Re: [bug #25300] Additional i/o port names, Frédéric Nadeau, 2009/04/12
- RE: [avr-libc-dev] Re: [bug #25300] Additional i/o port names, Weddington, Eric, 2009/04/12
- Re: [avr-libc-dev] Re: [bug #25300] Additional i/o port names, Frédéric Nadeau, 2009/04/14
- RE: [avr-libc-dev] Re: [bug #25300] Additional i/o port names, Weddington, Eric, 2009/04/14