[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] [RFC] portpins
From: |
E . Weddington |
Subject: |
Re: [avr-libc-dev] [RFC] portpins |
Date: |
Fri, 17 Oct 2003 21:21:21 GMT |
>
>
> On Fri, 17 Oct 2003, E.Weddington wrote:
>
> > >
> >
> > > How's the attached patch look? I don't intend for
this to go into
> > > 1.0.1, but more likely 1.0.2 unless there's a
compelling reason
> > > not to wait.
> >
> >
> > Looks fine to me. Though, are you planning to use the
> > generic data direction register bit defintions in a
similar
> > fashion?
>
> I'm not sure what you mean here. Can you give me an
example?
No. My bad, ignore that comment.
Looks fine!
> >
> >
> > > I'm not against the Pxn defs in io*.h...
> > >
> > > I've been working a gui program that will read in the
device
> > > readers and display all the register names and bit
names in a
> > > table very similar to the register summary in the
datasheet. I'm
> > > hoping that this will make creating/verifying of the
device
> > > headers _much_ simpler. The headers will need a bit
of massaging
> > > though before they are parseable by my program. It's
getting close
> > > to useable, but not yet ready for mass consumption
yet...
> > >
> >
> > Cool. What language?
>
> Python with gtk2+glade for the GUI. My research shows
that this should
> be usable on Windows (in theory, but I don't know how
much work that
> will take in practice ;).
>
> Ted Roth
>
Hmm. Don't know much about the gtk2+glade part. I'll have
to look into it.
Eric
- Re: [avr-libc-dev] [RFC] portpins,
E . Weddington <=