mvme6100 support for CVS head

[Joel Sherrill]

Kate Feng wrote:
> Daron Chabot wrote:
>   
>> On Fri, Jul 17, 2009 at 7:06 AM, Kate Feng<feng1 at bnl.gov> wrote:
>>   
>>     
>>> Joel Sherrill wrote:
>>>     
>>>       
>>>> Feng, Kate wrote:
>>>>       
>>>>         
>>>>> I wrote and upgraded the mvme5500 BSP to disco BSP to support the
>>>>> mvme6100 board.  At that time, the performance of the network on
>>>>> the mvme6100 board was not important, but the decision for the
>>>>> choice of H/W for my project was urgent.  Thus, the code for
>>>>> the network is not really ready for a formal release yet.  It seems that
>>>>> the
>>>>> network code for beatnik BSP needs to be  optimized or rewritten  as well
>>>>> based on the version I obtained from Till Straumann a while ago.  I do
>>>>> not know if he had any chance to improve the netowrk
>>>>> performance ever since then.
>>>>>         
>>>>>           
>>>> So .. it should work to ...
>>>>
>>>> a) build for mvme5500 and run on mvme6100?
>>>>       
>>>>         
>>> Not the mvme5500 BSP  in the current RTEMS release.
>>>     
>>>       
>> As in my original posting, I am not referring to the current (4.9.2)
>> release, but to the mvme5500 BSP as it stands
>> in the cvs HEAD version.
>>
>> This enum from mvme5500/include/bsp.h seems to imply run-time
>> detection of board type:
>> /* Board type */
>> typedef enum {
>> 	undefined = 0,
>> 	MVME5500,
>> 	MVME6100
>> } BSP_BoardTypes;
>>
>> So, as Joel asked, with the version on cvs HEAD, is it possible to
>> build for the 5500 and _run_ on the 6100 ?
>>   
>>     
> I will have to submit the network driver for the mvme6100.   I just wish
> one to be aware that the current driver is not written in the typical RTEMS
> real-time fashion, and its performance could be boosted -up to at least
> an estimated factor of two. Thus, one should not use that as a template
> for other network driver.
>
> Speaking of  the CVS head, back in April, I  had to modify some shared files
> to solve the issue with the RTEMS work space and C program heap
> before I submitted the updated code for mvme5500 BSP.  I did not send
> the patch for the shared files back then because I only had it tested 
> for the case
> when rtems_unified_work_area is false.  Joel, is the code updated ?
> The code should be updated before mvme5500,  mvme6100, and I think
> any other PPC can work.  Did I miss something ?
>
>   
I have no idea what the problem you are referring to is. :)

Give me a description or half-baked old patch and I will look
at it. 

--joel
> Kate
>
>   
>> BTW -- Kate, I am now working at BNL with the NSLS2 controls group :-)
>> so, I may be able to help with the mvme6100 bsp issues.
>>
>>
>> -- dc
>>
>>   
>>     
>>> I could rename "disco" BSP  back to "mvme5500" BSP
>>> for the RTEMS release, except the network driver was/is
>>> really not ready for the open release yet.
>>>     
>>>       
>>>> b) add alias to build for mvme6100 and fix x odd
>>>>    issues for mvme6100
>>>>
>>>> Does this mean the network driver works?  How
>>>> bad is "not optimized" really?
>>>>       
>>>>         
>>> Yes, the network driver for the mvme6100 works, at
>>> least for the one project I tested, but a workaround that
>>> have degraded the actual performance of the H/W by my
>>> estimation of at least two.
>>> It was not written for the real-time performance because
>>> there were somethings missing.  I had to quickly move on
>>> to a different H/W platform because the DDR memory
>>> date rate is too slow for my project, not because of the
>>> network driver.  I actually started to rewrite the driver to
>>> meet the requirement of the real-time programming.
>>> However, it kept getting interrupted by my other higher
>>> priority projects that I could not get this project
>>> completed.  It should be fun to get it finished, but
>>> it is more important to get my other projects done at
>>> this point.
>>>
>>> Regards,
>>> Kate
>>>     
>>>       
>>>> Just asking because I know you are a perfectionist and
>>>> wanted to get an accurate description of the status. :)
>>>>
>>>> --joel
>>>>       
>>>>         
>>>>>  At this point, I have at least two other higher priority tasks to be
>>>>> completed before I have a chance to  finish rewriting the network
>>>>> code for the mvme6100 board to boost up its performance, although it
>>>>> could be a fun project.
>>>>>  Cheers,
>>>>> Kate
>>>>>
>>>>> ________________________________
>>>>>
>>>>> From: rtems-users-bounces at rtems.org on behalf of Daron Chabot
>>>>> Sent: Thu 7/16/2009 9:25 PM
>>>>> To: RTEMS
>>>>> Subject: mvme6100 support
>>>>>
>>>>>
>>>>>
>>>>> Just looking at the cvs HEAD, it seems as though the mvme5500 bsp may
>>>>> also support the mvme6100 board. Is this correct ?
>>>>>
>>>>> Or should I instead be inquiring about the "beatnik" bsp for 6100 support
>>>>> ?
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
>>>>> -- dc
>>>>> _______________________________________________
>>>>> rtems-users mailing list
>>>>> rtems-users at rtems.org
>>>>> http://www.rtems.org/mailman/listinfo/rtems-users
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> rtems-users mailing list
>>>>> rtems-users at rtems.org
>>>>> http://www.rtems.org/mailman/listinfo/rtems-users
>>>>>
>>>>>         
>>>>>           
>>>     
>>>       
>
>   


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985