On Fri, May 12, 2017 at 3:12 PM, Oleksandr Grytsov wrote:
> On Thu, May 4, 2017 at 11:49 AM, Oleksandr Grytsov wrote:
>> Hi All,
>>
>> Here is configuration proposal with connector (surface) id:
>>
>> 1. Configuration file:
>> vdispl = [ 'backend=0, devId=0, beAlloc=1,
>> connectors=id0:800x600;i
On Thu, May 4, 2017 at 11:49 AM, Oleksandr Grytsov wrote:
> Hi All,
>
> Here is configuration proposal with connector (surface) id:
>
> 1. Configuration file:
> vdispl = [ 'backend=0, devId=0, beAlloc=1,
> connectors=id0:800x600;id1:1024x768' ]
>
> * backend - backend domain id or name (if dif
Hi All,
Here is configuration proposal with connector (surface) id:
1. Configuration file:
vdispl = [ 'backend=0, devId=0, beAlloc=1,
connectors=id0:800x600;id1:1024x768' ]
* backend - backend domain id or name (if different from dom 0);
* devId - device id (if different from 0);
* b
Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV display
device driver interface"):
> I considered that frontend domain name and surface index is a unique surface
> identifier. Like following:
>
> Surface with index 0 from DomU should be placed a
On Tue, May 2, 2017 at 5:28 PM, Ian Jackson wrote:
> Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV
> display device driver interface"):
>> On Thu, Apr 13, 2017 at 3:54 PM, Ian Jackson
>> wrote:
>> > Can you sketch out w
Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV display
device driver interface"):
> On Thu, Apr 13, 2017 at 3:54 PM, Ian Jackson
> wrote:
> > Can you sketch out what the rest of the system does, then ?
> > Presumably there has to be a differ
On Fri, Apr 14, 2017 at 1:12 PM, Oleksandr Grytsov wrote:
> On Thu, Apr 13, 2017 at 3:54 PM, Ian Jackson
> wrote:
>> Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV
>> display device driver interface"):
>>> After internal discussio
On Thu, Apr 13, 2017 at 3:54 PM, Ian Jackson wrote:
> Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV
> display device driver interface"):
>> After internal discussion we think that putting positions and
>> z-orders of virtual connector
Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV display
device driver interface"):
> After internal discussion we think that putting positions and
> z-orders of virtual connectors to the Xen store and libxl
> configuration is not so good idea. Becaus
On Wed, Apr 12, 2017 at 7:48 PM, Wei Liu wrote:
> On Mon, Apr 10, 2017 at 01:58:47PM +0300, Oleksandr Grytsov wrote:
>> Hi Ian,
>>
>> After internal discussion we think that putting positions and z-orders
>> of virtual connectors
>> to the Xen store and libxl configuration is not so good idea. Bec
On Mon, Apr 10, 2017 at 01:58:47PM +0300, Oleksandr Grytsov wrote:
> Hi Ian,
>
> After internal discussion we think that putting positions and z-orders
> of virtual connectors
> to the Xen store and libxl configuration is not so good idea. Because
> their composition
> depends on an application an
Hi Ian,
After internal discussion we think that putting positions and z-orders
of virtual connectors
to the Xen store and libxl configuration is not so good idea. Because
their composition
depends on an application and usage. We consider automotive usage.
For example one of domain drives navigatio
On Thu, Apr 6, 2017 at 4:03 PM, Ian Jackson wrote:
> Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV
> display device driver interface"):
>> On Thu, Apr 6, 2017 at 2:17 PM, Ian Jackson
>> wrote:
>> > Oleksandr Grytsov writes ("
Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV display
device driver interface"):
> On Thu, Apr 6, 2017 at 2:17 PM, Ian Jackson wrote:
> > Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV
> > display device driver i
On Thu, Apr 6, 2017 at 2:17 PM, Ian Jackson wrote:
> Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV
> display device driver interface"):
>> Backend and frontend operate with connectors (virtual displays). They
>> are identified by connector i
Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV display
device driver interface"):
> Backend and frontend operate with connectors (virtual displays). They
> are identified by connector index.
> The virtual display layouts, orders, on which physical
On Wed, Apr 5, 2017 at 6:50 PM, Ian Jackson wrote:
> Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV
> display device driver interface"):
>> On Wed, Apr 5, 2017 at 5:28 PM, Ian Jackson
>> wrote:
>> > Who starts the display backend
Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV display
device driver interface"):
> On Wed, Apr 5, 2017 at 5:28 PM, Ian Jackson wrote:
> > Who starts the display backend ? I'm obviously missing some of the
> > plumbing. Sorry again for a
On Wed, Apr 5, 2017 at 5:28 PM, Ian Jackson wrote:
> Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV
> display device driver interface"):
>> The display backend is a user-space application which is DRM or
>> Wayland client. Generally it can b
Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV display
device driver interface"):
> The display backend is a user-space application which is DRM or
> Wayland client. Generally it can be run on any domain.
Who starts the display backend ? I'm obvi
On Wed, Apr 5, 2017 at 5:18 PM, Oleksandr Grytsov wrote:
> On Wed, Apr 5, 2017 at 5:00 PM, Konrad Rzeszutek Wilk
> wrote:
>> On Wed, Apr 05, 2017 at 02:49:26PM +0100, Ian Jackson wrote:
>>> al1img . writes ("Re: [PATCH v1 0/2] libxl: add PV display device driver
>>> interface"):
>>> > On Wed, Ap
On Wed, Apr 5, 2017 at 5:00 PM, Konrad Rzeszutek Wilk
wrote:
> On Wed, Apr 05, 2017 at 02:49:26PM +0100, Ian Jackson wrote:
>> al1img . writes ("Re: [PATCH v1 0/2] libxl: add PV display device driver
>> interface"):
>> > On Wed, Apr 5, 2017 at 2:05 PM, Ian Jackson
>> > wrote:
>> > > Sorry to sh
On Wed, Apr 05, 2017 at 02:49:26PM +0100, Ian Jackson wrote:
> al1img . writes ("Re: [PATCH v1 0/2] libxl: add PV display device driver
> interface"):
> > On Wed, Apr 5, 2017 at 2:05 PM, Ian Jackson
> > wrote:
> > > Sorry to show my ignorance, but what is a "PV display device" ?
> > > Where is t
al1img . writes ("Re: [PATCH v1 0/2] libxl: add PV display device driver
interface"):
> On Wed, Apr 5, 2017 at 2:05 PM, Ian Jackson wrote:
> > Sorry to show my ignorance, but what is a "PV display device" ?
> > Where is the backend ? What protocol do the frontend/backend speak ?
>
> This is PV
On Wed, Apr 5, 2017 at 2:05 PM, Ian Jackson wrote:
> Oleksandr Grytsov writes ("[PATCH v1 0/2] libxl: add PV display device driver
> interface"):
>> From: Oleksandr Grytsov
>>
>> These patches add PV display device to libxl and xl.
>>
>> Changes since initial:
>> * re-work libxl displ related f
Oleksandr Grytsov writes ("[PATCH v1 0/2] libxl: add PV display device driver
interface"):
> From: Oleksandr Grytsov
>
> These patches add PV display device to libxl and xl.
>
> Changes since initial:
> * re-work libxl displ related functions to use libxl_device_type
>
> Oleksandr Grytsov (2)
From: Oleksandr Grytsov
These patches add PV display device to libxl and xl.
Changes since initial:
* re-work libxl displ related functions to use libxl_device_type
Oleksandr Grytsov (2):
libxl: add PV display device driver interface
xl: add PV display device commands
tools/libxl/Makefil
27 matches
Mail list logo
