Re: [PATCH v7 15/15] RISC-V: Build Infastructure

From: Randy Dunlap
Date: Tue Aug 01 2017 - 11:28:08 EST


On 07/31/2017 06:00 PM, Palmer Dabbelt wrote:
> This patch contains all the build infastructure that actually enables
> the RISC-V port. This includes Makefiles, linker scripts, and Kconfig
> files. It also contains the only top-level change, which adds RISC-V to
> the list of architectures that need a sed run to produce the ARCH
> variable when building locally.
>
> Signed-off-by: Palmer Dabbelt <palmer@xxxxxxxxxxx>
> ---
>
> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> new file mode 100644
> index 000000000000..9b7d077f40af
> --- /dev/null
> +++ b/arch/riscv/Kconfig
> @@ -0,0 +1,275 @@
> +#
> +# For a description of the syntax of this configuration file,
> +# see Documentation/kbuild/kconfig-language.txt.
> +#

[]

drop the "default n" lines below:

> +config CMDLINE_BOOL
> + bool "Built-in kernel command line"
> + default n
> + help
> + For most platforms, it is firmware or second stage bootloader
> + that by default specifies the kernel command line options.
> + However, it might be necessary or advantageous to either override
> + the default kernel command line or add a few extra options to it.
> + For such cases, this option allows hardcoding command line options
> + directly into the kernel.
> +
> + For that, choose 'Y' here and fill in the extra boot parameters
> + in CONFIG_CMDLINE.
> +
> + The built-in options will be concatenated to the default command
> + line if CMDLINE_OVERRIDE is set to 'N'. Otherwise, the default
> + command line will be ignored and replaced by the built-in string.
> +
> +config CMDLINE
> + string "Built-in kernel command string"
> + depends on CMDLINE_BOOL
> + default ""
> + help
> + Supply command-line options at build time by entering them here.
> +
> +config CMDLINE_OVERRIDE
> + bool "Built-in command line overrides bootloader arguments"
> + default n
> + depends on CMDLINE_BOOL
> + help
> + Set this option to 'Y' to have the kernel ignore the bootloader
> + or firmware command line. Instead, the built-in command line
> + will be used exclusively.
> +
> + If you don't know what to do here, say N.



--
~Randy