lkml.org 
[lkml]   [2014]   [Apr]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] QR encoding for Oops messages
On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote:
> Or, we could use core_param and simply have 'oops_qr' or
> 'qr_oops'. In my humble opinion the latter sounds better.

Ack. My original suggestion was focused on 0=disable, >0 is scale. I
literally pulled the name from my nether-regions. :-)

> Oh and another suggestion, I think placing it in the bottom-right
> corner would be better since then we wouldn't overwrite some of
> the timestamps and messages.

The real text is still sent to the (hopefully written to disk) logs. If
a user (or distro) builds with this feature, I would think centered and
scaled for ease of scanning would be highest priority.

I don't think there is a 'safe' part of the framebuffer real estate
where the QR could be written for all scenarios. Best to make it easy
to scan.

thx,

Jason.


\
 
 \ /
  Last update: 2014-04-07 17:41    [W:0.062 / U:1.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site