ARM64: rockchip_cros_defconfig: Don't force the command line
authorDouglas Anderson <dianders@chromium.org>
Tue, 26 Apr 2016 17:53:17 +0000 (10:53 -0700)
committerCaesar Wang <wxt@rock-chips.com>
Wed, 27 Apr 2016 03:26:24 +0000 (11:26 +0800)
There's no reason to force the command line at this point.

Forcing the command like makes it pretty hard to switch between eMMC and
SD card boots because the old command line forced the root filesystem to
/dev/mmcblk0p3 vs. depthcharge automatically inserting the right UUID
based on where it found the kernel.

BUG=None
TEST=I see my command line now.

Change-Id: I5f76b60b9726aee2152c09fbd6460b2b973b0b20
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Caesar Wang <wxt@rock-chips.com>
arch/arm64/configs/rockchip_cros_defconfig

index dbd211e133507fc1479c5850c1caea28aa882e3f..c86f3d7eb3cfb675d972fb21b671854e5914d4ab 100644 (file)
@@ -54,7 +54,7 @@ CONFIG_SWP_EMULATION=y
 CONFIG_CP15_BARRIER_EMULATION=y
 CONFIG_SETEND_EMULATION=y
 CONFIG_CMDLINE="console=uart,mmio32,0xff1a0000 rootwait cros_debug cros_secure ro root=/dev/mmcblk0p3 init=/sbin/init kgdboc=ttyS2"
-CONFIG_CMDLINE_FORCE=y
+# CONFIG_CMDLINE_FORCE is not set
 # CONFIG_EFI is not set
 # CONFIG_COREDUMP is not set
 CONFIG_COMPAT=y