From: "Jan Beulich" <JBeulich@suse.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>
Cc: Lars Kurth <lars.kurth@citrix.com>,
Iurii Konovalenko <iurii.konovalenko@globallogic.com>,
xen-devel@lists.xensource.com,
Volodymyr Babchuk <vlad.babchuk@gmail.com>,
Tim Deegan <tim@xen.org>,
Dario Faggioli <dario.faggioli@citrix.com>,
ian.jackson@eu.citrix.com, al1img@gmail.com,
Andrii Anisov <andrii.anisov@gmail.com>,
Oleksandr Tyshchenko <olekstysh@gmail.com>,
embedded-pv-devel <embedded-pv-devel@lists.xenproject.org>,
Julien Grall <julien.grall@arm.com>,
David Vrabel <david.vrabel@citrix.com>,
Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>,
Mygaiev Artem <joculator@gmail.com>
Subject: Re: [Embedded-pv-devel] [PATCH] drmif: add ABI for para-virtual DRM/KMS
Date: Thu, 24 Nov 2016 09:06:26 -0700 [thread overview]
Message-ID: <58371E120200007800121E08@prv-mh.provo.novell.com> (raw)
In-Reply-To: <CANY+8dcWSK=afgJfLN2RMFT+iQH=qBZh2F2Wuqz82r5eV5XVdA@mail.gmail.com>
>>> On 24.11.16 at 16:44, <andr2000@gmail.com> wrote:
>> One thing which I think you should have clarified up front is why
>> the existing fbfront is neither sufficient nor possible to extend
>> suitably.
> Framebuffer device is rather outdated way for Linux user-space
> to draw. All modern software expects DRM/KMS drivers and as
> a fallback *may* use fbdev. For that reason, there is a demand
> on DRM support for guests. So, it doesn't replace fbdev, but rather extend
>> Which gets me to a second aspect: The chosen name is
>> rather Linux centric - DRM has quite different a meaning in the
>> Windows world afaik.
>>
> Well, that was my intent: define ABI for *Linux DRM/KMS* protocol
> That said, it is still possible to implement back or front on Windows
> with this protocol if need be
Hmm, I think you want a PV Linux DRM/KMS driver, but that doesn't
mean you want/need a protocol by that name. The interface has
to describe virtual hardware, and I don't think you'd call a graphics
card "DRM/KMS card"? Hence also the question whether the existing
fbfront protocol couldn't be extended - after all modern graphics
(3D) cards have also evolved from simple frame buffer (2D) ones.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-24 16:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 11:30 [PATCH] drmif: add ABI for para-virtual DRM/KMS Oleksandr Andrushchenko
2016-11-24 11:30 ` Oleksandr Andrushchenko
2016-11-24 12:25 ` Jan Beulich
2016-11-24 12:32 ` [Embedded-pv-devel] " Julien Grall
2016-11-24 14:42 ` Oleksandr Andrushchenko
2016-11-24 15:08 ` Jan Beulich
2016-11-24 15:44 ` Oleksandr Andrushchenko
2016-11-24 16:06 ` Jan Beulich [this message]
2016-11-24 18:31 ` Oleksandr Andrushchenko
2016-11-24 22:14 ` Dario Faggioli
2016-11-25 7:20 ` Jan Beulich
2016-11-25 7:35 ` Oleksandr Andrushchenko
2016-11-24 15:05 ` Lars Kurth
2016-11-24 15:38 ` Oleksandr Andrushchenko
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=58371E120200007800121E08@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=al1img@gmail.com \
--cc=andr2000@gmail.com \
--cc=andrii.anisov@gmail.com \
--cc=dario.faggioli@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=embedded-pv-devel@lists.xenproject.org \
--cc=ian.jackson@eu.citrix.com \
--cc=iurii.konovalenko@globallogic.com \
--cc=joculator@gmail.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth@citrix.com \
--cc=oleksandr.dmytryshyn@globallogic.com \
--cc=olekstysh@gmail.com \
--cc=tim@xen.org \
--cc=vlad.babchuk@gmail.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.