mvme6100 support

[Daron Chabot]

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 ?

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
>>>
>>
>
>