[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] I2C Driver issues with Xen


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Johan van de Groenendaal" <worldlycitizen@xxxxxxxxx>
  • Date: Fri, 10 Aug 2007 19:11:14 -0400
  • Delivery-date: Fri, 10 Aug 2007 16:11:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=al9Aqs/vEFA824MFfkjE+dnC+rWpGVmAA+vcTXSJJBBYHuecoxudlvBYZNQmi7znbdZcVa3LuAQl4M3fK0pw79oxI52H/9Tnjubewo2pWW4y/iYRkt1RI29Y6oVUtV+2gBtujmgqSl801L48/lDu3T6YB6oB+N1TNLWcQp0Uxtc=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

We have been developing an application that communicates with I2C/SMBUS devices where the comms includes multibyte read and write. When we run on a standard 2.6.18 kernel we have no issues, but as soon as we move the application to dom0 of a Xen kernel based on 2.6.18 , we are unable to do multibyte read and writes. It appears in the debugger either the ioctl interface or the driver no longer works correctly.

The h/w we are using is ICH7 and a Intel Core 2 Duo with VT.

Does anyone know how Xen impacts the I2C drivers if at all or the PCI interface to the chipset (I assume that it is not behaving correctly when we communicate to the chipset).

Regards
Johan


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.