source: rtems/c/src/lib/libbsp/powerpc/mvme5500/README.VME @ 9b4422a2

Last change on this file since 9b4422a2 was 54cb48f, checked in by Jennifer Averett <Jennifer.Averett@…>, on May 12, 2005 at 6:25:29 PM

2005-05-12 Jennifer Averett <jennifer.averett@…>

  • README.VME, include/bsp.h, irq/irq.h, network/GT64260eth.c, pci/detect_host_bridge.c, pci/gtpcireg.h, pci/pci.c, pci/pci.h, pci/pci_interface.c, pci/pcifinddevice.c: Submitted by Kate Feng <feng1@…> as RTEMS-MVME5500 BSP v1.1 release. Modifications made to merge this release with the current tree.
  • Property mode set to 100644
File size: 896 bytes
1README.VME: written by S. Kate Feng <> , 7/22/04
4Some VME modules(e.g. Oms58 motor controller) might require a PCI sync
5command following the out_xx() function (e.g. out_be16()) if mvme5500 is
6used as the SBC.  The mechanism is a hardware hook to help software
7synchronize between the CPU and PCI activities. The PCI sync is
8implemented in pci/pci_interface.c. For more example of the usage,one
9can reference the file that is posted in synAppRTEMS of
13In spite of the PCI sync overhead for the Oms58 motor controller, I do
14not see the runtime performance of RTEMS-mvme5500 being compromised as
15compared with that of RTEMS-mvme2307.  For example, it takes the same
16time to run motor_init() of synAppRTEMS for 48 motor initializations
17running either RTEMS-mvme2307 or RTEMS-mvme5500.
Note: See TracBrowser for help on using the repository browser.