From: Sascha Hauer <s.hauer@pengutronix.de>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Documentation: framebuffer: update documentation to current state
Date: Wed, 4 Apr 2018 07:55:01 +0200 [thread overview]
Message-ID: <20180404055501.pqohi44y2yec74ki@pengutronix.de> (raw)
In-Reply-To: <20180403160854.5654-1-linux@rempel-privat.de>
On Tue, Apr 03, 2018 at 06:08:54PM +0200, Oleksij Rempel wrote:
> Framebuffer console support was added in 2015.
>
> Reported-by: TobSnyder at #barebox irc
> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
> ---
> Documentation/user/framebuffer.rst | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
Applied, thanks
Sascha
>
> diff --git a/Documentation/user/framebuffer.rst b/Documentation/user/framebuffer.rst
> index 7d004fa1c..d033ff08f 100644
> --- a/Documentation/user/framebuffer.rst
> +++ b/Documentation/user/framebuffer.rst
> @@ -1,9 +1,10 @@
> Framebuffer support
> ===================
>
> -barebox has support for framebuffer devices. Currently there is no console support
> -for framebuffers, so framebuffer usage is limited to splash screens only. barebox
> -supports BMP and PNG graphics using the :ref:`command_splash` command. barebox
> +Framebuffer spash screen
> +------------------------
> +
> +barebox supports BMP and PNG graphics using the :ref:`command_splash` command. barebox
> currently has no support for backlights, so unless there is a board specific enable
> hook for enabling a display it must be done manually with a script. Since barebox
> has nothing useful to show on the framebuffer it doesn't enable it during startup.
> --
> 2.14.1
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-04-04 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 16:08 Oleksij Rempel
2018-04-04 5:55 ` Sascha Hauer [this message]
2018-04-04 12:48 ` Roland Hieber
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=20180404055501.pqohi44y2yec74ki@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=linux@rempel-privat.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