diff options
| author | Heiko Carstens <heiko.carstens@de.ibm.com> | 2012-05-09 16:27:38 +0200 |
|---|---|---|
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2012-05-16 14:42:40 +0200 |
| commit | 58770be6cc5901bfbb908d9c6d8ca679fc55df26 (patch) | |
| tree | f83ef3786225009d0cf59ac34b698c0a8f4ccac4 /arch/s390/Kconfig | |
| parent | c15787a7c3f702c4240708fb8e63abce1bfe1136 (diff) | |
s390/ipl: remove builtin tape ipl code
Remove the builtin tape ipl code. If somebody really wants to create a
tape which can be ipl'ed from, then this can be achieved by using zipl.
zipl can write an ipl record to a tape device and aftwards the kernel
image must be written to tape.
The steps are described in the "Linux on System z - Device Drivers,
Features, and Commands" book (SC33-8411).
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch/s390/Kconfig')
| -rw-r--r-- | arch/s390/Kconfig | 27 |
1 files changed, 0 insertions, 27 deletions
diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig index eeaed9be5fd..354c0fe72ae 100644 --- a/arch/s390/Kconfig +++ b/arch/s390/Kconfig @@ -406,33 +406,6 @@ config CHSC_SCH comment "Misc" -config IPL - def_bool y - prompt "Builtin IPL record support" - help - If you want to use the produced kernel to IPL directly from a - device, you have to merge a bootsector specific to the device - into the first bytes of the kernel. You will have to select the - IPL device. - -choice - prompt "IPL method generated into head.S" - depends on IPL - default IPL_VM - help - Select "tape" if you want to IPL the image from a Tape. - - Select "vm_reader" if you are running under VM/ESA and want - to IPL the image from the emulated card reader. - -config IPL_TAPE - bool "tape" - -config IPL_VM - bool "vm_reader" - -endchoice - source "fs/Kconfig.binfmt" config FORCE_MAX_ZONEORDER |