[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RTEMS-mvme5500 BSP update
- Date: Thu, 19 Mar 2009 15:54:35 -0500
- From: joel.sherrill at OARcorp.com (Joel Sherrill)
- Subject: RTEMS-mvme5500 BSP update
Kate Feng wrote:
> Joel Sherrill wrote:
>> Any chance of getting a patch to apply to the
>> RTEMS source base?
> The attached mvme5500-patch.tar.gz contains two files :
> I tried to file a PR, but it seems that there are some problems
> with the bug tracking system : bugzilla. I could not even view
> It was OK last week, though.
We got a new bugzilla version in an update and apparently
it needed touching by hand.
It is back up now. Weird update.
>> --joel sherrill
>> Kate Feng wrote:
>>> The stable version of RTEMS-mvme5500 BSP is posted at
>>> The "RTEMS-mvme5500 BSP v18.104.22.168", was tested
>>> under RTEMS 4.9.1, and the "RTEMS-mvme5500 BSP v22.214.171.124"
>>> was tested under RTEMS 4.8.0..
>>> The highlights of the change are :
>>> 1) Use the GT_GPP_Value register (0xf104) instead of the
>>> GT_GPP_Interrupt_Cause register (0xf108) to monitor the cause
>>> of the level sensitive interrupts. See irq/BSP_irq.c.
>>> This is an unique solution which solves part of the bugs in
>>> the BSP, which especially affects the 1GHz network driver.
>>> 2) There is no change in the 100 MHz network driver. Thus,
>>> its performance stays the same. Some bugs were fixed in the
>>> 1GHz network drivers (e.g. if_wm.c).
>>> 3)Enable "PCI Read Agressive Prefetch", "PCI Read Line Agressive
>>> and "PCI Read Multiple Agressive Prefetch" to improve the performance of
>>> the PCI based applications (e.g. 1GHz network driver). See
>>> However, performance is driven by applications.
>>> There is no known bug at this point. Any feedback which is related to
>>> the RTEMS-mvme5500 BSP would be highly appreciated.
>>> Hope this helps,
>>> rtems-users mailing list
>>> rtems-users at rtems.com