[Efi332] Standard GNU C library for CYGWIN

[Doug Brunner]

Here's my current codebase. The ISR is located in interrupt.s, which 
contains the exception service routine for all my interrupts, and the 
actual communications functions are in comm.c.

       --Doug Brunner

David Eicher wrote:

>Oh yeah, I'm interested. It sounds like exactly what I need for the efi
>code.
>
>Thanks,
>
>Dave
>
>
>-----Original Message-----
>From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
>Behalf Of Doug Brunner
>Sent: Saturday, July 23, 2005 2:26 AM
>To: efi332 at diy-efi.org
>Subject: Re: [Efi332] Standard GNU C library for CYGWIN
>
>I don't know if it'll help you or not, but I've written an ISR in 
>assembly (currently untested) that uses the QSCI, and a pair of circular 
>buffers to feed it--this allows the ISR to keep feeding the transmit 
>queue and pulling data off the receive queue without intervention by the 
>main program.
>
>Let me know if you're interested,
>
>--Doug Brunner
>
>David Eicher wrote:
>
>  
>
>>Hi Kevin,
>>
>>Yep, I'm not aware that a library exists for SCI either. So.., it 
>>looks like I'm going to build one. One thing I struggle with is, use 
>>SCI or QSCI? My ultimate goal is to be using QSCI with interrupts. But 
>>that might be a bit much to hope for initially. Maybe I'll try to walk 
>>before I run, and just use basic character puts and gets. Then, when 
>>I'm more familiar with the process of building a library (never done 
>>it), I'll go for the more powerful approach.
>>
>>That is nice to know that the stdlib with GCC is so big, gotta stay 
>>away from that!
>>
>>Thanks,
>>
>>Dave
>>
>>------------------------------------------------------------------------
>>
>>*From:* efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] 
>>*On Behalf Of *Kevin Yachimec
>>*Sent:* Friday, July 22, 2005 9:33 AM
>>*To:* efi332 at diy-efi.org
>>*Subject:* RE: [Efi332] Standard GNU C library for CYGWIN
>>
>>Dave,
>>
>>I haven't built GCC for the 555 but I have re-built GCC for the 332 
>>many times and I have found that newlib is much better than stdlib 
>>that comes with GCC. For example if you build the 332 source code on 
>>Sourceforge with the newlib it's almost half the size of stdlib. As 
>>far as printf() I have seen a number of versions for embedded work but 
>>you would be required to build from source in order to use it. I don't 
>>know of anything that's ready to work with SCI out of the box.
>>
>>Kevin
>>
>>
>>    
>>
>------------------------------------------------------------------------
>  
>
>>    *From:* efi332-bounces at diy-efi.org
>>    [mailto:efi332-bounces at diy-efi.org] *On Behalf Of *David Eicher
>>    *Sent:* Friday, July 22, 2005 6:22 AM
>>    *To:* efi332 at diy-efi.org
>>    *Subject:* [Efi332] Standard GNU C library for CYGWIN
>>
>>        Hello list,
>>
>>        Has anyone built a standard C library for the GNU C running on
>>        cygwin? I'm looking for the prinf( ) function (and others),
>>        that have been re-directed to the SCI serial interface for
>>        MPC555/565.
>>
>>        Thanks,
>>
>>        Dave
>>
>>
>>
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>Efi332 mailing list
>>Efi332 at diy-efi.org
>>http://lists.diy-efi.org/mailman/listinfo/efi332
>> 
>>
>>    
>>
>
>_______________________________________________
>Efi332 mailing list
>Efi332 at diy-efi.org
>http://lists.diy-efi.org/mailman/listinfo/efi332
>
>_______________________________________________
>Efi332 mailing list
>Efi332 at diy-efi.org
>http://lists.diy-efi.org/mailman/listinfo/efi332
>
>  
>