xen-devel
[Xen-devel] Re: [PATCH 2/2] xen pvfb: Para-virtual framebuffer, keyboard
To: |
Markus Armbruster <armbru@xxxxxxxxxx> |
Subject: |
[Xen-devel] Re: [PATCH 2/2] xen pvfb: Para-virtual framebuffer, keyboard and pointer driver |
From: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
Date: |
Fri, 22 Feb 2008 14:31:55 -0800 |
Cc: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, linux-fbdev-devel@xxxxxxxxxxxxxxxxxxxxx, dmitry.torokhov@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxx, linux-input@xxxxxxxxxxxxxxx, adaplas@xxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, jayakumar.lkml@xxxxxxxxx |
Delivery-date: |
Fri, 22 Feb 2008 14:35:36 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
In-reply-to: |
<8763whbiy8.fsf@xxxxxxxxxxxxxxxxx> |
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<871w76ejdg.fsf@xxxxxxxxxxxxxxxxx> <87skzmd4qc.fsf@xxxxxxxxxxxxxxxxx> <47BDDF97.7070001@xxxxxxxx> <8763whbiy8.fsf@xxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Thunderbird 2.0.0.9 (X11/20071115) |
Markus Armbruster wrote:
Jeremy Fitzhardinge <jeremy@xxxxxxxx> writes:
Markus Armbruster wrote:
This is a pair of Xen para-virtual frontend device drivers:
drivers/video/xen-fbfront.c provides a framebuffer, and
drivers/input/xen-kbdfront provides keyboard and mouse.
Unless they're actually inter-dependent, could you post this as two
separate patches? I don't know anything about these parts of the
kernel, so it would be nice to make it very obvious which changes are
fb vs mouse/keyboard.
I could do that do that, but the intermediate step (one driver, not
the other) is somewhat problematic: the backend in dom0 needs both
drivers, and will refuse to complete device initialization unless
they're both present.
That's OK. In that case keep them together.
J
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|