 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> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] domU unable to release memory to dom0, Luke S Crawford |
|---|---|
| Next by Date: | [Xen-devel] "xm vcpu-pin" error, Huang2, Wei |
| Previous by Thread: | [Xen-users] Re: [Xen-devel] Xen - Guest memory allocation, dinesh chandrasekaran |
| Next by Thread: | Re: [Xen-devel] information needed for netbsd porting project, Lin.Yu@xxxxxxxxxxxxx |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
