vme_slave_window_create - Allocates a VMEbus Slave Window handle.
Handle allocated by vme_init.
Pointer to the window handle to allocate.
VMEbus address.
VMEbus address space. Valid values are:
- VME_A16Minimum size of the window, in bytes.
Flags indicating special window features. If a value is specified, it must be a bitwise "OR" of the following values for the Tundra Universe II device:
- VME_CTL_PWEN - Posted writes enabled.One of the following address modes can be used. If a mode is not specified, the window responds to accesses in either mode.
- VME_CTL_PROGRAM_ONLY - Respond to program address modifiers only.One of the following address privileges can be used. If a privledge is not specified, the window responds to accesses of either privledge.
- VME_CTL_SUPER_ONLY - Respond to supervisor address modifiers only.One of the following PCI address spaces can be used. If a flag is not specified, the window maps to PCI memory space.
- VME_CTL_PCI_CONFIG - Access PCI bus using configuration cycles.Specifies the local physical address to which the VMEbus window should translate. If NULL, the driver attempts to allocate physical RAM.
Allocates a VMEbus Slave Window handle. If a suitable window is already configured within the bridge device, then that window will be used, otherwise, a VMEbus window is created to access the specified address and address space.
0 on success or -1 on failure
Setting VME_CTL_64_BIT results in a performance degradation when accessing 32-bit targets.
Setting VME_CTL_64_BIT results in performance degradation when accessing 64-bit targets if less than 64 bits of data are being transferred.
Enabling VME_CTL_RMW for a Slave Window may reduce performance for all transactions through that Slave Window.