CHROMIUM: Revert "printk/console: Allow to disable console output by using console="" or console=null"
This reverts commit 0181a55027a0ff6f4cccccaae1b0e48ebd0c066f.
The reverted patch "handles" blank "console=" command line parameters
by explicitly ignoring them. This is different to the previous behavior,
where such an argument disabled a default console (for example a
console specified via devicetree).
Chrome OS uses the empty "console=" kernel command line parameter in
production images to explicitly disable the default console. With the
reverted patch in place, this no longer works. This has severe performance
impacts, especially in systems where the console is on a serial interface.
There may be other undesirable side effects - on at least one platform,
it was observed that dm-verity no longer works with the reverted patch
in place, for unknown reasons.
BUG=b:172215283
TEST=Verify that console is disabled in production images, and that dm-verity works
1 file changed
