<div>Hi again,</div>
<div> </div>
<div>First of all thanks for reply.<br> </div>
<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I attached a diff to the 3.7 version of the Motorola patch. I hope this<br>will help you. This is not the Xenomai version, but the standard version
<br>with VME interrupts per level. The mechanism for Xenomai is identical,<br>but I don't know yet about the legal status of this. The attached patch<br>has also been provided to Motorola.</blockquote>
<div> </div>
<div>I've got the 3.5 version of the driver, and tried to find newer one. Where do you get this new releases and patches?</div>
<div>Nevertheless thanks for the patch.</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I also had some ssh problems, but AFAICR I had to enable UNIX98PTYS and<br>BSDPTYS, and create the entries in /dev/ for the BSD ptys (/dev/ttypXX
<br>and /dev/ptyXX).</blockquote>
<div> </div>
<div>I also had these two options enabled, but still the kernel hangs at boot time just after trying to initialize SCSI devices... Without Xenomai this problem doesn't occur. I'm wondering what is that makes Xenomai mess up things so badly?
</div>
<div> </div>
<div>Best regards,</div>
<div>Konstantin Boyanov</div></div>