From: Alexandre Courbot <gnurou@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: EARLY_PRINTK equivalent for framebuffers.
Date: Fri, 29 Aug 2014 01:36:00 +0000 [thread overview]
Message-ID: <CAAVeFuJee6cUURJGCLA8A8FbSApy7WiABdCYo9ra_ChBe4=6yQ@mail.gmail.com> (raw)
In-Reply-To: <CAKON4Owx5wQS29qj9Ks2CzP-Q9Kos6=6MbPRxS+4n9WkdbWegQ@mail.gmail.com>
On Thu, Aug 28, 2014 at 12:19 PM, jonsmirl@gmail.com <jonsmirl@gmail.com> wrote:
> Is there some existing way to do early printk type output to a
> framebuffer that has been set up by the bootloader? early printk is
> before any device drivers are loaded.
>
> If not, what would it take to create a way to do this? Something along
> the lines of build in the fbdev library and give it an address plus
> x/y layout of the buffer. Assume that everything else is set up and
> anything written to the buffer will appear on the display. Then hook
> into where the kernel does early printk on uarts and add in support
> for this buffer. The core fbdev library implements scrolling and
> graphical characters.
simplefb does something like this (implement a console on top of a
framebuffer set up by the bootloader), but I don't think you can use
it for earlyprintk. It would be a very interesting option though (and
even better if it could be used by the kernel decompression code), but
I suspect this is more involved than good old UART as you need to
manage fonts, pixel format, screen geometry, etc.
OTOH it would be very useful for some retail devices that come without
an accessible serial line, but have a framebuffer set up by the
bootloader.
Alex.
next prev parent reply other threads:[~2014-08-29 1:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 19:19 EARLY_PRINTK equivalent for framebuffers jonsmirl
2014-08-29 1:36 ` Alexandre Courbot [this message]
2014-08-29 1:40 ` jonsmirl
2014-08-29 1:54 ` Alexandre Courbot
2014-08-29 2:00 ` jonsmirl
2014-08-29 2:05 ` Alexandre Courbot
2014-08-29 2:09 ` jonsmirl
2014-08-29 8:51 ` Geert Uytterhoeven
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='CAAVeFuJee6cUURJGCLA8A8FbSApy7WiABdCYo9ra_ChBe4=6yQ@mail.gmail.com' \
--to=gnurou@gmail.com \
--cc=linux-fbdev@vger.kernel.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