On 24 January 2019 6:18:32 am NZDT, Emil Velikov
wrote:
>On Wed, 23 Jan 2019 at 04:39, Christopher James Halse Rogers
> wrote:
>>
>> We can't use drmSetMaster to query whether or not a drm fd is master
>> because it requires CAP_SYS_ADMIN, even if the fd
than MODE_ATTACHMODE, as it's more
clearly related to master status.
Signed-off-by: Christopher James Halse Rogers
---
xf86drm.c | 15 +++
xf86drm.h | 2 ++
2 files changed, 17 insertions(+)
diff --git a/xf86drm.c b/xf86drm.c
index 10df682b..adee5bd9 100644
--- a/
On 18 December 2018 7:07:01 pm NZDT, Christopher James Halse Rogers
wrote:
>On 18 December 2018 4:35:37 am AEDT, Emil Velikov
> wrote:
>>Hi Christopher,
>>
>>On Tue, 20 Nov 2018 at 03:37, Christopher James Halse Rogers
>> wrote:
>>>
>>> We can
On 18 December 2018 5:03:22 am AEDT, Emil Velikov
wrote:
>Hi Christopher,
>
>On Tue, 20 Nov 2018 at 04:30, Christopher James Halse Rogers
> wrote:
>>
>> I have wanted this code in Mir, so it's plausibly useful elsewhere,
>> particularly if the DRM dev
On 18 December 2018 4:35:37 am AEDT, Emil Velikov
wrote:
>Hi Christopher,
>
>On Tue, 20 Nov 2018 at 03:37, Christopher James Halse Rogers
> wrote:
>>
>> We can't use drmSetMaster to query whether or not a drm fd is master
>> because it requires CAP_SYS_ADM
I have wanted this code in Mir, so it's plausibly useful elsewhere,
particularly if the DRM device major number is going to become
dynamic.
Signed-off-by: Christopher James Halse Rogers
---
xf86drm.c | 2 +-
xf86drm.h | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --
fd is master.
Signed-off-by: Christopher James Halse Rogers
---
xf86drm.c | 20
xf86drm.h | 2 ++
2 files changed, 22 insertions(+)
diff --git a/xf86drm.c b/xf86drm.c
index 10df682b..bdb0439d 100644
--- a/xf86drm.c
+++ b/xf86drm.c
@@ -2741,6 +2741,26 @@ drm_publi
On 10 April 2017 6:51:21 pm AEST, "Michel Dänzer" wrote:
>On 06/04/17 04:47 PM, Christopher James Halse Rogers wrote:
>> On Wed, 5 Apr 2017 at 20:14 Lucas Stach > <mailto:l.st...@pengutronix.de>> wrote:
>>
>> Am Mittwoch, den 05.04.2017, 11:59 +
On Wed, 5 Apr 2017 at 20:14 Lucas Stach wrote:
> Am Mittwoch, den 05.04.2017, 11:59 +0200 schrieb Daniel Vetter:
> > On Wed, Apr 05, 2017 at 10:15:44AM +0200, Lucas Stach wrote:
> > > Am Mittwoch, den 05.04.2017, 00:20 + schrieb Christopher James
&g
On Wed, Apr 5, 2017 at 8:14 PM Lucas Stach wrote:
> Am Mittwoch, den 05.04.2017, 11:59 +0200 schrieb Daniel Vetter:
> > On Wed, Apr 05, 2017 at 10:15:44AM +0200, Lucas Stach wrote:
> > > Am Mittwoch, den 05.04.2017, 00:20 + schrieb Christopher James
&g
On Wed, Apr 5, 2017 at 4:27 PM, Daniel Vetter wrote:
On Wed, Apr 05, 2017 at 12:20:46AM +, Christopher James Halse
Rogers wrote:
On Tue, Apr 4, 2017 at 9:53 PM Daniel Vetter
wrote:
> On Tue, Apr 4, 2017 at 12:43 PM, Lucas Stach
> wrote:
> >> If I could guarante
On Tue, Apr 4, 2017 at 9:53 PM Daniel Vetter wrote:
> On Tue, Apr 4, 2017 at 12:43 PM, Lucas Stach
> wrote:
> >> If I could guarantee that I'd only ever run on 4.13-or-later kernels
> >> (I think that's when the previous patches will land?), then this would
> >> indeed be mostly unnecessary. It
On 4 April 2017 6:31:12 pm AEST, Daniel Vetter wrote:
>On Tue, Apr 04, 2017 at 06:13:20PM +1000, r...@ubuntu.com wrote:
>> From: Christopher James Halse Rogers
>>
>> Until recently, on (at least) nouveau, radeon, and amdgpu attempting
>to scanout of an
>> imported
her:
> > On Mon, Apr 3, 2017 at 4:24 AM, Christian König
> wrote:
> >> Am 03.04.2017 um 05:35 schrieb r...@ubuntu.com:
> >>> From: Christopher James Halse Rogers
> >>>
> >>>
> >>> BOs shared via dma-buf, either imported or exp
On Wed, 29 Mar 2017 at 13:04 Michel Dänzer wrote:
> On 29/03/17 09:27 AM, r...@ubuntu.com wrote:
> > From: Christopher James Halse Rogers <
> christopher.halse.rog...@canonical.com>
> >
> > Any use of the framebuffer will migrate it to VRAM, which is not
> sen
On Tue, 2013-11-05 at 14:23 -0800, Kristian H?gsberg wrote:
> On Mon, Nov 04, 2013 at 06:23:23PM -0800, Keith Packard wrote:
> > Instead of assuming that the size will be height * pitch, have the caller
> > pass
> > in the size explicitly.
> >
> > Signed-off-by: Keith Packard
> > ---
> > src/me
Signed-off-by: Christopher James Halse Rogers
Reviewed-by: Daniel Vetter
Tested-by: Daniel Vetter
---
Documentation/dma-buf-sharing.txt | 12
drivers/base/dma-buf.c| 28
2 files changed, 40 insertions(+)
diff --git a/Documentation/dma-buf-s
Each dma-buf has an associated size and it's reasonable for userspace
to want to know what it is.
Since userspace already has an fd, expose the size using the
size = lseek(fd, SEEK_END, 0); lseek(fd, SEEK_CUR, 0);
idiom.
Signed-off-by: Christopher James Halse Rogers
---
I've run in
Each dma-buf has an associated size and it's reasonable for userspace
to want to know what it is.
Since userspace already has an fd, expose the size using the
size = lseek(fd, SEEK_END, 0); lseek(fd, SEEK_CUR, 0);
idiom.
Signed-off-by: Christopher James Halse Rogers
---
I've run in
On Fri, 2011-04-29 at 17:55 +0200, Marcin Slusarz wrote:
> On Fri, Apr 29, 2011 at 01:57:10PM +1000, christopher.halse.rogers at
> canonical.com wrote:
> > From: Christopher James Halse Rogers > canonical.com>
> >
> > v2: Also pull out the drm_vblank_put call.
On Fri, 2011-04-29 at 17:55 +0200, Marcin Slusarz wrote:
> On Fri, Apr 29, 2011 at 01:57:10PM +1000,
> christopher.halse.rog...@canonical.com wrote:
> > From: Christopher James Halse Rogers
> >
> >
> > v2: Also pull out the drm_vblank_put call.
> > Signed-of
On Wed, 2011-04-27 at 11:08 +0200, Michel D?nzer wrote:
> On Mit, 2011-04-27 at 18:58 +1000, Christopher James Halse Rogers
> wrote:
> > On Wed, 2011-04-27 at 10:32 +0200, Michel D?nzer wrote:
> > > On Mit, 2011-04-27 at 16:10 +1000, christopher.halse.rogers at
>
> >
> > On Mit, 2011-04-27 at 16:10 +1000,
> > christopher.halse.rogers at canonical.com wrote:
> >> From: Christopher James Halse Rogers
> >>
> >>
> >> After emitting all the waiting vblank events no-one should hold
> >> a vblank referen
On Wed, 2011-04-27 at 11:08 +0200, Michel Dänzer wrote:
> On Mit, 2011-04-27 at 18:58 +1000, Christopher James Halse Rogers
> wrote:
> > On Wed, 2011-04-27 at 10:32 +0200, Michel Dänzer wrote:
> > > On Mit, 2011-04-27 at 16:10 +1000, christopher.halse.rog...@canon
t; On Mit, 2011-04-27 at 16:10 +1000,
> > christopher.halse.rog...@canonical.com wrote:
> >> From: Christopher James Halse Rogers
> >>
> >>
> >> After emitting all the waiting vblank events no-one should hold
> >> a vblank reference. Emit a warni
On Wed, 2011-04-27 at 11:08 +0200, Michel D?nzer wrote:
> On Mit, 2011-04-27 at 18:58 +1000, Christopher James Halse Rogers
> wrote:
> > On Wed, 2011-04-27 at 10:32 +0200, Michel D?nzer wrote:
> > > On Mit, 2011-04-27 at 16:10 +1000, christopher.halse.rogers at
>
On Wed, 2011-04-27 at 10:32 +0200, Michel D?nzer wrote:
> On Mit, 2011-04-27 at 16:10 +1000, christopher.halse.rogers at canonical.com
> wrote:
> > From: Christopher James Halse Rogers > canonical.com>
> >
> > This is the least-bad behaviour. It means that we sign
On Wed, 2011-04-27 at 10:36 +0200, Michel D?nzer wrote:
> On Mit, 2011-04-27 at 16:10 +1000, christopher.halse.rogers at canonical.com
> wrote:
> > From: Christopher James Halse Rogers > canonical.com>
> >
> > Signed-off-by: Christopher James Halse Rogers > ca
On Wed, 2011-04-27 at 11:08 +0200, Michel Dänzer wrote:
> On Mit, 2011-04-27 at 18:58 +1000, Christopher James Halse Rogers
> wrote:
> > On Wed, 2011-04-27 at 10:32 +0200, Michel Dänzer wrote:
> > > On Mit, 2011-04-27 at 16:10 +1000, christopher.halse.rog...@canon
On Wed, 2011-04-27 at 10:32 +0200, Michel Dänzer wrote:
> On Mit, 2011-04-27 at 16:10 +1000, christopher.halse.rog...@canonical.com
> wrote:
> > From: Christopher James Halse Rogers
> >
> >
> > This is the least-bad behaviour. It means that we signal the
>
On Wed, 2011-04-27 at 10:36 +0200, Michel Dänzer wrote:
> On Mit, 2011-04-27 at 16:10 +1000, christopher.halse.rog...@canonical.com
> wrote:
> > From: Christopher James Halse Rogers
> >
> >
> > Signed-off-by: Christopher James Halse Rogers
> >
> >
31 matches
Mail list logo
