From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Petr Mladek <pmladek@suse.com>,
linux-fbdev@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Hans de Goede <hdegoede@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v4 0/3] console/fbcon: Add support for deferred console takeover
Date: Wed, 27 Jun 2018 09:47:51 +0000 [thread overview]
Message-ID: <66532157.tkLS2buF0U@amdc3058> (raw)
In-Reply-To: <20180627091520.GI13978@phenom.ffwll.local>
On Wednesday, June 27, 2018 11:15:20 AM Daniel Vetter wrote:
> On Tue, Jun 26, 2018 at 08:36:09PM +0200, Hans de Goede wrote:
> > Hi All,
> >
> > Here is v4 of my patch-set, to delay fbcon taking over the console (and
> > binding to fbdev devices) until there actually is some text output to the
> > console. This is intended for use with the "quiet" cmdline option, in
> > combination with a bootloader which leaves the vendor's logo /
> > EFI bootgraphics put up by the firmware intact on the EFI framebuffer.
> >
> > The end goal here is a boot where the firmware shows its boot graphics
> > and these stay in place for a couple of seconds until the GUI loads and
> > the GUI then smoothly takes over the framebuffer without any distruptions.
> >
> > This patch-set spans 2 subsystems.
> >
> > Petr, the printk subsys change is really trivial (1 line addition) can we
> > get your Acked-by for merging all 3 patches through the fbdev tree?
> >
> > Changelog:
> >
> > Changes in v4:
> > -Keep the comments about which fbcon functions need locks in place
> >
> > Changes in v3:
> > -Export is_console_locke() for use in modules (as fbcon may be built as a .ko)
> > -Use WARN_CONSOLE_UNLOCKED() in several places in the fbcon code to assert
> > proper locking (requested by Daniel)
> > -Unregister the fbcon-dummycon-output-notifier on fbcon_exit() (req. by Daniel)
> > -Document the fbcon=nodefer commandline option (req. by Emil)
> >
> > Changes in v2:
> > -Check the whole string when checking for erases in putcs, instead of just
> > the first char
> > -Make dummycon_blank return 1, so that a redraw gets triggered and any text
> > rendered while blanked gets output so that it can trigger a deferred
> > takeover if one is pending
>
> Wrt merging I think it'd be best if we stuff this into drm-misc-next -
> that will increase testing by gpu drivers a lot, instead of a suprise when
> the fbdev pull lands in upstream.
>
> Bart, is that ok with you?
Not really, since there are efifb changes in the queue which depend
on this series I would really prefer to merge all patches through
fbdev tree.
Also fbdev tree is pulled into -next kernels so testing coverage
should be okay (I assume that everybody are testing -next kernels in
addition to their own branches :-)..
> Hans, if Bart acks this you can directly push this imo.
> -Daniel
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
WARNING: multiple messages have this Message-ID (diff)
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Petr Mladek <pmladek@suse.com>,
linux-fbdev@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Hans de Goede <hdegoede@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v4 0/3] console/fbcon: Add support for deferred console takeover
Date: Wed, 27 Jun 2018 11:47:51 +0200 [thread overview]
Message-ID: <66532157.tkLS2buF0U@amdc3058> (raw)
In-Reply-To: <20180627091520.GI13978@phenom.ffwll.local>
On Wednesday, June 27, 2018 11:15:20 AM Daniel Vetter wrote:
> On Tue, Jun 26, 2018 at 08:36:09PM +0200, Hans de Goede wrote:
> > Hi All,
> >
> > Here is v4 of my patch-set, to delay fbcon taking over the console (and
> > binding to fbdev devices) until there actually is some text output to the
> > console. This is intended for use with the "quiet" cmdline option, in
> > combination with a bootloader which leaves the vendor's logo /
> > EFI bootgraphics put up by the firmware intact on the EFI framebuffer.
> >
> > The end goal here is a boot where the firmware shows its boot graphics
> > and these stay in place for a couple of seconds until the GUI loads and
> > the GUI then smoothly takes over the framebuffer without any distruptions.
> >
> > This patch-set spans 2 subsystems.
> >
> > Petr, the printk subsys change is really trivial (1 line addition) can we
> > get your Acked-by for merging all 3 patches through the fbdev tree?
> >
> > Changelog:
> >
> > Changes in v4:
> > -Keep the comments about which fbcon functions need locks in place
> >
> > Changes in v3:
> > -Export is_console_locke() for use in modules (as fbcon may be built as a .ko)
> > -Use WARN_CONSOLE_UNLOCKED() in several places in the fbcon code to assert
> > proper locking (requested by Daniel)
> > -Unregister the fbcon-dummycon-output-notifier on fbcon_exit() (req. by Daniel)
> > -Document the fbcon=nodefer commandline option (req. by Emil)
> >
> > Changes in v2:
> > -Check the whole string when checking for erases in putcs, instead of just
> > the first char
> > -Make dummycon_blank return 1, so that a redraw gets triggered and any text
> > rendered while blanked gets output so that it can trigger a deferred
> > takeover if one is pending
>
> Wrt merging I think it'd be best if we stuff this into drm-misc-next -
> that will increase testing by gpu drivers a lot, instead of a suprise when
> the fbdev pull lands in upstream.
>
> Bart, is that ok with you?
Not really, since there are efifb changes in the queue which depend
on this series I would really prefer to merge all patches through
fbdev tree.
Also fbdev tree is pulled into -next kernels so testing coverage
should be okay (I assume that everybody are testing -next kernels in
addition to their own branches :-)..
> Hans, if Bart acks this you can directly push this imo.
> -Daniel
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Hans de Goede <hdegoede@redhat.com>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-fbdev@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] console/fbcon: Add support for deferred console takeover
Date: Wed, 27 Jun 2018 11:47:51 +0200 [thread overview]
Message-ID: <66532157.tkLS2buF0U@amdc3058> (raw)
In-Reply-To: <20180627091520.GI13978@phenom.ffwll.local>
On Wednesday, June 27, 2018 11:15:20 AM Daniel Vetter wrote:
> On Tue, Jun 26, 2018 at 08:36:09PM +0200, Hans de Goede wrote:
> > Hi All,
> >
> > Here is v4 of my patch-set, to delay fbcon taking over the console (and
> > binding to fbdev devices) until there actually is some text output to the
> > console. This is intended for use with the "quiet" cmdline option, in
> > combination with a bootloader which leaves the vendor's logo /
> > EFI bootgraphics put up by the firmware intact on the EFI framebuffer.
> >
> > The end goal here is a boot where the firmware shows its boot graphics
> > and these stay in place for a couple of seconds until the GUI loads and
> > the GUI then smoothly takes over the framebuffer without any distruptions.
> >
> > This patch-set spans 2 subsystems.
> >
> > Petr, the printk subsys change is really trivial (1 line addition) can we
> > get your Acked-by for merging all 3 patches through the fbdev tree?
> >
> > Changelog:
> >
> > Changes in v4:
> > -Keep the comments about which fbcon functions need locks in place
> >
> > Changes in v3:
> > -Export is_console_locke() for use in modules (as fbcon may be built as a .ko)
> > -Use WARN_CONSOLE_UNLOCKED() in several places in the fbcon code to assert
> > proper locking (requested by Daniel)
> > -Unregister the fbcon-dummycon-output-notifier on fbcon_exit() (req. by Daniel)
> > -Document the fbcon=nodefer commandline option (req. by Emil)
> >
> > Changes in v2:
> > -Check the whole string when checking for erases in putcs, instead of just
> > the first char
> > -Make dummycon_blank return 1, so that a redraw gets triggered and any text
> > rendered while blanked gets output so that it can trigger a deferred
> > takeover if one is pending
>
> Wrt merging I think it'd be best if we stuff this into drm-misc-next -
> that will increase testing by gpu drivers a lot, instead of a suprise when
> the fbdev pull lands in upstream.
>
> Bart, is that ok with you?
Not really, since there are efifb changes in the queue which depend
on this series I would really prefer to merge all patches through
fbdev tree.
Also fbdev tree is pulled into -next kernels so testing coverage
should be okay (I assume that everybody are testing -next kernels in
addition to their own branches :-)..
> Hans, if Bart acks this you can directly push this imo.
> -Daniel
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2018-06-27 9:47 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 18:36 [PATCH v4 0/3] console/fbcon: Add support for deferred console takeover Hans de Goede
2018-06-26 18:36 ` Hans de Goede
2018-06-26 18:36 ` Hans de Goede
2018-06-26 18:36 ` [PATCH v3 1/3] printk: Export is_console_locked Hans de Goede
2018-06-26 18:36 ` Hans de Goede
2018-06-26 18:36 ` Hans de Goede
2018-06-26 18:38 ` Hans de Goede
2018-06-26 18:38 ` Hans de Goede
2018-06-26 18:38 ` Hans de Goede
2018-06-27 1:07 ` Sergey Senozhatsky
2018-06-27 1:07 ` Sergey Senozhatsky
2018-06-27 13:31 ` Petr Mladek
2018-06-27 13:31 ` Petr Mladek
2018-06-26 18:36 ` [PATCH v3 2/3] fbcon: Call WARN_CONSOLE_UNLOCKED() where applicable Hans de Goede
2018-06-26 18:36 ` Hans de Goede
2018-06-26 18:36 ` Hans de Goede
2018-06-27 1:09 ` Sergey Senozhatsky
2018-06-27 1:09 ` Sergey Senozhatsky
2018-06-26 18:36 ` [PATCH v3 3/3] console/fbcon: Add support for deferred console takeover Hans de Goede
2018-06-26 18:36 ` Hans de Goede
2018-06-26 18:36 ` Hans de Goede
2018-06-28 7:55 ` Daniel Vetter
2018-06-28 7:55 ` Daniel Vetter
2018-06-28 7:55 ` Daniel Vetter
2018-06-28 8:20 ` Hans de Goede
2018-06-28 8:20 ` Hans de Goede
2018-06-28 8:20 ` Hans de Goede
2018-06-28 8:37 ` Daniel Vetter
2018-06-28 8:37 ` Daniel Vetter
2018-06-28 8:37 ` Daniel Vetter
2018-06-28 8:58 ` Hans de Goede
2018-06-28 8:58 ` Hans de Goede
2018-06-28 8:58 ` Hans de Goede
2018-06-26 19:14 ` [PATCH v4 0/3] " Steven Rostedt
2018-06-26 19:14 ` Steven Rostedt
2018-06-26 19:14 ` Steven Rostedt
2018-06-27 9:15 ` Daniel Vetter
2018-06-27 9:15 ` Daniel Vetter
2018-06-27 9:15 ` Daniel Vetter
2018-06-27 9:47 ` Bartlomiej Zolnierkiewicz [this message]
2018-06-27 9:47 ` Bartlomiej Zolnierkiewicz
2018-06-27 9:47 ` Bartlomiej Zolnierkiewicz
2018-06-27 11:13 ` Hans de Goede
2018-06-27 11:13 ` Hans de Goede
2018-06-27 11:13 ` Hans de Goede
2018-06-27 14:15 ` Daniel Vetter
2018-06-27 14:15 ` Daniel Vetter
2018-06-27 14:15 ` 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=66532157.tkLS2buF0U@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.