Lpc2000

At 12:52 PM 10/13/05 +1000, Bruce Paterson wrote:
> > Hey Bruce,
> >
> > Care to enlighten me about that last comment.
> >
> > > lpc newlib extensions
> >
> > I've been meaning to go through the newlib re-entrancy
> > configuration etc to see what needs to be turned on for
> > uCOS-II thread-safe usage, and to create some sort of device
> > operations table interface (as per Bill Gatliff's docs from
> > Embedded Systems Programming).
> > I saw a post the other day from someone at Aeolus regarding
> > their newlib port layer (perhaps that was you)
> >
> > http://www.aeolusdevelopment.com/Articles/download.html
> >
> > anyways, if you have a nice clean way of implementing a
> > device layer, let us know and people can contribute with a
> > common interface.
>
>No it wasn't me. It was the Robert Ansett, the compiler of newlib_lpc.
>I'm not sure if he has rolled my SPI module into his latest newlib_lpc
>release as yet, but if necessary I can email it to you.
>Yes, it is good to conform to a common interface, and due to other
>newlib_lpc modules being available it significantly cut down my overall
>effort, even though I coded the SPI, and added some zero-copy options to
>the the uart modules.


It was probably my post you saw David.  And I haven't rolled Bruce's stuff 
in yet.  I've been distracted with clients work.  It is high on my todo 
list as well as a way to allow contributed code out in the wild more 
quickly especially drivers so they don't get stalled like this.  It'll 
probably be simple but I have to actually get it done.

I haven't explicitly addressed re-entrancy but I did try to structure 
things so it could be taken care of in the future.  As far as how 
successful that's been well the proof of the pudding will be in the eating.

Robert

" 'Freedom' has no meaning of itself.  There are always restrictions,   be 
they legal, genetic, or physical.  If you don't believe me, try to chew a 
radio signal. "  -- Kelvin Throop, III
http://www.aeolusdevelopment.com/