On Mon, 2014-05-12 at 12:15 -0400, Jason Cooper wrote: > On Sun, May 11, 2014 at 08:52:12PM +0300, Teodora Băluţă wrote: > > On Sun, May 11, 2014 at 8:18 PM, Levente Kurusa wrote: > > > On Sun, May 11, 2014 at 06:37:47PM +0200, Laurent Pinchart wrote: > > >> On Sunday 11 May 2014 18:29:18 Levente Kurusa wrote: > > >> > On Sun, May 11, 2014 at 08:57:01AM -0700, Sarah A Sharp wrote: > > >> > > On Sat, May 10, 2014 at 9:14 PM, Jason Cooper wrote: > > >> > > > All, > > >> > > > > > >> > > > I recently came across a patch series attempting to implement encoding > > >> > > > kernel oops into a QR code [1]. The QR code is then dumped to the > > >> > > > > > >> > > > framebuffer. The QR code is a URL of the form: > > >> > > > https://oops.kernel.org/?qr= > > >> > > > > > >> > > > This proposal is interesting because it fundamentally changes the way > > >> > > > users report bugs to the kernel community. First and foremost, it makes > > >> > > > it much easier. > > >> > > > > > >> > > > 1) oops occurs > > >> > > > 2) user pulls out phone, scans QR code > > >> > > > - at this point, the oops is recorded on the server. Nothing more > > >> > > > is required of the user. > > >> > > > >> > To be precise, most scanners don't automatically open the links > > >> > found in QR codes and hence a tap/click from the user is required. :-) > > > > That's correct, you still need a click, so maybe a special Android app > > could do the work so you don't need to turn the compressed oops into > > base64. > > I'd like the URL to be valid (meaning base64 the compressed data) so > that we can get the data to the kernel.org server as easily as possible. > Making the app a requirement for reporting is too onerous for > non-developers. I see no reason we can't link to (Open in/Install) it > on the webform though. > > I see your app as a great tool for people developing the kernel or > curious about what happened, but there will be a significant number of > users who don't develop (possibly anything) who won't go to the effort > to install an app just to help us out. Knowing how many of those folks > are affected by the bug is, imho, a very important data point when > triaging bugs. With smart Internet-connected TVs and monitors, can't we embed the app in the monitor itself, and have it upload the oops? Why use a camera...? :) -- dwmw2