On Sat 2019-04-13 09:22:05, Alastair D'Silva wrote: > > -----Original Message----- > > From: Petr Mladek <pmla...@suse.com> > > Sent: Friday, 12 April 2019 11:48 PM > > To: Alastair D'Silva <alast...@au1.ibm.com> > > Cc: alast...@d-silva.org; Jani Nikula <jani.nik...@linux.intel.com>; > Joonas > > Lahtinen <joonas.lahti...@linux.intel.com>; Rodrigo Vivi > > <rodrigo.v...@intel.com>; David Airlie <airl...@linux.ie>; Daniel Vetter > > <dan...@ffwll.ch>; Karsten Keil <i...@linux-pingi.de>; Jassi Brar > > <jassisinghb...@gmail.com>; Tom Lendacky <thomas.lenda...@amd.com>; > > David S. Miller <da...@davemloft.net>; Jose Abreu > > <jose.ab...@synopsys.com>; Kalle Valo <kv...@codeaurora.org>; > > Stanislaw Gruszka <sgrus...@redhat.com>; Benson Leung > > <ble...@chromium.org>; Enric Balletbo i Serra > > <enric.balle...@collabora.com>; James E.J. Bottomley > > <j...@linux.ibm.com>; Martin K. Petersen <martin.peter...@oracle.com>; > > Greg Kroah-Hartman <gre...@linuxfoundation.org>; Alexander Viro > > <v...@zeniv.linux.org.uk>; Sergey Senozhatsky > > <sergey.senozhat...@gmail.com>; Steven Rostedt <rost...@goodmis.org>; > > Andrew Morton <a...@linux-foundation.org>; intel- > > g...@lists.freedesktop.org; dri-de...@lists.freedesktop.org; linux- > > ker...@vger.kernel.org; net...@vger.kernel.org; > > ath...@lists.infradead.org; linux-wirel...@vger.kernel.org; linux- > > s...@vger.kernel.org; linux-fb...@vger.kernel.org; > > de...@driverdev.osuosl.org; linux-fsde...@vger.kernel.org > > Subject: Re: [PATCH 1/4] lib/hexdump.c: Allow 64 bytes per line > > > > On Wed 2019-04-10 13:17:17, Alastair D'Silva wrote: > > > From: Alastair D'Silva <alast...@d-silva.org> > > > > > > With modern high resolution screens, we can display more data, which > > > makes life a bit easier when debugging. > > > > I have quite some doubts about this feature. > > > > We are talking about more than 256 characters per-line. I wonder if such a > > long line is really easier to read for a human. > > It's basically 2 separate panes of information side by side, the hexdump and > the ASCII version. > > I'm using this myself when dealing with the pmem labels, and it works quite > nicely.
I am sure that it works for you. But I do not believe that it would be useful in general. > > I am not expert but there is a reason why the standard is 80 characters > per- > > line. I guess that anything above 100 characters is questionable. > > https://en.wikipedia.org/wiki/Line_length > > somehow confirms that. > > > > Second, if we take 8 pixels per-character. Then we need > > 2048 to show the 256 characters. It is more than HD. > > IMHO, there is still huge number of people that even do not have HD > display, > > especially on a notebook. > > The intent is to make debugging easier when dealing with large chunks of > binary data. I don't expect end users to see this output. How is it supposed to be used then? Only by your temporary patches? Best Regards, Petr _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
