From: stsp <stsp2@yandex.ru>
To: Thomas Zimmermann <tzimmermann@suse.de>,
linux-fbdev@vger.kernel.org,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: drmfb console switching problems/questions
Date: Fri, 9 Oct 2020 17:14:42 +0300 [thread overview]
Message-ID: <e3f40930-6927-042f-7857-e843e1e24236@yandex.ru> (raw)
In-Reply-To: <050632f0-6440-1254-2aed-931dd515ff37@suse.de>
09.10.2020 16:31, Thomas Zimmermann пишет:
> I can't say for sure. IIRC SDL2 can use DRM directly.
Yes, that was a great hint indeed,
thanks. It didn't work for me in the past
(a year ago or so), so I added SDL1
support. But now I re-tried, and it indeed
works!
And, as far as I can tell, the hanging
behaviour does not happen, at least
not that simple.
Thank you.
prev parent reply other threads:[~2020-10-09 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 10:50 drmfb console switching problems/questions stsp
2020-10-09 11:59 ` Thomas Zimmermann
2020-10-09 12:16 ` stsp
2020-10-09 12:58 ` Thomas Zimmermann
2020-10-09 13:19 ` stsp
2020-10-09 13:31 ` Thomas Zimmermann
2020-10-09 14:14 ` stsp [this message]
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=e3f40930-6927-042f-7857-e843e1e24236@yandex.ru \
--to=stsp2@yandex.ru \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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).