On Fri, Jun 15, 2012 at 12:35:00PM +0200, Michel Dänzer wrote:
> On Fre, 2012-06-15 at 19:01 +1000, Christopher James Halse Rogers
> wrote:
> > xwayland drivers need access to their screen private data to authenticate.
> > Now that drivers no longer have direct access to the global screen arrays,
On Fri, Jun 15, 2012 at 07:01:34PM +1000, Christopher James Halse Rogers wrote:
> xwayland drivers need access to their screen private data to authenticate.
> Now that drivers no longer have direct access to the global screen arrays,
> this needs to be passed in as function context. The way it was
On Fri, 2012-06-15 at 21:54 +1000, Christopher James Halse Rogers wrote:
> On Fri, 2012-06-15 at 12:35 +0200, Michel Dänzer wrote:
> > On Fre, 2012-06-15 at 19:01 +1000, Christopher James Halse Rogers
> > wrote:
> > > xwayland drivers need access to their screen private data to authenticate.
> > >
On Fri, 2012-06-15 at 12:35 +0200, Michel Dänzer wrote:
> On Fre, 2012-06-15 at 19:01 +1000, Christopher James Halse Rogers
> wrote:
> > xwayland drivers need access to their screen private data to authenticate.
> > Now that drivers no longer have direct access to the global screen arrays,
> > thi
xwayland drivers need access to their screen private data to authenticate.
Now that drivers no longer have direct access to the global screen arrays,
this needs to be passed in as function context. The way it was working
was ugly, anyway.
Signed-off-by: Christopher James Halse Rogers
---
This c
