Kconfig 21 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679
  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see Documentation/kbuild/kconfig-language.txt.
  4. #
  5. config M68K
  6. bool
  7. default y
  8. config MMU
  9. bool
  10. default y
  11. config RWSEM_GENERIC_SPINLOCK
  12. bool
  13. default y
  14. config RWSEM_XCHGADD_ALGORITHM
  15. bool
  16. config ARCH_HAS_ILOG2_U32
  17. bool
  18. default n
  19. config ARCH_HAS_ILOG2_U64
  20. bool
  21. default n
  22. config GENERIC_HWEIGHT
  23. bool
  24. default y
  25. config GENERIC_CALIBRATE_DELAY
  26. bool
  27. default y
  28. config TIME_LOW_RES
  29. bool
  30. default y
  31. config ARCH_MAY_HAVE_PC_FDC
  32. bool
  33. depends on Q40 || (BROKEN && SUN3X)
  34. default y
  35. config NO_IOPORT
  36. def_bool y
  37. mainmenu "Linux/68k Kernel Configuration"
  38. source "init/Kconfig"
  39. menu "Platform dependent setup"
  40. config EISA
  41. bool
  42. ---help---
  43. The Extended Industry Standard Architecture (EISA) bus was
  44. developed as an open alternative to the IBM MicroChannel bus.
  45. The EISA bus provided some of the features of the IBM MicroChannel
  46. bus while maintaining backward compatibility with cards made for
  47. the older ISA bus. The EISA bus saw limited use between 1988 and
  48. 1995 when it was made obsolete by the PCI bus.
  49. Say Y here if you are building a kernel for an EISA-based machine.
  50. Otherwise, say N.
  51. config MCA
  52. bool
  53. help
  54. MicroChannel Architecture is found in some IBM PS/2 machines and
  55. laptops. It is a bus system similar to PCI or ISA. See
  56. <file:Documentation/mca.txt> (and especially the web page given
  57. there) before attempting to build an MCA bus kernel.
  58. config PCMCIA
  59. tristate
  60. ---help---
  61. Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
  62. computer. These are credit-card size devices such as network cards,
  63. modems or hard drives often used with laptops computers. There are
  64. actually two varieties of these cards: the older 16 bit PCMCIA cards
  65. and the newer 32 bit CardBus cards. If you want to use CardBus
  66. cards, you need to say Y here and also to "CardBus support" below.
  67. To use your PC-cards, you will need supporting software from David
  68. Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
  69. for location). Please also read the PCMCIA-HOWTO, available from
  70. <http://www.tldp.org/docs.html#howto>.
  71. To compile this driver as modules, choose M here: the
  72. modules will be called pcmcia_core and ds.
  73. config SUN3
  74. bool "Sun3 support"
  75. select M68020
  76. select MMU_SUN3 if MMU
  77. help
  78. This option enables support for the Sun 3 series of workstations
  79. (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
  80. that all other hardware types must be disabled, as Sun 3 kernels
  81. are incompatible with all other m68k targets (including Sun 3x!).
  82. If you don't want to compile a kernel exclusively for a Sun 3, say N.
  83. config AMIGA
  84. bool "Amiga support"
  85. depends on !MMU_SUN3
  86. help
  87. This option enables support for the Amiga series of computers. If
  88. you plan to use this kernel on an Amiga, say Y here and browse the
  89. material available in <file:Documentation/m68k>; otherwise say N.
  90. config ATARI
  91. bool "Atari support"
  92. depends on !MMU_SUN3
  93. help
  94. This option enables support for the 68000-based Atari series of
  95. computers (including the TT, Falcon and Medusa). If you plan to use
  96. this kernel on an Atari, say Y here and browse the material
  97. available in <file:Documentation/m68k>; otherwise say N.
  98. config HADES
  99. bool "Hades support"
  100. depends on ATARI && BROKEN
  101. help
  102. This option enables support for the Hades Atari clone. If you plan
  103. to use this kernel on a Hades, say Y here; otherwise say N.
  104. config PCI
  105. bool
  106. depends on HADES
  107. default y
  108. help
  109. Find out whether you have a PCI motherboard. PCI is the name of a
  110. bus system, i.e. the way the CPU talks to the other stuff inside
  111. your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  112. VESA. If you have PCI, say Y, otherwise N.
  113. The PCI-HOWTO, available from
  114. <http://www.tldp.org/docs.html#howto>, contains valuable
  115. information about which PCI hardware does work under Linux and which
  116. doesn't.
  117. config MAC
  118. bool "Macintosh support"
  119. depends on !MMU_SUN3
  120. help
  121. This option enables support for the Apple Macintosh series of
  122. computers (yes, there is experimental support now, at least for part
  123. of the series).
  124. Say N unless you're willing to code the remaining necessary support.
  125. ;)
  126. config NUBUS
  127. bool
  128. depends on MAC
  129. default y
  130. config M68K_L2_CACHE
  131. bool
  132. depends on MAC
  133. default y
  134. config APOLLO
  135. bool "Apollo support"
  136. depends on !MMU_SUN3
  137. help
  138. Say Y here if you want to run Linux on an MC680x0-based Apollo
  139. Domain workstation such as the DN3500.
  140. config VME
  141. bool "VME (Motorola and BVM) support"
  142. depends on !MMU_SUN3
  143. help
  144. Say Y here if you want to build a kernel for a 680x0 based VME
  145. board. Boards currently supported include Motorola boards MVME147,
  146. MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
  147. BVME6000 boards from BVM Ltd are also supported.
  148. config MVME147
  149. bool "MVME147 support"
  150. depends on VME
  151. help
  152. Say Y to include support for early Motorola VME boards. This will
  153. build a kernel which can run on MVME147 single-board computers. If
  154. you select this option you will have to select the appropriate
  155. drivers for SCSI, Ethernet and serial ports later on.
  156. config MVME16x
  157. bool "MVME162, 166 and 167 support"
  158. depends on VME
  159. help
  160. Say Y to include support for Motorola VME boards. This will build a
  161. kernel which can run on MVME162, MVME166, MVME167, MVME172, and
  162. MVME177 boards. If you select this option you will have to select
  163. the appropriate drivers for SCSI, Ethernet and serial ports later
  164. on.
  165. config BVME6000
  166. bool "BVME4000 and BVME6000 support"
  167. depends on VME
  168. help
  169. Say Y to include support for VME boards from BVM Ltd. This will
  170. build a kernel which can run on BVME4000 and BVME6000 boards. If
  171. you select this option you will have to select the appropriate
  172. drivers for SCSI, Ethernet and serial ports later on.
  173. config HP300
  174. bool "HP9000/300 and HP9000/400 support"
  175. depends on !MMU_SUN3
  176. help
  177. This option enables support for the HP9000/300 and HP9000/400 series
  178. of workstations. Support for these machines is still somewhat
  179. experimental. If you plan to try to use the kernel on such a machine
  180. say Y here.
  181. Everybody else says N.
  182. config DIO
  183. bool "DIO bus support"
  184. depends on HP300
  185. default y
  186. help
  187. Say Y here to enable support for the "DIO" expansion bus used in
  188. HP300 machines. If you are using such a system you almost certainly
  189. want this.
  190. config SUN3X
  191. bool "Sun3x support"
  192. depends on !MMU_SUN3
  193. select M68030
  194. help
  195. This option enables support for the Sun 3x series of workstations.
  196. Be warned that this support is very experimental.
  197. Note that Sun 3x kernels are not compatible with Sun 3 hardware.
  198. General Linux information on the Sun 3x series (now discontinued)
  199. is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
  200. If you don't want to compile a kernel for a Sun 3x, say N.
  201. config Q40
  202. bool "Q40/Q60 support"
  203. depends on !MMU_SUN3
  204. help
  205. The Q40 is a Motorola 68040-based successor to the Sinclair QL
  206. manufactured in Germany. There is an official Q40 home page at
  207. <http://www.q40.de/>. This option enables support for the Q40 and
  208. Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
  209. emulation.
  210. comment "Processor type"
  211. config M68020
  212. bool "68020 support"
  213. help
  214. If you anticipate running this kernel on a computer with a MC68020
  215. processor, say Y. Otherwise, say N. Note that the 68020 requires a
  216. 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
  217. Sun 3, which provides its own version.
  218. config M68030
  219. bool "68030 support"
  220. depends on !MMU_SUN3
  221. help
  222. If you anticipate running this kernel on a computer with a MC68030
  223. processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
  224. work, as it does not include an MMU (Memory Management Unit).
  225. config M68040
  226. bool "68040 support"
  227. depends on !MMU_SUN3
  228. help
  229. If you anticipate running this kernel on a computer with a MC68LC040
  230. or MC68040 processor, say Y. Otherwise, say N. Note that an
  231. MC68EC040 will not work, as it does not include an MMU (Memory
  232. Management Unit).
  233. config M68060
  234. bool "68060 support"
  235. depends on !MMU_SUN3
  236. help
  237. If you anticipate running this kernel on a computer with a MC68060
  238. processor, say Y. Otherwise, say N.
  239. config MMU_MOTOROLA
  240. bool
  241. depends on MMU && !MMU_SUN3
  242. default y
  243. config MMU_SUN3
  244. bool
  245. config M68KFPU_EMU
  246. bool "Math emulation support (EXPERIMENTAL)"
  247. depends on EXPERIMENTAL
  248. help
  249. At some point in the future, this will cause floating-point math
  250. instructions to be emulated by the kernel on machines that lack a
  251. floating-point math coprocessor. Thrill-seekers and chronically
  252. sleep-deprived psychotic hacker types can say Y now, everyone else
  253. should probably wait a while.
  254. config M68KFPU_EMU_EXTRAPREC
  255. bool "Math emulation extra precision"
  256. depends on M68KFPU_EMU
  257. help
  258. The fpu uses normally a few bit more during calculations for
  259. correct rounding, the emulator can (often) do the same but this
  260. extra calculation can cost quite some time, so you can disable
  261. it here. The emulator will then "only" calculate with a 64 bit
  262. mantissa and round slightly incorrect, what is more then enough
  263. for normal usage.
  264. config M68KFPU_EMU_ONLY
  265. bool "Math emulation only kernel"
  266. depends on M68KFPU_EMU
  267. help
  268. This option prevents any floating-point instructions from being
  269. compiled into the kernel, thereby the kernel doesn't save any
  270. floating point context anymore during task switches, so this
  271. kernel will only be usable on machines without a floating-point
  272. math coprocessor. This makes the kernel a bit faster as no tests
  273. needs to be executed whether a floating-point instruction in the
  274. kernel should be executed or not.
  275. config ADVANCED
  276. bool "Advanced configuration options"
  277. ---help---
  278. This gives you access to some advanced options for the CPU. The
  279. defaults should be fine for most users, but these options may make
  280. it possible for you to improve performance somewhat if you know what
  281. you are doing.
  282. Note that the answer to this question won't directly affect the
  283. kernel: saying N will just cause the configurator to skip all
  284. the questions about these options.
  285. Most users should say N to this question.
  286. config RMW_INSNS
  287. bool "Use read-modify-write instructions"
  288. depends on ADVANCED
  289. ---help---
  290. This allows to use certain instructions that work with indivisible
  291. read-modify-write bus cycles. While this is faster than the
  292. workaround of disabling interrupts, it can conflict with DMA
  293. ( = direct memory access) on many Amiga systems, and it is also said
  294. to destabilize other machines. It is very likely that this will
  295. cause serious problems on any Amiga or Atari Medusa if set. The only
  296. configuration where it should work are 68030-based Ataris, where it
  297. apparently improves performance. But you've been warned! Unless you
  298. really know what you are doing, say N. Try Y only if you're quite
  299. adventurous.
  300. config SINGLE_MEMORY_CHUNK
  301. bool "Use one physical chunk of memory only"
  302. depends on ADVANCED && !SUN3
  303. help
  304. Ignore all but the first contiguous chunk of physical memory for VM
  305. purposes. This will save a few bytes kernel size and may speed up
  306. some operations. Say N if not sure.
  307. config 060_WRITETHROUGH
  308. bool "Use write-through caching for 68060 supervisor accesses"
  309. depends on ADVANCED && M68060
  310. ---help---
  311. The 68060 generally uses copyback caching of recently accessed data.
  312. Copyback caching means that memory writes will be held in an on-chip
  313. cache and only written back to memory some time later. Saying Y
  314. here will force supervisor (kernel) accesses to use writethrough
  315. caching. Writethrough caching means that data is written to memory
  316. straight away, so that cache and memory data always agree.
  317. Writethrough caching is less efficient, but is needed for some
  318. drivers on 68060 based systems where the 68060 bus snooping signal
  319. is hardwired on. The 53c710 SCSI driver is known to suffer from
  320. this problem.
  321. source "mm/Kconfig"
  322. endmenu
  323. menu "General setup"
  324. source "fs/Kconfig.binfmt"
  325. config ZORRO
  326. bool "Amiga Zorro (AutoConfig) bus support"
  327. depends on AMIGA
  328. help
  329. This enables support for the Zorro bus in the Amiga. If you have
  330. expansion cards in your Amiga that conform to the Amiga
  331. AutoConfig(tm) specification, say Y, otherwise N. Note that even
  332. expansion cards that do not fit in the Zorro slots but fit in e.g.
  333. the CPU slot may fall in this category, so you have to say Y to let
  334. Linux use these.
  335. config AMIGA_PCMCIA
  336. bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
  337. depends on AMIGA && EXPERIMENTAL
  338. help
  339. Include support in the kernel for pcmcia on Amiga 1200 and Amiga
  340. 600. If you intend to use pcmcia cards say Y; otherwise say N.
  341. config STRAM_PROC
  342. bool "ST-RAM statistics in /proc"
  343. depends on ATARI
  344. help
  345. Say Y here to report ST-RAM usage statistics in /proc/stram.
  346. config ATARI_KBD_CORE
  347. bool
  348. config HEARTBEAT
  349. bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
  350. default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
  351. help
  352. Use the power-on LED on your machine as a load meter. The exact
  353. behavior is platform-dependent, but normally the flash frequency is
  354. a hyperbolic function of the 5-minute load average.
  355. # We have a dedicated heartbeat LED. :-)
  356. config PROC_HARDWARE
  357. bool "/proc/hardware support"
  358. help
  359. Say Y here to support the /proc/hardware file, which gives you
  360. access to information about the machine you're running on,
  361. including the model, CPU, MMU, clock speed, BogoMIPS rating,
  362. and memory size.
  363. config ISA
  364. bool
  365. depends on Q40 || AMIGA_PCMCIA || GG2
  366. default y
  367. help
  368. Find out whether you have ISA slots on your motherboard. ISA is the
  369. name of a bus system, i.e. the way the CPU talks to the other stuff
  370. inside your box. Other bus systems are PCI, EISA, MicroChannel
  371. (MCA) or VESA. ISA is an older system, now being displaced by PCI;
  372. newer boards don't support it. If you have ISA, say Y, otherwise N.
  373. config GENERIC_ISA_DMA
  374. bool
  375. depends on Q40 || AMIGA_PCMCIA || GG2
  376. default y
  377. config ZONE_DMA
  378. bool
  379. default y
  380. source "drivers/pci/Kconfig"
  381. source "drivers/zorro/Kconfig"
  382. endmenu
  383. source "net/Kconfig"
  384. source "drivers/Kconfig"
  385. menu "Character devices"
  386. config ATARI_MFPSER
  387. tristate "Atari MFP serial support"
  388. depends on ATARI
  389. ---help---
  390. If you like to use the MFP serial ports ("Modem1", "Serial1") under
  391. Linux, say Y. The driver equally supports all kinds of MFP serial
  392. ports and automatically detects whether Serial1 is available.
  393. To compile this driver as a module, choose M here.
  394. Note for Falcon users: You also have an MFP port, it's just not
  395. wired to the outside... But you could use the port under Linux.
  396. config ATARI_SCC
  397. tristate "Atari SCC serial support"
  398. depends on ATARI
  399. ---help---
  400. If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
  401. LAN) and like to use them under Linux, say Y. All built-in SCC's are
  402. supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
  403. two connectors for channel A (Serial2 and LAN), they are visible as
  404. two separate devices.
  405. To compile this driver as a module, choose M here.
  406. config ATARI_SCC_DMA
  407. bool "Atari SCC serial DMA support"
  408. depends on ATARI_SCC
  409. help
  410. This enables DMA support for receiving data on channel A of the SCC.
  411. If you have a TT you may say Y here and read
  412. drivers/char/atari_SCC.README. All other users should say N here,
  413. because only the TT has SCC-DMA, even if your machine keeps claiming
  414. so at boot time.
  415. config ATARI_MIDI
  416. tristate "Atari MIDI serial support"
  417. depends on ATARI
  418. help
  419. If you want to use your Atari's MIDI port in Linux, say Y.
  420. To compile this driver as a module, choose M here.
  421. config ATARI_DSP56K
  422. tristate "Atari DSP56k support (EXPERIMENTAL)"
  423. depends on ATARI && EXPERIMENTAL
  424. help
  425. If you want to be able to use the DSP56001 in Falcons, say Y. This
  426. driver is still experimental, and if you don't know what it is, or
  427. if you don't have this processor, just say N.
  428. To compile this driver as a module, choose M here.
  429. config AMIGA_BUILTIN_SERIAL
  430. tristate "Amiga builtin serial support"
  431. depends on AMIGA
  432. help
  433. If you want to use your Amiga's built-in serial port in Linux,
  434. answer Y.
  435. To compile this driver as a module, choose M here.
  436. config WHIPPET_SERIAL
  437. tristate "Hisoft Whippet PCMCIA serial support"
  438. depends on AMIGA_PCMCIA
  439. help
  440. HiSoft has a web page at <http://www.hisoft.co.uk/>, but there
  441. is no listing for the Whippet in their Amiga section.
  442. config MULTIFACE_III_TTY
  443. tristate "Multiface Card III serial support"
  444. depends on AMIGA
  445. help
  446. If you want to use a Multiface III card's serial port in Linux,
  447. answer Y.
  448. To compile this driver as a module, choose M here.
  449. config GVPIOEXT
  450. tristate "GVP IO-Extender support"
  451. depends on PARPORT=n && ZORRO
  452. help
  453. If you want to use a GVP IO-Extender serial card in Linux, say Y.
  454. Otherwise, say N.
  455. config GVPIOEXT_LP
  456. tristate "GVP IO-Extender parallel printer support"
  457. depends on GVPIOEXT
  458. help
  459. Say Y to enable driving a printer from the parallel port on your
  460. GVP IO-Extender card, N otherwise.
  461. config GVPIOEXT_PLIP
  462. tristate "GVP IO-Extender PLIP support"
  463. depends on GVPIOEXT
  464. help
  465. Say Y to enable doing IP over the parallel port on your GVP
  466. IO-Extender card, N otherwise.
  467. config MAC_SCC
  468. tristate "Macintosh serial support"
  469. depends on MAC
  470. config MAC_HID
  471. bool
  472. depends on INPUT_ADBHID
  473. default y
  474. config MAC_ADBKEYCODES
  475. bool "Support for ADB raw keycodes"
  476. depends on INPUT_ADBHID
  477. help
  478. This provides support for sending raw ADB keycodes to console
  479. devices. This is the default up to 2.4.0, but in future this may be
  480. phased out in favor of generic Linux keycodes. If you say Y here,
  481. you can dynamically switch via the
  482. /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
  483. sysctl and with the "keyboard_sends_linux_keycodes=" kernel
  484. argument.
  485. If unsure, say Y here.
  486. config ADB_KEYBOARD
  487. bool "Support for ADB keyboard (old driver)"
  488. depends on MAC && !INPUT_ADBHID
  489. help
  490. This option allows you to use an ADB keyboard attached to your
  491. machine. Note that this disables any other (ie. PS/2) keyboard
  492. support, even if your machine is physically capable of using both at
  493. the same time.
  494. If you use an ADB keyboard (4 pin connector), say Y here.
  495. If you use a PS/2 keyboard (6 pin connector), say N here.
  496. config HPDCA
  497. tristate "HP DCA serial support"
  498. depends on DIO && SERIAL_8250
  499. help
  500. If you want to use the internal "DCA" serial ports on an HP300
  501. machine, say Y here.
  502. config HPAPCI
  503. tristate "HP APCI serial support"
  504. depends on HP300 && SERIAL_8250 && EXPERIMENTAL
  505. help
  506. If you want to use the internal "APCI" serial ports on an HP400
  507. machine, say Y here.
  508. config MVME147_SCC
  509. bool "SCC support for MVME147 serial ports"
  510. depends on MVME147
  511. help
  512. This is the driver for the serial ports on the Motorola MVME147
  513. boards. Everyone using one of these boards should say Y here.
  514. config SERIAL167
  515. bool "CD2401 support for MVME166/7 serial ports"
  516. depends on MVME16x
  517. help
  518. This is the driver for the serial ports on the Motorola MVME166,
  519. 167, and 172 boards. Everyone using one of these boards should say
  520. Y here.
  521. config MVME162_SCC
  522. bool "SCC support for MVME162 serial ports"
  523. depends on MVME16x
  524. help
  525. This is the driver for the serial ports on the Motorola MVME162 and
  526. 172 boards. Everyone using one of these boards should say Y here.
  527. config BVME6000_SCC
  528. bool "SCC support for BVME6000 serial ports"
  529. depends on BVME6000
  530. help
  531. This is the driver for the serial ports on the BVME4000 and BVME6000
  532. boards from BVM Ltd. Everyone using one of these boards should say
  533. Y here.
  534. config DN_SERIAL
  535. bool "Support for DN serial port (dummy)"
  536. depends on APOLLO
  537. config SERIAL_CONSOLE
  538. bool "Support for serial port console"
  539. depends on (AMIGA || ATARI || MAC || SUN3 || SUN3X || VME || APOLLO) && (ATARI_MFPSER=y || ATARI_SCC=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)
  540. ---help---
  541. If you say Y here, it will be possible to use a serial port as the
  542. system console (the system console is the device which receives all
  543. kernel messages and warnings and which allows logins in single user
  544. mode). This could be useful if some terminal or printer is connected
  545. to that serial port.
  546. Even if you say Y here, the currently visible virtual console
  547. (/dev/tty0) will still be used as the system console by default, but
  548. you can alter that using a kernel command line option such as
  549. "console=ttyS1". (Try "man bootparam" or see the documentation of
  550. your boot loader (lilo or loadlin) about how to pass options to the
  551. kernel at boot time.)
  552. If you don't have a VGA card installed and you say Y here, the
  553. kernel will automatically use the first serial line, /dev/ttyS0, as
  554. system console.
  555. If unsure, say N.
  556. endmenu
  557. source "fs/Kconfig"
  558. source "arch/m68k/Kconfig.debug"
  559. source "security/Kconfig"
  560. source "crypto/Kconfig"
  561. source "lib/Kconfig"