linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: stsp <stsp2@yandex.ru>,
	linux-fbdev@vger.kernel.org,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: drmfb console switching problems/questions
Date: Fri, 09 Oct 2020 12:58:59 +0000	[thread overview]
Message-ID: <e2118f89-2c55-ec12-1e33-f2ba418af914@suse.de> (raw)
In-Reply-To: <70ce31ca-5922-584c-8631-3853c488f3c7@yandex.ru>


[-- Attachment #1.1: Type: text/plain, Size: 1571 bytes --]

Hi

Am 09.10.20 um 14:16 schrieb stsp:
> 09.10.2020 14:59, Thomas Zimmermann пишет:
>> Fbdev exposes the video ram (or a shadow buffer of it) to all
>> applications. Only one can draw at the same time. It's a limitation of
>> the design. To fix this, your application has to stop drawing when you
>> switch consoles.
> OK, thanks for info.
> Quite a sad news, if you ask me.
> Is there any ongoing work at solving that?

I don't think so. Both, SDL1 and fbdev, are pretty much dead these days.
The solution to fbdev is DRM, which does not have these problems.

You could your application under X11 to use SDL's X backend. X would do
all the VC handling then. For SDL advice you should ask on the SDL
mailing list.

> 
> Anyway, the fact that fb can
> permanently hang, is, I suppose,
> another problem - the one that
> can't be worked around in an app.
> I suspect it is the result of sdl doing
> ioctl(console_fd, KDSETMODE, KD_GRAPHICS);
> After which, I think, redrawing on a
> VC switch became disabled.
> Would it make sense to improve SAK
> to unfreeze from that? Otherwise its
> too easy to hang the screen permanently,
> and no way to recover.

That 'hung-up' problem you described sounds like the fbdev console does
not correctly redraw itself. But I don't know where the related code is
located.

Best regards
Thomas

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 516 bytes --]

  reply	other threads:[~2020-10-09 12:58 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 [this message]
2020-10-09 13:19       ` stsp
2020-10-09 13:31         ` Thomas Zimmermann
2020-10-09 14:14           ` stsp

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=e2118f89-2c55-ec12-1e33-f2ba418af914@suse.de \
    --to=tzimmermann@suse.de \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stsp2@yandex.ru \
    /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).