Messages in this thread | ![/](/images/icornerl.gif) | | Subject | Re: [RFC][PATCH] Oops messages transfer using QR codes | From | Randy Dunlap <> | Date | Fri, 30 Oct 2015 15:05:29 -0700 |
| |
On 10/30/15 08:03, Murtaza Alexandru wrote: > This patch is continued from this previous RFC: > https://lkml.org/lkml/2014/3/17/525 > > ---
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index ab76b99..822fe7d 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -15,6 +15,23 @@ config PRINTK_TIME > The behavior is also controlled by the kernel command line > parameter printk.time=1. See Documentation/kernel-parameters.txt > > +config QR_OOPS > + bool "Display QR barcode for Oops messages for debugging purposes" > + depends on PRINTK && FB > + select QRLIB > + select ZLIB_DEFLATE > + select ZLIB_INFLATE > + select FB_CFB_FILLRECT > + select REED_SOLOMON > + select REED_SOLOMON_ENC8 > + help > + Selecting this option makes printk() calls to accumulate > + the Oops messages in a buffer, compresses the message > + and prints the OR to the frame buffer device.
? QR
> + > + This is an experimental feature at the moment. > + > +
-- ~Randy
| ![\](/images/icornerr.gif) |