[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACvgo53s7DC6+h=piS3kgoub=P0k+jjLgy5WAT6Mt92EutRxMw@mail.gmail.com>
Date: Mon, 4 Dec 2017 17:52:58 +0000
From: Emil Velikov <emil.l.velikov@...il.com>
To: Jose Abreu <Jose.Abreu@...opsys.com>
Cc: Alexey Brodkin <Alexey.Brodkin@...opsys.com>,
"l.stach@...gutronix.de" <l.stach@...gutronix.de>,
"daniel.vetter@...ll.ch" <daniel.vetter@...ll.ch>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"airlied@...hat.com" <airlied@...hat.com>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>
Subject: Re: xf86-video-armada via UDL [was: Re: UDL's fbdev doesn't work for
user-space apps]
On 4 December 2017 at 14:02, Jose Abreu <Jose.Abreu@...opsys.com> wrote:
> On 04-12-2017 13:16, Alexey Brodkin wrote:
>> Option "kmsdev" "/dev/dri/card1"
>
> Which drm driver uses /dev/dri/card0? I'm seing drmOpen code and
> if you don't specify the busID it will fallback for the first
> card that matches "armada-drm" or "imx-drm" or "udl".
>
As you've noticed, drmOpen can give you some 'nice' side-effects.
I'd recommend getting a list of devices with drmGetDevice{,s}2 and
applying $heuristics to filter the device you want.
-Emil
Powered by blists - more mailing lists