From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: "open list:FRAMEBUFFER LAYER" <linux-fbdev@vger.kernel.org>,
Gerd Hoffmann <kraxel@redhat.com>,
dri-devel@lists.freedesktop.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fbdev: wait for references go away
Date: Mon, 20 Jan 2020 18:11:46 +0000 [thread overview]
Message-ID: <20200120181146.GL1314@mail-itl> (raw)
In-Reply-To: <d143e43b-8a38-940e-3ae5-e7b830a74bb3@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Mon, Jan 20, 2020 at 06:51:17PM +0100, Bartlomiej Zolnierkiewicz wrote:
> I guess that a problem is happening during DRM driver load while fbdev
> driver is loaded? I assume do_unregister_framebuffer() is called inside
> do_remove_conflicting_framebuffers()?
Yes, exactly. More details here:
https://lists.linuxfoundation.org/pipermail/virtualization/2020-January/045026.html
> At first glance it seems to be an user-space issue as it should not be
> holding references on /dev/fb0 while DRM driver is being loaded.
How plymouth would know when exactly it needs to release /dev/fb0?
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-20 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200120100025eucas1p21f5e2da0fd7c1fcb33cb47a97e9e645c@eucas1p2.samsung.com>
2020-01-20 10:00 ` [PATCH] fbdev: wait for references go away Gerd Hoffmann
2020-01-20 17:51 ` Bartlomiej Zolnierkiewicz
2020-01-20 17:54 ` Bartlomiej Zolnierkiewicz
2020-01-20 18:11 ` Marek Marczykowski-Górecki [this message]
2020-01-21 5:53 ` Gerd Hoffmann
2020-01-28 15:20 ` Bartlomiej Zolnierkiewicz
2020-01-28 16:39 ` Daniel Vetter
2020-01-28 16:44 ` Daniel Vetter
2020-01-28 16:58 ` Daniel Vetter
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=20200120181146.GL1314@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).