dri-devel Archive on lore.kernel.org
 help / color / Atom feed
From: Simon Ser <contact@emersion.fr>
To: Mauro Rossi <issor.oruam@gmail.com>
Cc: "robert.foss@collabora.com" <robert.foss@collabora.com>,
	"cwhuang@linux.org.tw" <cwhuang@linux.org.tw>,
	"emil.l.velikov@gmail.com" <emil.l.velikov@gmail.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] xf86drm: add drmOpenByFB
Date: Sat, 23 May 2020 21:36:45 +0000
Message-ID: <U8jrM_GtxrGK0nNOiMU4H-uVLXPdv79TjXOQh_PVn7tkWFixOqW3wA15x5MIpygORK3x8X8Kdz45tbqe57MA3nAWh-J0K8QIfDSSa6yeOc0=@emersion.fr> (raw)
In-Reply-To: <20200523154426.1088988-1-issor.oruam@gmail.com>

On Saturday, May 23, 2020 5:44 PM, Mauro Rossi <issor.oruam@gmail.com> wrote:

> OpenByFB is introduced to overcome GPU driver loading order issue
> on a device with multiple GPUs, e.g. Intel iGPU and Nvidia dGPU
> where the first drmfb kernel module loaded will become device file
> /dev/dri/card0 and the second will become /dev/dri/card1
>
> The use case is to prefer Intel iGPU over dGPU, or viceversa,
> in a deterministic and reliable manner.
>
> OpenByFB function opens the DRM device with specified fb and node type,
> thus enabling gralloc to open the correct device node of the primary fb,
> regardless of the GPU driver loading order.

"FB" is ambiguous here, because the other FB functions in this file
refer to DRM frame-buffer objects (as opposed to fbdev I believe?).
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 15:44 Mauro Rossi
2020-05-23 21:36 ` Simon Ser [this message]
2020-05-24 18:53 ` Daniel Vetter
2020-05-24 19:25   ` Simon Ser
2020-05-28  9:46     ` Chih-Wei Huang
2020-05-28 12:38       ` Emil Velikov
2020-05-29  7:48       ` Pekka Paalanen
2020-05-29 14:20         ` Alex Deucher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='U8jrM_GtxrGK0nNOiMU4H-uVLXPdv79TjXOQh_PVn7tkWFixOqW3wA15x5MIpygORK3x8X8Kdz45tbqe57MA3nAWh-J0K8QIfDSSa6yeOc0=@emersion.fr' \
    --to=contact@emersion.fr \
    --cc=cwhuang@linux.org.tw \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=issor.oruam@gmail.com \
    --cc=robert.foss@collabora.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

dri-devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/dri-devel/0 dri-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dri-devel dri-devel/ https://lore.kernel.org/dri-devel \
		dri-devel@lists.freedesktop.org
	public-inbox-index dri-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.freedesktop.lists.dri-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git