From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC] WIP: video: implement quick-n-dirty framebuffer console
Date: Thu, 9 Jul 2015 08:49:20 +0200 [thread overview]
Message-ID: <20150709064920.GJ18700@pengutronix.de> (raw)
In-Reply-To: <1436346939-2306-1-git-send-email-antonynpavlov@gmail.com>
Hi Antony,
On Wed, Jul 08, 2015 at 12:15:39PM +0300, Antony Pavlov wrote:
> This patch realizes very simple framebuffer console for barebox.
> Minimal ANSI/VT100 Escape Sequence parser is used to ignore color
> change commands (based on GNU screen parser).
>
> THere are several ANSI/VT100 parsers:
>
> * GNU screen (git://git.savannah.gnu.org/screen.git);
> * st - simple terminal (http://git.suckless.org/st);
> * or even mutt (https://github.com/karelzak/mutt-kz).
There's even one in barebox in drivers/serial/efi-stdio.c
>
> fbconsole mini-HOWTO
> ====================
>
> 1. compile sandbox barebox with
>
> CONFIG_VIDEO=y
> CONFIG_FBCONSOLE=y
> CONFIG_DRIVER_VIDEO_SDL=y
>
> 2. run barebox
>
> 3. test fbconsole
>
> fbconsole0.active=o
I gave it a try on real hardware. Works nice.
>
> TODO:
>
> * no visible cursor;
I couldn't resist and did some hacking on this. The cursor is visible
now. Also I implemented more control characters and color support. I'll
send an update patch shortly.
> * FIXME: /dev/fb0 is hardcoded;
> * FIXME: drop blanckchar() dirty hack;
> * Sascha Hauer: character set should be prerendered for the actual framebuffer format
> before printing a string.
Did I mention that ealier? I don't know if that's a good idea since with
color support we would need quite some memory and I'm not sure if that
would really speed up things.
I'd really love to have framebuffer console in barebox. I wasn't aware
that this would be relatively straight forward to implement though. I'm
willing to help working on this job so that we finally have a fbcon.
Maybe one first step is to simply merge the font so that the patches
get smaller.
Sascha
--
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:[~2015-07-09 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 9:15 Antony Pavlov
2015-07-09 6:49 ` Sascha Hauer [this message]
2015-07-09 9:42 ` Antony Pavlov
2015-07-09 10:46 ` Sascha Hauer
2015-07-09 8:16 ` Sascha Hauer
2015-07-09 9:47 ` Antony Pavlov
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=20150709064920.GJ18700@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
/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