<div>
<div> </div>
<div>Hi again,</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I also work with devices on the VME bus. The approach we took is to map<br>all the devices into userspace, and use Xenomai for RT performance. This
<br>avoids the need to write drivers for all the devices. The RT-performance<br>of Xenomai is quite good: the jitter on a timer-interrupt is always less<br>than 20usec, even under high load, where standard Linux only achieves
<br>this in a no load situatieo, under high load standard Linux has a jitter<br>of over 10 msec.</blockquote>
<div> </div>
<div>Good advice, I will investigate in this direction.</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">The setup we choose was to have a RT-interrupt handler and a RT IOCTL<br>call "WAIT_FOR_INTERRUPT". This is a slightly modified version from the
<br>Motorola driver (I guess that you also use the Tundra chipset to access<br>the VME-bus). </blockquote>
<div> </div>
<div>Yes, I do. It is the Tsi148 in fact. I'll be interested to see some sample code of yours, if it doesn't violate some restrictions ofcourse.</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Here you can wait for a specific VME interrupt-level, and<br>it returns the vector number. So you can have several applications
<br>connect to the same VME driver, but all on different levels.</blockquote>
<div> </div>
<div>So, if I understand you correctly, you altered the Motorola driver in order for it to be able to communicate with user spae programms through Xenomai. Which version of Xenomai ws that? I tried to test Xemonai 2.0 on my setup but it iterfred somehow with SSH configuration and thats why i dropped it.
</div>
<div> </div>
<div>Many thanks,</div>
<div>Konstantin</div></div><br>