tile property contents

[Andy Ritger]

I assume the TILE property described below would be per-connector?

It looks like this would handle the DP MST tiled display case.

At the risk of trying to solve too much at once:

There are also configurations where users configure multiple heads to
drive power walls that they want to be treated as one logical monitor,
similar to the DP MST tiled display case.  Normally, those powerwall
configurations don't have any layout information from the monitors
themselves, and the layout is configured by the user.

Would it be appropriate for users to be able to set the TILE property
in that sort of scenario?

For the sake of generality, I wonder if max[hv]tiles and [hv]_tile_loc
should be expressed in pixels rather than tiles?  Sometimes, the tiles
in those powerwalls may not all have the same resolution, or may be
configured with overlap.  I suppose that would make the TILE configuration
specific to the current modetimings on each tile...

Thanks,
- Andy


On Tue, Oct 14, 2014 at 01:23:22PM +1000, Dave Airlie wrote:
> Hi,
> 
> So I've been hacking on mutter and the gnome pieces for tiling, and
> I've at least fixed mutter locally so maximise windows works and the
> heads are in the right order.
> 
> Now I've strung all the pieces together using a single KMS property
> that X.org propogates, and mutter picks up and propagates over dbus as
> well,
> 
> Currently I've ascii encoded the property into a blob,
> 
> <ver>:<tileid>:<flags>:<maxhtiles>:<maxvtiles>:<h_tile_loc>:<v_tile_loc>:<tile_w>:<tile_h>
> 
> I'm thinking of dropping the version field and just exposing TILE2
> property if we need it later to add more values,
> 
> The other fields:
> tileid: a group id assigned by the kernel to all tiles in the same
> group - unique per group
> flags: bit 0 : single monitor enclosure
> maxhtiles: total number of horiz tiles
> maxvtiles: total number of vert tiles
> h_tile_loc: horiz location of this output in tile group
> v_tile_loc: vert location of this output in tile group
> tile_w: width of this tile
> tile_h: height of this tile.
> 
> Now we extract all of these from the DisplayID v1.3 block, and I'm
> wondering if maybe I shouldn't just export the whole DisplayID tiling
> info block instead, it however encodes a few other pieces of
> information, including bezel info, and some flags specifying behaviour
> in some cases.
> 
> The former could be more suitable for cases where DisplayID isn't
> available (Dual DSI panels?) but I'm worried abuot exposing too little
> at this point making TILE useless when the next monitor comes out.
> 
> I'm not sure any part of the stack should be extracting things and
> splitting them out, I'd like to just give the same tile property all
> the way through.
> 
> Dave.
> _______________________________________________
> xorg-devel at lists.x.org: X.Org development
> Archives: http://lists.x.org/archives/xorg-devel
> Info: http://lists.x.org/mailman/listinfo/xorg-devel