On Wed, 2018-08-15 at 14:15 -0700, Rodrigo Vivi wrote:
> On Tue, Jul 17, 2018 at 09:04:45PM +0100, Chris Wilson wrote:
> > Quoting Souza, Jose (2018-07-17 18:02:17)
> > > On Tue, 2018-07-17 at 08:28 +0100, Chris Wilson wrote:
> > > > Quoting José Roberto de Souza (2018-07-16 23:38:36)
> > > > > GPU
On Tue, Jul 17, 2018 at 09:04:45PM +0100, Chris Wilson wrote:
> Quoting Souza, Jose (2018-07-17 18:02:17)
> > On Tue, 2018-07-17 at 08:28 +0100, Chris Wilson wrote:
> > > Quoting José Roberto de Souza (2018-07-16 23:38:36)
> > > > GPU accelerators usually don't have display block or the display
> >
Quoting Souza, Jose (2018-07-17 18:02:17)
> On Tue, 2018-07-17 at 08:28 +0100, Chris Wilson wrote:
> > Quoting José Roberto de Souza (2018-07-16 23:38:36)
> > > GPU accelerators usually don't have display block or the display
> > > driver part can be disable when building driver(for servers it save
On Tue, 2018-07-17 at 08:28 +0100, Chris Wilson wrote:
> Quoting José Roberto de Souza (2018-07-16 23:38:36)
> > GPU accelerators usually don't have display block or the display
> > driver part can be disable when building driver(for servers it save
> > some resources) so it is important let usersp
Quoting José Roberto de Souza (2018-07-16 23:38:36)
> GPU accelerators usually don't have display block or the display
> driver part can be disable when building driver(for servers it save
> some resources) so it is important let userspace check this
> capability too.
We currently communicate that
GPU accelerators usually don't have display block or the display
driver part can be disable when building driver(for servers it save
some resources) so it is important let userspace check this
capability too.
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/drm_ioctl.c | 3 +++
include/u