From: Antony Pavlov <antonynpavlov@gmail.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC] [JUST DEMO] commands: implement 'fbputs' command
Date: Mon, 2 Feb 2015 12:46:58 +0400 [thread overview]
Message-ID: <20150202124658.d5a89863bda9de9bba4a895d@gmail.com> (raw)
In-Reply-To: <6A48CA9F-26EB-433F-BE18-CDFEB050970B@jcrosoft.com>
On Mon, 26 Jan 2015 16:55:40 +0800
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> wrote:
>
> > On Jan 26, 2015, at 4:14 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> >
> > On Sun, Jan 25, 2015 at 05:21:30PM +0300, Antony Pavlov wrote:
> >> Mainline barebox at the moment has no framebuffer
> >> console support.
> >> The 'fbputs' demo command displays a text string
> >> on fb device.
> >>
> >> This quick-n-dirty patch demonstates that barebox
> >> framebuffer console can be easely realized.
> >>
> >> I'm awaiting your comments!
> >
> > Unfortunately real console support is not that simple, we would have to
> > parse ANSI escape sequences up to some point to make it generally usable.
> >
> > Jean Christophe has framebuffer console patches, he'll probably comment
> > on this one aswell.
> > Personally I would be fine with your simple approach until real console
> > support arrives.
>
>
> Yes I have the framebuffer console support and yes you do need to have the ANSI support
> and it’s not that easy
>
Are your planning add your framebuffer console patches to mainline barebox?
What is about your raspberry-pi patchseries?
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-02-02 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 14:21 Antony Pavlov
2015-01-26 8:14 ` Sascha Hauer
2015-01-26 8:55 ` Jean-Christophe PLAGNIOL-VILLARD
2015-01-26 9:20 ` Antony Pavlov
2015-02-02 8:46 ` Antony Pavlov [this message]
2015-02-02 21:28 ` Alexander Aring
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=20150202124658.d5a89863bda9de9bba4a895d@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.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