MCF5329EVB BSP

Joel Sherrill joel.sherrill at oarcorp.com
Fri Oct 5 16:07:47 CDT 2007


Kirspel, Kevin wrote:
> There are no licensing issues with the BSP.  The port does require a change
> to the gnu tool chain generation so that it generates a m68k-rtems for the
> coldfire version 3 core (m5307 cpu).
OK.  That's another kettle of fish entirely.  Eventually gcc will catch 
up. :D

--joel
>   
>  
> Kevin Kirspel
> Opti Medical Systems
> Electrical Engineer
> 235 Hembree Park Drive
> Roswell GA 30076
> (ph) 770-510-4444 x4568
> (fax) 770-510-4445
>
> -----Original Message-----
> From: Joel Sherrill [mailto:joel.sherrill at oarcorp.com] 
> Sent: Friday, October 05, 2007 2:36 PM
> To: Kirspel, Kevin
> Cc: 'rtems-users at rtems.org'
> Subject: Re: MCF5329EVB BSP
>
> Kirspel, Kevin wrote:
>   
>> I have almost completed a port to RTEMS of the MCF5329EVB evaluation 
>> board from Freescale. With this BSP I had to port the YAFFS2 file 
>> system to RTEMS. I would like to submit the BSP and YAFFS2 port to 
>> RTEMS. The YAFFS2 license is GPL. I don't know if that is OK with 
>> RTEMS. I would like to do some robustness testing on the YAFFS2 port. 
>> Does RTEMS have a test plan/procedure to validate new file systems?
>>
>>     
> Congratulations on the BSP and port. Is the license OK on the BSP? Other 
> email
> deals with the YAFFS2 license issue.
>
> There are POSIX tests which exercise files through the C library IO 
> calls and
> should exercise all the functionality available through "normal" APIs. You
> would just have to arrange to have that mounted and the paths point to it.
>
> --joel
>   
>> Kevin Kirspel
>>
>> Opti Medical Systems
>>
>> Electrical Engineer
>>
>> 235 Hembree Park Drive
>>
>> Roswell GA 30076
>>
>> (ph) 770-510-4444 x4568
>>
>> (fax) 770-510-4445
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> rtems-users mailing list
>> rtems-users at rtems.com
>> http://rtems.rtems.org/mailman/listinfo/rtems-users
>>   
>>     




More information about the rtems-users mailing list