From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Petr Mladek <pmladek@suse.com>,
linux-fbdev@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 3/3] console/fbcon: Add support for deferred console takeover
Date: Tue, 26 Jun 2018 18:29:44 +0000 [thread overview]
Message-ID: <ad0becb1-eece-b89c-c77f-273403052491@redhat.com> (raw)
In-Reply-To: <CAHp75VfxQMTMMSZvNBtHGGQAyBaURrBTddtuiQqFmpcjWG6Ktg@mail.gmail.com>
Hi,
On 26-06-18 19:12, Andy Shevchenko wrote:
> On Tue, Jun 26, 2018 at 4:55 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> Currently fbcon claims fbdevs as soon as they are registered and takes over
>> the console as soon as the first fbdev gets registered.
>>
>> This behavior is undesirable in cases where a smooth graphical bootup is
>> desired, in such cases we typically want the contents of the framebuffer
>> (typically a vendor logo) to stay in place as is.
>>
>> The current solution for this problem (on embedded systems) is to not
>> enable fbcon.
>>
>> This commit adds a new FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER config option,
>> which when enabled defers fbcon taking over the console from the dummy
>> console until the first text is displayed on the console. Together with the
>> "quiet" kernel commandline option, this allows fbcon to still be used
>> together with a smooth graphical bootup, having it take over the console as
>> soon as e.g. an error message is logged.
>
>> + for (i = 0; i < FB_MAX; i++) {
>> + if (registered_fb[i])
>> + fbcon_fb_registered(registered_fb[i]);
>> + }
>
> Simple git grep shows that we perhaps do
>
> #define for_each_registered_fbcon(i) ...
>
> (As an example see for_each_pci_bridge() how it's done there)
This is probably a worthwhile cleanup for all the fbdev related
code / drivers. But outside of the scope of this patchset.
Regards,
Hans
next prev parent reply other threads:[~2018-06-26 18:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 13:55 [PATCH v3 0/3] console/fbcon: Add support for deferred console takeover Hans de Goede
2018-06-26 13:55 ` [PATCH v3 1/3] printk: Export is_console_locked Hans de Goede
2018-06-26 13:55 ` [PATCH v3 2/3] fbcon: Call WARN_CONSOLE_UNLOCKED() where applicable Hans de Goede
2018-06-26 14:00 ` Daniel Vetter
2018-06-26 14:47 ` Steven Rostedt
2018-06-26 18:29 ` Hans de Goede
2018-06-26 13:55 ` [PATCH v3 3/3] console/fbcon: Add support for deferred console takeover Hans de Goede
2018-06-26 17:12 ` Andy Shevchenko
2018-06-26 17:13 ` Andy Shevchenko
2018-06-26 18:29 ` Hans de Goede [this message]
2018-06-26 18:49 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2018-06-26 18:36 [PATCH v4 0/3] " Hans de Goede
2018-06-26 18:36 ` [PATCH v3 3/3] " Hans de Goede
2018-06-28 7:55 ` Daniel Vetter
2018-06-28 8:20 ` Hans de Goede
2018-06-28 8:37 ` Daniel Vetter
2018-06-28 8:58 ` Hans de Goede
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=ad0becb1-eece-b89c-c77f-273403052491@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy.shevchenko@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.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
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).