1. HW API internal meeting 2/10/2001 Eric CANO, CERN/EP-CMD1 What’s proposed? l Integration with Christoph’s generic hardware access library for user-friendly functions. l Addition on generic read-write functions (instead of only message passing in xdaq-shell) l Creation of a Generic access utility for i2ocore/xdaq- shell (could also serve as an example for i2ocore users) l Creation of PCI memory space mapping functionnality

2. HW API internal meeting 2/10/2001 Eric CANO, CERN/EP-CMD2 I 2 O core architecture (Linux) (updated) PCI bus Reserved memory for DMA (physmem) Kernel space Xdaq-shell messaging Interrupts Slave accesses PCI device DMA engine DMA Address translation Xdaq-shell Dbuffs Slave accesses Interrupts Mapping (no copy)Message passing (copies) Xdaq-shell messages Xdaq-shell Dbuffs User space (applications, paged memory) I 2 O core API New proposal In red & italic Xdaq-shell PCIMaps Mapping (no copy) Generic R/W module I 2 O core user’s module

3. HW API internal meeting 2/10/2001 Eric CANO, CERN/EP-CMD3 Proposal layout for the hardware integration and for VME l VME interfaces usually come with a driver, in user space already, let’s use it when it’s there. l The final user (system integrator) wants a nice interface to the hardware (possibly C++) l The C++ interface is application oriented and hides the hardware implementation as much as possible.

4. HW API internal meeting 2/10/2001 Eric CANO, CERN/EP-CMD4 Layout of hardware to C++, PCI and VME Final application OO library VboardOO library Pboard1OO library Pboard2 Real hardware Kernel space User space Xdaq-Shell Christoph’s interface VME interface Driver and API (e.g. NI-VISA) USER PROVIDED Unless Sergio decided Christoph’s interface I2o core for PCI User’s moduleGeneric module