From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
linux-fbdev-devel@lists.sourceforge.net,
dmitry.torokhov@gmail.com, virtualization@lists.osdl.org,
linux-input@vger.kernel.org, adaplas@pol.net,
akpm@linux-foundation.org, jayakumar.lkml@gmail.com
Subject: Re: [PATCH 0/2] xen pvfb: Para-virtual framebuffer, keyboard and pointer
Date: Thu, 21 Feb 2008 14:33:05 -0800 [thread overview]
Message-ID: <47BDFC21.6010604@goop.org> (raw)
In-Reply-To: <871w76ca0i.fsf@pike.pond.sub.org>
Markus Armbruster wrote:
> Here's the description again:
>
> Frontends are expected to write their protocol ABI to xenstore. Since
> the protocol ABI defaults to the backend's native ABI, things work
> fine without that as long as the frontend's native ABI is identical to
> the backend's native ABI. This is not the case for xen-blkfront
> running 32-on-64, because its ABI differs between 32 and 64 bit, and
> thus needs this fix.
>
> I can break the dependency by putting the same bug that is now in
> xen-blkfront into xen-fbfront and xen-kbdfront.
>
Right, I see. The dependency is on the protocols.h changes.
J
prev parent reply other threads:[~2008-02-21 22:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 9:42 [PATCH 0/2] xen pvfb: Para-virtual framebuffer, keyboard and pointer Markus Armbruster
2008-02-21 9:43 ` [PATCH 1/2] fbdev: Make deferred I/O work as advertized Markus Armbruster
2008-02-21 16:30 ` Jaya Kumar
2008-02-21 17:31 ` Markus Armbruster
2008-02-21 9:43 ` [PATCH 2/2] xen pvfb: Para-virtual framebuffer, keyboard and pointer driver Markus Armbruster
2008-02-21 16:37 ` Jaya Kumar
2008-02-21 16:37 ` Jaya Kumar
2008-02-21 20:31 ` Jeremy Fitzhardinge
2008-02-22 6:31 ` Markus Armbruster
2008-02-22 22:31 ` Jeremy Fitzhardinge
2008-02-21 11:51 ` [PATCH 0/2] xen pvfb: Para-virtual framebuffer, keyboard and pointer Markus Armbruster
2008-02-21 11:51 ` Markus Armbruster
2008-02-21 19:45 ` Jeremy Fitzhardinge
2008-02-21 20:47 ` Markus Armbruster
2008-02-21 22:33 ` Jeremy Fitzhardinge [this message]
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=47BDFC21.6010604@goop.org \
--to=jeremy@goop.org \
--cc=adaplas@pol.net \
--cc=akpm@linux-foundation.org \
--cc=armbru@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jayakumar.lkml@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--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.