crosstool-ng/config/arch/xtensa.in.2

choice
    prompt "Target Architecture Variant"
    default ARCH_xtensa_fsf

config XTENSA_CUSTOM
    bool "Custom Xtensa processor configuration"
    select TARGET_USE_OVERLAY

config ARCH_xtensa_fsf
    bool "fsf - Default configuration"

endchoice
xtensa: add support for the configurable Xtensa architecture. The Xtensa processor architecture is a configurable, extensible, and synthesizable 32-bit RISC processor core. Processor and SOC vendors can select from various processor options and even create customized instructions in addition to a base ISA to tailor the processor for a particular application. Because of the configurability, the build process requires one additional step for gcc, binutils, and gdb to update the default configuration. These configurations are packed into an 'overlay' tar image, and are simply untarred on top of the default configuration during the build. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> 2013-07-24 22:10:47 +00:00			`choice`
Whitespace: We don't use tabs in shell or kconfig files We indent by multiples of 4. This change cleans up whitespace in offending files. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com> 2015-12-08 17:09:49 +00:00			`prompt "Target Architecture Variant"`
			`default ARCH_xtensa_fsf`

xtensa: add support for the configurable Xtensa architecture. The Xtensa processor architecture is a configurable, extensible, and synthesizable 32-bit RISC processor core. Processor and SOC vendors can select from various processor options and even create customized instructions in addition to a base ISA to tailor the processor for a particular application. Because of the configurability, the build process requires one additional step for gcc, binutils, and gdb to update the default configuration. These configurations are packed into an 'overlay' tar image, and are simply untarred on top of the default configuration during the build. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> 2013-07-24 22:10:47 +00:00			`config XTENSA_CUSTOM`
Whitespace: We don't use tabs in shell or kconfig files We indent by multiples of 4. This change cleans up whitespace in offending files. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com> 2015-12-08 17:09:49 +00:00			`bool "Custom Xtensa processor configuration"`
Building packages using the new framework (fails at building GMP off the VCS because it needs to run bootstrap scripts) Signed-off-by: Alexey Neyman <stilor@att.net> 2017-06-26 05:54:29 +00:00			`select TARGET_USE_OVERLAY`
xtensa: add support for the configurable Xtensa architecture. The Xtensa processor architecture is a configurable, extensible, and synthesizable 32-bit RISC processor core. Processor and SOC vendors can select from various processor options and even create customized instructions in addition to a base ISA to tailor the processor for a particular application. Because of the configurability, the build process requires one additional step for gcc, binutils, and gdb to update the default configuration. These configurations are packed into an 'overlay' tar image, and are simply untarred on top of the default configuration during the build. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> 2013-07-24 22:10:47 +00:00
			`config ARCH_xtensa_fsf`
Whitespace: We don't use tabs in shell or kconfig files We indent by multiples of 4. This change cleans up whitespace in offending files. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com> 2015-12-08 17:09:49 +00:00			`bool "fsf - Default configuration"`
xtensa: add support for the configurable Xtensa architecture. The Xtensa processor architecture is a configurable, extensible, and synthesizable 32-bit RISC processor core. Processor and SOC vendors can select from various processor options and even create customized instructions in addition to a base ISA to tailor the processor for a particular application. Because of the configurability, the build process requires one additional step for gcc, binutils, and gdb to update the default configuration. These configurations are packed into an 'overlay' tar image, and are simply untarred on top of the default configuration during the build. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> 2013-07-24 22:10:47 +00:00
			`endchoice`