Kconfig 21 KB

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