From: "Murtaza, Alexandru" <alexandru.murtaza@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Baluta, Teodora" <teodora.baluta@intel.com>
Subject: RE: [RFC][PATCH] Oops messages transfer using QR codes
Date: Wed, 4 Nov 2015 13:40:15 +0000 [thread overview]
Message-ID: <70CA577BF349C64188E42B39029FE9AD135AB5A1@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <5633E9A9.3000605@infradead.org>
Thanks for catching that typo!
________________________________________
From: Randy Dunlap [rdunlap@infradead.org]
Sent: Saturday, October 31, 2015 12:05 AM
To: Murtaza, Alexandru; linux-kernel@vger.kernel.org
Cc: Baluta, Teodora; levex@linux.com; Hohndel, Dirk; Anvin, H Peter
Subject: Re: [RFC][PATCH] Oops messages transfer using QR codes
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
next prev parent reply other threads:[~2015-11-04 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 15:03 [RFC][PATCH] Oops messages transfer using QR codes Murtaza Alexandru
2015-10-30 22:05 ` Randy Dunlap
2015-11-04 13:40 ` Murtaza, Alexandru [this message]
2015-11-02 18:56 ` Laura Abbott
2015-11-04 11:32 ` Murtaza, Alexandru
2015-11-10 0:27 ` Laura Abbott
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=70CA577BF349C64188E42B39029FE9AD135AB5A1@IRSMSX102.ger.corp.intel.com \
--to=alexandru.murtaza@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=teodora.baluta@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).