From: "Daniel P. Berrange" <berrange@redhat.com>
To: Kasai Takanori <kasai.takanori@jp.fujitsu.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Patch] Fix keymap support for PVFB.
Date: Tue, 3 Jul 2007 15:10:35 +0100 [thread overview]
Message-ID: <20070703141035.GA8410@redhat.com> (raw)
In-Reply-To: <21c701c7bd4c$c178c4b0$dab2220a@VF03007L>
On Tue, Jul 03, 2007 at 05:32:34PM +0900, Kasai Takanori wrote:
> Hi Daniel & Markus,
>
> >On Mon, Jul 02, 2007 at 07:51:36PM +0900, Kasai Takanori wrote:
> >>However, I think that it should do this with xenkbd who is originally the
> >>driver on the FrontEnd side.
> >>It will be problem if the HVM domain is working on PVFB in the future.
> >
> >I honestly can't see HVM using the PVFB at any time in the forseeable
> >future
> >unless PVFB is further developed to not suck. ie being able to change the
> >resolution / bpp would be a start for PVFB - something HVM can already do
> >trivially.
>
> Does it mean not to support making the HVM domain work on PVFB?
Sure you /could/ do it. I'm just saying there's no real point in trying
to though, since the HVM framebuffer has much more functionality than
the paravirt framebuffer. ie why would you want make HVM use a worse
framebuffer ?
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2007-07-03 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 10:51 [Patch] Fix keymap support for PVFB Kasai Takanori
2007-07-02 12:09 ` Daniel P. Berrange
2007-07-03 8:32 ` Kasai Takanori
2007-07-03 14:10 ` Daniel P. Berrange [this message]
2007-07-04 0:11 ` Kasai Takanori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070703141035.GA8410@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=kasai.takanori@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.