WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] information needed for netbsd porting project

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] information needed for netbsd porting project
From: "Michael Litchard" <michael@xxxxxxxxxxx>
Date: Tue, 8 Jul 2008 13:05:29 -0700
Delivery-date: Tue, 08 Jul 2008 13:05:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I would like to be able to do device driver development on a domU for
devices that the domO doesn't know about.
Using the sources for 3.1.2, could someone tell me where to look
to find the protocol between dom0 and domU used by Xen to do this?

After that, I will need to implement the PCI front-end and back-end drivers.
Could someone show me some sample code?


                                                           Thanks

Michael Litchard

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

<Prev in Thread] Current Thread [Next in Thread>