From: David Herrmann <dh.herrmann@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: PJ Waskiewicz <pjwaskiewicz@gmail.com>,
Sarah A Sharp <sarah@minilop.net>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Anton Arapov <arapov@gmail.com>,
Dirk Hohndel <hohndel@infradead.org>
Subject: Re: [Ksummit-discuss] Fwd: [TECH TOPIC] QR encoded oops for the kernel
Date: Mon, 19 May 2014 13:59:13 +0200 [thread overview]
Message-ID: <CANq1E4TsYT+qPVrQaRKZ8ZL6vt1DbMtU=ZxCWLHWDBZYqwoo6A@mail.gmail.com> (raw)
In-Reply-To: <CAKMK7uE5F+_kwtRKjkjbr0d+-r8VjVD7UD5b1rGizhkfCVRkxQ@mail.gmail.com>
Hi
On Wed, May 14, 2014 at 10:24 PM, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> On Wed, May 14, 2014 at 10:00 PM, Levente Kurusa <levex@linux.com> wrote:
>> I as well would love to support QR codes in textmode, but I think that
>> it's really not possible at the moment.
>
> David Herrman is working on some new infrastructure for emergency log
> services on top of drm/kms drivers since we really, really want to
> move away from the horrors called fbcon. His design is fairly neat and
> there shouldn't be that big an issue with replacing the current
> character-painting code he has with some oops-painting code. Adding
> him to the discussion so he can point at some of the patches.
Still working on that, but I have no public tree for it right now. The
design basically asks all registered graphics driver for a
kernel-mapped framebuffer and the current mode/format. In case the
current FB is not / cannot be mapped, we try to flip to a fallback
buffer with the same mode/format. If even that fails, we try to do a
full modeset and DPMS stuff and more (this is all the responsibility
of the driver).
To avoid expensive call-paths, we do this step-by-step: first all
drivers are asked for the current FB and we render on all successfull
mappings. Then we continue with the remaining drivers and the
remaining options, and so on..
Note that setting a modern DRM driver into text-mode is far more
expensive than asking for the current FB. This is even mostly true for
any VESA-compatible card (through SimpleDRM). So I don't see why
anyone should bother using textmode for QR codes (but if you think
that's fun, I won't stop you).
The kernel-core will see one function, drm_render_oops() (or something
similar), which will try to do its best to render on all screens.
Default mode is rendering the kernel-log (through drm_log), but any
other stuff like QR is possible. There's a helper called
drm_draw_pixel() that can draw pixels in _any_ RGB format (maybe even
YUV and stuff), so the renderers don't even have to deal with DRM
formats.
I will show a prototype at LPC14, if anyone is interested.
David
next prev parent reply other threads:[~2014-05-19 11:59 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 4:14 [Ksummit-discuss] " Jason Cooper
2014-05-11 15:57 ` Sarah A Sharp
2014-05-11 16:29 ` Levente Kurusa
2014-05-11 16:37 ` Laurent Pinchart
2014-05-11 17:18 ` Levente Kurusa
2014-05-11 17:52 ` Teodora Băluţă
2014-05-11 21:49 ` Laurent Pinchart
2014-05-12 16:15 ` Jason Cooper
2014-05-12 16:36 ` Levente Kurusa
2014-05-12 16:53 ` H. Peter Anvin
2014-05-30 18:55 ` Steven Rostedt
2014-05-12 17:00 ` Johannes Berg
2014-05-12 17:46 ` Teodora Băluţă
[not found] ` <CACV2jQCV=rRFg-+x1B3H1=GM5rB_YWp1UU1p7xXkozHKv1Ewvg@mail.gmail.com>
2014-05-13 6:44 ` [Ksummit-discuss] Fwd: " Teodora Băluţă
2014-05-13 7:08 ` Josh Triplett
2014-05-13 15:52 ` Levente Kurusa
2014-05-13 18:42 ` Andy Lutomirski
2014-05-13 20:18 ` josh
2014-05-14 8:20 ` Johannes Berg
2014-05-14 15:52 ` Josh Triplett
2014-05-14 16:00 ` H. Peter Anvin
2014-05-14 16:09 ` Andy Lutomirski
2014-05-14 18:54 ` Josh Triplett
2014-05-14 20:00 ` Levente Kurusa
2014-05-14 20:24 ` Daniel Vetter
2014-05-19 11:59 ` David Herrmann [this message]
2014-05-14 22:55 ` Josh Triplett
2014-05-15 12:44 ` Levente Kurusa
2014-05-15 19:19 ` H. Peter Anvin
2014-05-15 19:18 ` H. Peter Anvin
2014-05-15 20:41 ` Levente Kurusa
2014-05-13 14:45 ` [Ksummit-discuss] " David Woodhouse
2014-05-15 19:21 ` H. Peter Anvin
2014-05-15 19:53 ` Jiri Kosina
2014-05-12 15:53 ` Jason Cooper
2014-05-12 16:49 ` Levente Kurusa
2014-05-12 17:09 ` H. Peter Anvin
2014-05-12 17:50 ` Teodora Băluţă
2014-05-13 11:25 ` Greg KH
2014-05-13 14:41 ` Sarah A Sharp
2014-05-13 15:05 ` Greg KH
2014-05-13 15:51 ` Sarah A Sharp
2014-05-13 15:59 ` Josh Boyer
2014-05-13 16:07 ` Theodore Ts'o
2014-05-13 17:43 ` Levente Kurusa
2014-05-13 18:14 ` Teodora Baluta
2014-05-15 14:24 ` Levente Kurusa
2014-05-15 16:02 ` Teodora Băluţă
2014-05-14 1:14 ` Josh Boyer
2014-05-15 17:01 ` Levente Kurusa
2014-05-15 17:11 ` Josh Boyer
2014-05-17 15:02 ` Levente Kurusa
2014-05-15 5:41 ` PJ Waskiewicz
2014-05-15 15:41 ` Theodore Ts'o
2014-05-17 16:36 ` Levente Kurusa
2014-05-20 14:47 ` Theodore Ts'o
2014-05-21 18:03 ` Levente Kurusa
2014-05-25 19:49 ` Teodora Băluţă
2014-05-15 19:24 ` H. Peter Anvin
2014-05-15 21:13 ` Levente Kurusa
2014-05-13 16:03 ` Greg KH
2014-05-12 17:24 ` Jason Cooper
2014-05-11 17:49 ` Sarah A Sharp
2014-05-12 10:13 ` Masami Hiramatsu
2014-05-12 2:38 ` H. Peter Anvin
2014-05-12 6:13 ` Josh Triplett
2014-05-12 9:23 ` David Woodhouse
2014-05-12 13:48 ` Lukáš Czerner
2014-05-12 16:24 ` Jason Cooper
2014-05-12 16:45 ` H. Peter Anvin
2014-05-12 16:22 ` Jason Cooper
2014-05-12 16:46 ` H. Peter Anvin
2014-05-12 17:32 ` Jason Cooper
2014-05-12 17:42 ` Sarah A Sharp
2014-05-12 15:46 ` Jason Cooper
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='CANq1E4TsYT+qPVrQaRKZ8ZL6vt1DbMtU=ZxCWLHWDBZYqwoo6A@mail.gmail.com' \
--to=dh.herrmann@gmail.com \
--cc=arapov@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=hohndel@infradead.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=pjwaskiewicz@gmail.com \
--cc=sarah@minilop.net \
/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