Re: [RFC] QR encoding for Oops messages

[David Lang]

On Tue, 1 Apr 2014, Jason Cooper wrote:

> > Now I guess we need to think how to make it work without a
> > framebuffer. I already suggested using the ASCII characters,
> > but seeing the resolution of this QR code for example (147x147),
> > made me realize that we can't shuffle that into a 80x25 textmode
> > display. Any ideas how to fix that or should we just simply depend
> > on a framebuffer being present?
>
> I think depending on the framebuffer being present (via kconfig) is
> sane.  Folks running old systems know what they're in for, like missing
> shiny new features. ;-)

First get it working and into acceptable form, but after that, take a look at 
the various ASCII-art tools out there. While the display may be limited to 
80x25, that's not a hard requirement (and I'd happily run systems with a smaller 
text console if this was an option), and then you can look at the possibility of 
using characters that represent more than one pixel per character. While this 
may not be able to render everything perfectly, remember that qr codes can 
include redundancy to correct for bad pixels, you may be able to get something 
working.

David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/