mirror of
https://github.com/torvalds/linux.git
synced 2024-11-16 17:12:06 +00:00
dc52ddc0e6
This patch implements a new freezer subsystem in the control groups framework. It provides a way to stop and resume execution of all tasks in a cgroup by writing in the cgroup filesystem. The freezer subsystem in the container filesystem defines a file named freezer.state. Writing "FROZEN" to the state file will freeze all tasks in the cgroup. Subsequently writing "RUNNING" will unfreeze the tasks in the cgroup. Reading will return the current state. * Examples of usage : # mkdir /containers/freezer # mount -t cgroup -ofreezer freezer /containers # mkdir /containers/0 # echo $some_pid > /containers/0/tasks to get status of the freezer subsystem : # cat /containers/0/freezer.state RUNNING to freeze all tasks in the container : # echo FROZEN > /containers/0/freezer.state # cat /containers/0/freezer.state FREEZING # cat /containers/0/freezer.state FROZEN to unfreeze all tasks in the container : # echo RUNNING > /containers/0/freezer.state # cat /containers/0/freezer.state RUNNING This is the basic mechanism which should do the right thing for user space task in a simple scenario. It's important to note that freezing can be incomplete. In that case we return EBUSY. This means that some tasks in the cgroup are busy doing something that prevents us from completely freezing the cgroup at this time. After EBUSY, the cgroup will remain partially frozen -- reflected by freezer.state reporting "FREEZING" when read. The state will remain "FREEZING" until one of these things happens: 1) Userspace cancels the freezing operation by writing "RUNNING" to the freezer.state file 2) Userspace retries the freezing operation by writing "FROZEN" to the freezer.state file (writing "FREEZING" is not legal and returns EIO) 3) The tasks that blocked the cgroup from entering the "FROZEN" state disappear from the cgroup's set of tasks. [akpm@linux-foundation.org: coding-style fixes] [akpm@linux-foundation.org: export thaw_process] Signed-off-by: Cedric Le Goater <clg@fr.ibm.com> Signed-off-by: Matt Helsley <matthltc@us.ibm.com> Acked-by: Serge E. Hallyn <serue@us.ibm.com> Tested-by: Matt Helsley <matthltc@us.ibm.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
625 lines
19 KiB
Plaintext
625 lines
19 KiB
Plaintext
#
|
|
# For a description of the syntax of this configuration file,
|
|
# see Documentation/kbuild/kconfig-language.txt.
|
|
#
|
|
config M68K
|
|
bool
|
|
default y
|
|
select HAVE_AOUT
|
|
select HAVE_IDE
|
|
|
|
config MMU
|
|
bool
|
|
default y
|
|
|
|
config RWSEM_GENERIC_SPINLOCK
|
|
bool
|
|
default y
|
|
|
|
config RWSEM_XCHGADD_ALGORITHM
|
|
bool
|
|
|
|
config ARCH_HAS_ILOG2_U32
|
|
bool
|
|
default n
|
|
|
|
config ARCH_HAS_ILOG2_U64
|
|
bool
|
|
default n
|
|
|
|
config GENERIC_HWEIGHT
|
|
bool
|
|
default y
|
|
|
|
config GENERIC_CALIBRATE_DELAY
|
|
bool
|
|
default y
|
|
|
|
config TIME_LOW_RES
|
|
bool
|
|
default y
|
|
|
|
config GENERIC_IOMAP
|
|
bool
|
|
default y
|
|
|
|
config ARCH_MAY_HAVE_PC_FDC
|
|
bool
|
|
depends on BROKEN && (Q40 || SUN3X)
|
|
default y
|
|
|
|
config NO_IOPORT
|
|
def_bool y
|
|
|
|
config NO_DMA
|
|
def_bool SUN3
|
|
|
|
config HZ
|
|
int
|
|
default 100
|
|
|
|
mainmenu "Linux/68k Kernel Configuration"
|
|
|
|
source "init/Kconfig"
|
|
|
|
source "kernel/Kconfig.freezer"
|
|
|
|
menu "Platform dependent setup"
|
|
|
|
config EISA
|
|
bool
|
|
---help---
|
|
The Extended Industry Standard Architecture (EISA) bus was
|
|
developed as an open alternative to the IBM MicroChannel bus.
|
|
|
|
The EISA bus provided some of the features of the IBM MicroChannel
|
|
bus while maintaining backward compatibility with cards made for
|
|
the older ISA bus. The EISA bus saw limited use between 1988 and
|
|
1995 when it was made obsolete by the PCI bus.
|
|
|
|
Say Y here if you are building a kernel for an EISA-based machine.
|
|
|
|
Otherwise, say N.
|
|
|
|
config MCA
|
|
bool
|
|
help
|
|
MicroChannel Architecture is found in some IBM PS/2 machines and
|
|
laptops. It is a bus system similar to PCI or ISA. See
|
|
<file:Documentation/mca.txt> (and especially the web page given
|
|
there) before attempting to build an MCA bus kernel.
|
|
|
|
config PCMCIA
|
|
tristate
|
|
---help---
|
|
Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
|
|
computer. These are credit-card size devices such as network cards,
|
|
modems or hard drives often used with laptops computers. There are
|
|
actually two varieties of these cards: the older 16 bit PCMCIA cards
|
|
and the newer 32 bit CardBus cards. If you want to use CardBus
|
|
cards, you need to say Y here and also to "CardBus support" below.
|
|
|
|
To use your PC-cards, you will need supporting software from David
|
|
Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
|
|
for location). Please also read the PCMCIA-HOWTO, available from
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
To compile this driver as modules, choose M here: the
|
|
modules will be called pcmcia_core and ds.
|
|
|
|
config AMIGA
|
|
bool "Amiga support"
|
|
select MMU_MOTOROLA if MMU
|
|
help
|
|
This option enables support for the Amiga series of computers. If
|
|
you plan to use this kernel on an Amiga, say Y here and browse the
|
|
material available in <file:Documentation/m68k>; otherwise say N.
|
|
|
|
config ATARI
|
|
bool "Atari support"
|
|
select MMU_MOTOROLA if MMU
|
|
help
|
|
This option enables support for the 68000-based Atari series of
|
|
computers (including the TT, Falcon and Medusa). If you plan to use
|
|
this kernel on an Atari, say Y here and browse the material
|
|
available in <file:Documentation/m68k>; otherwise say N.
|
|
|
|
config MAC
|
|
bool "Macintosh support"
|
|
select MMU_MOTOROLA if MMU
|
|
help
|
|
This option enables support for the Apple Macintosh series of
|
|
computers (yes, there is experimental support now, at least for part
|
|
of the series).
|
|
|
|
Say N unless you're willing to code the remaining necessary support.
|
|
;)
|
|
|
|
config NUBUS
|
|
bool
|
|
depends on MAC
|
|
default y
|
|
|
|
config M68K_L2_CACHE
|
|
bool
|
|
depends on MAC
|
|
default y
|
|
|
|
config APOLLO
|
|
bool "Apollo support"
|
|
select MMU_MOTOROLA if MMU
|
|
help
|
|
Say Y here if you want to run Linux on an MC680x0-based Apollo
|
|
Domain workstation such as the DN3500.
|
|
|
|
config VME
|
|
bool "VME (Motorola and BVM) support"
|
|
select MMU_MOTOROLA if MMU
|
|
help
|
|
Say Y here if you want to build a kernel for a 680x0 based VME
|
|
board. Boards currently supported include Motorola boards MVME147,
|
|
MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
|
|
BVME6000 boards from BVM Ltd are also supported.
|
|
|
|
config MVME147
|
|
bool "MVME147 support"
|
|
depends on VME
|
|
help
|
|
Say Y to include support for early Motorola VME boards. This will
|
|
build a kernel which can run on MVME147 single-board computers. If
|
|
you select this option you will have to select the appropriate
|
|
drivers for SCSI, Ethernet and serial ports later on.
|
|
|
|
config MVME16x
|
|
bool "MVME162, 166 and 167 support"
|
|
depends on VME
|
|
help
|
|
Say Y to include support for Motorola VME boards. This will build a
|
|
kernel which can run on MVME162, MVME166, MVME167, MVME172, and
|
|
MVME177 boards. If you select this option you will have to select
|
|
the appropriate drivers for SCSI, Ethernet and serial ports later
|
|
on.
|
|
|
|
config BVME6000
|
|
bool "BVME4000 and BVME6000 support"
|
|
depends on VME
|
|
help
|
|
Say Y to include support for VME boards from BVM Ltd. This will
|
|
build a kernel which can run on BVME4000 and BVME6000 boards. If
|
|
you select this option you will have to select the appropriate
|
|
drivers for SCSI, Ethernet and serial ports later on.
|
|
|
|
config HP300
|
|
bool "HP9000/300 and HP9000/400 support"
|
|
select MMU_MOTOROLA if MMU
|
|
help
|
|
This option enables support for the HP9000/300 and HP9000/400 series
|
|
of workstations. Support for these machines is still somewhat
|
|
experimental. If you plan to try to use the kernel on such a machine
|
|
say Y here.
|
|
Everybody else says N.
|
|
|
|
config DIO
|
|
bool "DIO bus support"
|
|
depends on HP300
|
|
default y
|
|
help
|
|
Say Y here to enable support for the "DIO" expansion bus used in
|
|
HP300 machines. If you are using such a system you almost certainly
|
|
want this.
|
|
|
|
config SUN3X
|
|
bool "Sun3x support"
|
|
select MMU_MOTOROLA if MMU
|
|
select M68030
|
|
help
|
|
This option enables support for the Sun 3x series of workstations.
|
|
Be warned that this support is very experimental.
|
|
Note that Sun 3x kernels are not compatible with Sun 3 hardware.
|
|
General Linux information on the Sun 3x series (now discontinued)
|
|
is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
|
|
|
|
If you don't want to compile a kernel for a Sun 3x, say N.
|
|
|
|
config Q40
|
|
bool "Q40/Q60 support"
|
|
select MMU_MOTOROLA if MMU
|
|
help
|
|
The Q40 is a Motorola 68040-based successor to the Sinclair QL
|
|
manufactured in Germany. There is an official Q40 home page at
|
|
<http://www.q40.de/>. This option enables support for the Q40 and
|
|
Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
|
|
emulation.
|
|
|
|
config SUN3
|
|
bool "Sun3 support"
|
|
depends on !MMU_MOTOROLA
|
|
select MMU_SUN3 if MMU
|
|
select M68020
|
|
help
|
|
This option enables support for the Sun 3 series of workstations
|
|
(3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
|
|
that all other hardware types must be disabled, as Sun 3 kernels
|
|
are incompatible with all other m68k targets (including Sun 3x!).
|
|
|
|
If you don't want to compile a kernel exclusively for a Sun 3, say N.
|
|
|
|
comment "Processor type"
|
|
|
|
config M68020
|
|
bool "68020 support"
|
|
help
|
|
If you anticipate running this kernel on a computer with a MC68020
|
|
processor, say Y. Otherwise, say N. Note that the 68020 requires a
|
|
68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
|
|
Sun 3, which provides its own version.
|
|
|
|
config M68030
|
|
bool "68030 support"
|
|
depends on !MMU_SUN3
|
|
help
|
|
If you anticipate running this kernel on a computer with a MC68030
|
|
processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
|
|
work, as it does not include an MMU (Memory Management Unit).
|
|
|
|
config M68040
|
|
bool "68040 support"
|
|
depends on !MMU_SUN3
|
|
help
|
|
If you anticipate running this kernel on a computer with a MC68LC040
|
|
or MC68040 processor, say Y. Otherwise, say N. Note that an
|
|
MC68EC040 will not work, as it does not include an MMU (Memory
|
|
Management Unit).
|
|
|
|
config M68060
|
|
bool "68060 support"
|
|
depends on !MMU_SUN3
|
|
help
|
|
If you anticipate running this kernel on a computer with a MC68060
|
|
processor, say Y. Otherwise, say N.
|
|
|
|
config MMU_MOTOROLA
|
|
bool
|
|
depends on MMU && !MMU_SUN3
|
|
|
|
config MMU_SUN3
|
|
bool
|
|
depends on MMU && !MMU_MOTOROLA
|
|
|
|
config M68KFPU_EMU
|
|
bool "Math emulation support (EXPERIMENTAL)"
|
|
depends on EXPERIMENTAL
|
|
help
|
|
At some point in the future, this will cause floating-point math
|
|
instructions to be emulated by the kernel on machines that lack a
|
|
floating-point math coprocessor. Thrill-seekers and chronically
|
|
sleep-deprived psychotic hacker types can say Y now, everyone else
|
|
should probably wait a while.
|
|
|
|
config M68KFPU_EMU_EXTRAPREC
|
|
bool "Math emulation extra precision"
|
|
depends on M68KFPU_EMU
|
|
help
|
|
The fpu uses normally a few bit more during calculations for
|
|
correct rounding, the emulator can (often) do the same but this
|
|
extra calculation can cost quite some time, so you can disable
|
|
it here. The emulator will then "only" calculate with a 64 bit
|
|
mantissa and round slightly incorrect, what is more then enough
|
|
for normal usage.
|
|
|
|
config M68KFPU_EMU_ONLY
|
|
bool "Math emulation only kernel"
|
|
depends on M68KFPU_EMU
|
|
help
|
|
This option prevents any floating-point instructions from being
|
|
compiled into the kernel, thereby the kernel doesn't save any
|
|
floating point context anymore during task switches, so this
|
|
kernel will only be usable on machines without a floating-point
|
|
math coprocessor. This makes the kernel a bit faster as no tests
|
|
needs to be executed whether a floating-point instruction in the
|
|
kernel should be executed or not.
|
|
|
|
config ADVANCED
|
|
bool "Advanced configuration options"
|
|
---help---
|
|
This gives you access to some advanced options for the CPU. The
|
|
defaults should be fine for most users, but these options may make
|
|
it possible for you to improve performance somewhat if you know what
|
|
you are doing.
|
|
|
|
Note that the answer to this question won't directly affect the
|
|
kernel: saying N will just cause the configurator to skip all
|
|
the questions about these options.
|
|
|
|
Most users should say N to this question.
|
|
|
|
config RMW_INSNS
|
|
bool "Use read-modify-write instructions"
|
|
depends on ADVANCED
|
|
---help---
|
|
This allows to use certain instructions that work with indivisible
|
|
read-modify-write bus cycles. While this is faster than the
|
|
workaround of disabling interrupts, it can conflict with DMA
|
|
( = direct memory access) on many Amiga systems, and it is also said
|
|
to destabilize other machines. It is very likely that this will
|
|
cause serious problems on any Amiga or Atari Medusa if set. The only
|
|
configuration where it should work are 68030-based Ataris, where it
|
|
apparently improves performance. But you've been warned! Unless you
|
|
really know what you are doing, say N. Try Y only if you're quite
|
|
adventurous.
|
|
|
|
config SINGLE_MEMORY_CHUNK
|
|
bool "Use one physical chunk of memory only" if ADVANCED && !SUN3
|
|
default y if SUN3
|
|
select NEED_MULTIPLE_NODES
|
|
help
|
|
Ignore all but the first contiguous chunk of physical memory for VM
|
|
purposes. This will save a few bytes kernel size and may speed up
|
|
some operations. Say N if not sure.
|
|
|
|
config 060_WRITETHROUGH
|
|
bool "Use write-through caching for 68060 supervisor accesses"
|
|
depends on ADVANCED && M68060
|
|
---help---
|
|
The 68060 generally uses copyback caching of recently accessed data.
|
|
Copyback caching means that memory writes will be held in an on-chip
|
|
cache and only written back to memory some time later. Saying Y
|
|
here will force supervisor (kernel) accesses to use writethrough
|
|
caching. Writethrough caching means that data is written to memory
|
|
straight away, so that cache and memory data always agree.
|
|
Writethrough caching is less efficient, but is needed for some
|
|
drivers on 68060 based systems where the 68060 bus snooping signal
|
|
is hardwired on. The 53c710 SCSI driver is known to suffer from
|
|
this problem.
|
|
|
|
config ARCH_DISCONTIGMEM_ENABLE
|
|
def_bool !SINGLE_MEMORY_CHUNK
|
|
|
|
config NODES_SHIFT
|
|
int
|
|
default "3"
|
|
depends on !SINGLE_MEMORY_CHUNK
|
|
|
|
source "mm/Kconfig"
|
|
|
|
endmenu
|
|
|
|
menu "General setup"
|
|
|
|
source "fs/Kconfig.binfmt"
|
|
|
|
config ZORRO
|
|
bool "Amiga Zorro (AutoConfig) bus support"
|
|
depends on AMIGA
|
|
help
|
|
This enables support for the Zorro bus in the Amiga. If you have
|
|
expansion cards in your Amiga that conform to the Amiga
|
|
AutoConfig(tm) specification, say Y, otherwise N. Note that even
|
|
expansion cards that do not fit in the Zorro slots but fit in e.g.
|
|
the CPU slot may fall in this category, so you have to say Y to let
|
|
Linux use these.
|
|
|
|
config AMIGA_PCMCIA
|
|
bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
|
|
depends on AMIGA && EXPERIMENTAL
|
|
help
|
|
Include support in the kernel for pcmcia on Amiga 1200 and Amiga
|
|
600. If you intend to use pcmcia cards say Y; otherwise say N.
|
|
|
|
config STRAM_PROC
|
|
bool "ST-RAM statistics in /proc"
|
|
depends on ATARI
|
|
help
|
|
Say Y here to report ST-RAM usage statistics in /proc/stram.
|
|
|
|
config HEARTBEAT
|
|
bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
|
|
default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
|
|
help
|
|
Use the power-on LED on your machine as a load meter. The exact
|
|
behavior is platform-dependent, but normally the flash frequency is
|
|
a hyperbolic function of the 5-minute load average.
|
|
|
|
# We have a dedicated heartbeat LED. :-)
|
|
config PROC_HARDWARE
|
|
bool "/proc/hardware support"
|
|
help
|
|
Say Y here to support the /proc/hardware file, which gives you
|
|
access to information about the machine you're running on,
|
|
including the model, CPU, MMU, clock speed, BogoMIPS rating,
|
|
and memory size.
|
|
|
|
config ISA
|
|
bool
|
|
depends on Q40 || AMIGA_PCMCIA || GG2
|
|
default y
|
|
help
|
|
Find out whether you have ISA slots on your motherboard. ISA is the
|
|
name of a bus system, i.e. the way the CPU talks to the other stuff
|
|
inside your box. Other bus systems are PCI, EISA, MicroChannel
|
|
(MCA) or VESA. ISA is an older system, now being displaced by PCI;
|
|
newer boards don't support it. If you have ISA, say Y, otherwise N.
|
|
|
|
config GENERIC_ISA_DMA
|
|
bool
|
|
depends on Q40 || AMIGA_PCMCIA || GG2
|
|
default y
|
|
|
|
config ZONE_DMA
|
|
bool
|
|
default y
|
|
|
|
source "drivers/pci/Kconfig"
|
|
|
|
source "drivers/zorro/Kconfig"
|
|
|
|
endmenu
|
|
|
|
source "net/Kconfig"
|
|
|
|
source "drivers/Kconfig"
|
|
|
|
menu "Character devices"
|
|
|
|
config ATARI_MFPSER
|
|
tristate "Atari MFP serial support"
|
|
depends on ATARI
|
|
---help---
|
|
If you like to use the MFP serial ports ("Modem1", "Serial1") under
|
|
Linux, say Y. The driver equally supports all kinds of MFP serial
|
|
ports and automatically detects whether Serial1 is available.
|
|
|
|
To compile this driver as a module, choose M here.
|
|
|
|
Note for Falcon users: You also have an MFP port, it's just not
|
|
wired to the outside... But you could use the port under Linux.
|
|
|
|
config ATARI_MIDI
|
|
tristate "Atari MIDI serial support"
|
|
depends on ATARI
|
|
help
|
|
If you want to use your Atari's MIDI port in Linux, say Y.
|
|
|
|
To compile this driver as a module, choose M here.
|
|
|
|
config ATARI_DSP56K
|
|
tristate "Atari DSP56k support (EXPERIMENTAL)"
|
|
depends on ATARI && EXPERIMENTAL
|
|
help
|
|
If you want to be able to use the DSP56001 in Falcons, say Y. This
|
|
driver is still experimental, and if you don't know what it is, or
|
|
if you don't have this processor, just say N.
|
|
|
|
To compile this driver as a module, choose M here.
|
|
|
|
config AMIGA_BUILTIN_SERIAL
|
|
tristate "Amiga builtin serial support"
|
|
depends on AMIGA
|
|
help
|
|
If you want to use your Amiga's built-in serial port in Linux,
|
|
answer Y.
|
|
|
|
To compile this driver as a module, choose M here.
|
|
|
|
config MULTIFACE_III_TTY
|
|
tristate "Multiface Card III serial support"
|
|
depends on AMIGA
|
|
help
|
|
If you want to use a Multiface III card's serial port in Linux,
|
|
answer Y.
|
|
|
|
To compile this driver as a module, choose M here.
|
|
|
|
config GVPIOEXT
|
|
tristate "GVP IO-Extender support"
|
|
depends on PARPORT=n && ZORRO
|
|
help
|
|
If you want to use a GVP IO-Extender serial card in Linux, say Y.
|
|
Otherwise, say N.
|
|
|
|
config GVPIOEXT_LP
|
|
tristate "GVP IO-Extender parallel printer support"
|
|
depends on GVPIOEXT
|
|
help
|
|
Say Y to enable driving a printer from the parallel port on your
|
|
GVP IO-Extender card, N otherwise.
|
|
|
|
config GVPIOEXT_PLIP
|
|
tristate "GVP IO-Extender PLIP support"
|
|
depends on GVPIOEXT
|
|
help
|
|
Say Y to enable doing IP over the parallel port on your GVP
|
|
IO-Extender card, N otherwise.
|
|
|
|
config MAC_SCC
|
|
tristate "Macintosh serial support"
|
|
depends on MAC
|
|
|
|
config MAC_HID
|
|
bool
|
|
depends on INPUT_ADBHID
|
|
default y
|
|
|
|
config HPDCA
|
|
tristate "HP DCA serial support"
|
|
depends on DIO && SERIAL_8250
|
|
help
|
|
If you want to use the internal "DCA" serial ports on an HP300
|
|
machine, say Y here.
|
|
|
|
config HPAPCI
|
|
tristate "HP APCI serial support"
|
|
depends on HP300 && SERIAL_8250 && EXPERIMENTAL
|
|
help
|
|
If you want to use the internal "APCI" serial ports on an HP400
|
|
machine, say Y here.
|
|
|
|
config MVME147_SCC
|
|
bool "SCC support for MVME147 serial ports"
|
|
depends on MVME147
|
|
help
|
|
This is the driver for the serial ports on the Motorola MVME147
|
|
boards. Everyone using one of these boards should say Y here.
|
|
|
|
config SERIAL167
|
|
bool "CD2401 support for MVME166/7 serial ports"
|
|
depends on MVME16x
|
|
help
|
|
This is the driver for the serial ports on the Motorola MVME166,
|
|
167, and 172 boards. Everyone using one of these boards should say
|
|
Y here.
|
|
|
|
config MVME162_SCC
|
|
bool "SCC support for MVME162 serial ports"
|
|
depends on MVME16x
|
|
help
|
|
This is the driver for the serial ports on the Motorola MVME162 and
|
|
172 boards. Everyone using one of these boards should say Y here.
|
|
|
|
config BVME6000_SCC
|
|
bool "SCC support for BVME6000 serial ports"
|
|
depends on BVME6000
|
|
help
|
|
This is the driver for the serial ports on the BVME4000 and BVME6000
|
|
boards from BVM Ltd. Everyone using one of these boards should say
|
|
Y here.
|
|
|
|
config DN_SERIAL
|
|
bool "Support for DN serial port (dummy)"
|
|
depends on APOLLO
|
|
|
|
config SERIAL_CONSOLE
|
|
bool "Support for serial port console"
|
|
depends on (AMIGA || ATARI || MAC || SUN3 || SUN3X || VME || APOLLO) && (ATARI_MFPSER=y || ATARI_MIDI=y || MAC_SCC=y || AMIGA_BUILTIN_SERIAL=y || GVPIOEXT=y || MULTIFACE_III_TTY=y || SERIAL=y || MVME147_SCC || SERIAL167 || MVME162_SCC || BVME6000_SCC || DN_SERIAL)
|
|
---help---
|
|
If you say Y here, it will be possible to use a serial port as the
|
|
system console (the system console is the device which receives all
|
|
kernel messages and warnings and which allows logins in single user
|
|
mode). This could be useful if some terminal or printer is connected
|
|
to that serial port.
|
|
|
|
Even if you say Y here, the currently visible virtual console
|
|
(/dev/tty0) will still be used as the system console by default, but
|
|
you can alter that using a kernel command line option such as
|
|
"console=ttyS1". (Try "man bootparam" or see the documentation of
|
|
your boot loader (lilo or loadlin) about how to pass options to the
|
|
kernel at boot time.)
|
|
|
|
If you don't have a VGA card installed and you say Y here, the
|
|
kernel will automatically use the first serial line, /dev/ttyS0, as
|
|
system console.
|
|
|
|
If unsure, say N.
|
|
|
|
endmenu
|
|
|
|
source "fs/Kconfig"
|
|
|
|
source "arch/m68k/Kconfig.debug"
|
|
|
|
source "security/Kconfig"
|
|
|
|
source "crypto/Kconfig"
|
|
|
|
source "lib/Kconfig"
|