[lkml]   [2019]   [Mar]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2 7/7] x86/boot: Support nocfg parameter for earlyprintk
On Thu, Mar 28, 2019 at 02:42:13PM +0100, Borislav Petkov wrote:
> On Thu, Mar 28, 2019 at 03:21:53PM +0200, Andy Shevchenko wrote:
> > If the connection to the target is done via serial interface and
> > firmware and / or bootloader already did necessary configuration.
> Again: how is the user supposed to know that?

How one knows that she is typing on keyboard right now and not on touch screen?
I really don't get this. User either knows this beforehand or doesn't care.
Maybe she needs to read documentation on hardware at some point?

> When a user sees "nocfg"'s
> documentation, how is the user supposed to decide whether she needs
> to supply nocfg or not?

The problem nocfg tries to solve is a hard coded default baud rate and
impossibility to know at this stage all parameters of the serial interface.

> Which exact setups will need to supply nocfg on the cmdline?

If it's _non-standard_ serial interface (by meaning of I/O accessors and port
addresses), user may consider to use this options in case the interface to
communicate with kernel is serial one and its configuration is done by other
means (firmware / bootloader / EFI / etc).

With Best Regards,
Andy Shevchenko

 \ /
  Last update: 2019-03-28 15:01    [W:0.168 / U:3.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site