]>
Commit | Line | Data |
---|---|---|
1 | # SPDX-License-Identifier: GPL-2.0 | |
2 | if MMU | |
3 | ||
4 | config ARCH_MAY_HAVE_PC_FDC | |
5 | bool | |
6 | depends on BROKEN && (Q40 || SUN3X) | |
7 | default y | |
8 | ||
9 | menu "Platform devices" | |
10 | ||
11 | config HEARTBEAT | |
12 | bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || Q40 | |
13 | default y if !AMIGA && !APOLLO && !ATARI && !Q40 && HP300 | |
14 | help | |
15 | Use the power-on LED on your machine as a load meter. The exact | |
16 | behavior is platform-dependent, but normally the flash frequency is | |
17 | a hyperbolic function of the 5-minute load average. | |
18 | ||
19 | # We have a dedicated heartbeat LED. :-) | |
20 | config PROC_HARDWARE | |
21 | bool "/proc/hardware support" | |
22 | help | |
23 | Say Y here to support the /proc/hardware file, which gives you | |
24 | access to information about the machine you're running on, | |
25 | including the model, CPU, MMU, clock speed, BogoMIPS rating, | |
26 | and memory size. | |
27 | ||
28 | config NATFEAT | |
29 | bool "ARAnyM emulator support" | |
30 | depends on ATARI | |
31 | help | |
32 | This option enables support for ARAnyM native features, such as | |
33 | access to a disk image as /dev/hda. | |
34 | ||
35 | config NFBLOCK | |
36 | tristate "NatFeat block device support" | |
37 | depends on BLOCK && NATFEAT | |
38 | help | |
39 | Say Y to include support for the ARAnyM NatFeat block device | |
40 | which allows direct access to the hard drives without using | |
41 | the hardware emulation. | |
42 | ||
43 | config NFCON | |
44 | tristate "NatFeat console driver" | |
45 | depends on TTY && NATFEAT | |
46 | help | |
47 | Say Y to include support for the ARAnyM NatFeat console driver | |
48 | which allows the console output to be redirected to the stderr | |
49 | output of ARAnyM. | |
50 | ||
51 | config NFETH | |
52 | tristate "NatFeat Ethernet support" | |
53 | depends on ETHERNET && NATFEAT | |
54 | help | |
55 | Say Y to include support for the ARAnyM NatFeat network device | |
56 | which will emulate a regular ethernet device while presenting an | |
57 | ethertap device to the host system. | |
58 | ||
59 | config ATARI_ETHERNAT | |
60 | bool "Atari EtherNAT Ethernet support" | |
61 | depends on ATARI | |
62 | ---help--- | |
63 | Say Y to include support for the EtherNAT network adapter for the | |
64 | CT/60 extension port. | |
65 | ||
66 | To compile the actual ethernet driver, choose Y or M for the SMC91X | |
67 | option in the network device section; the module will be called smc91x. | |
68 | ||
69 | config ATARI_ETHERNEC | |
70 | bool "Atari EtherNEC Ethernet support" | |
71 | depends on ATARI_ROM_ISA | |
72 | ---help--- | |
73 | Say Y to include support for the EtherNEC network adapter for the | |
74 | ROM port. The driver works by polling instead of interrupts, so it | |
75 | is quite slow. | |
76 | ||
77 | This driver also supports the ethernet part of the NetUSBee ROM | |
78 | port combined Ethernet/USB adapter. | |
79 | ||
80 | To compile the actual ethernet driver, choose Y or M in for the NE2000 | |
81 | option in the network device section; the module will be called ne. | |
82 | ||
83 | endmenu | |
84 | ||
85 | menu "Character devices" | |
86 | ||
87 | config ATARI_DSP56K | |
88 | tristate "Atari DSP56k support" | |
89 | depends on ATARI | |
90 | help | |
91 | If you want to be able to use the DSP56001 in Falcons, say Y. This | |
92 | driver is still experimental, and if you don't know what it is, or | |
93 | if you don't have this processor, just say N. | |
94 | ||
95 | To compile this driver as a module, choose M here. | |
96 | ||
97 | config AMIGA_BUILTIN_SERIAL | |
98 | tristate "Amiga builtin serial support" | |
99 | depends on AMIGA && TTY | |
100 | help | |
101 | If you want to use your Amiga's built-in serial port in Linux, | |
102 | answer Y. | |
103 | ||
104 | To compile this driver as a module, choose M here. | |
105 | ||
106 | config HPDCA | |
107 | tristate "HP DCA serial support" | |
108 | depends on DIO && SERIAL_8250 | |
109 | help | |
110 | If you want to use the internal "DCA" serial ports on an HP300 | |
111 | machine, say Y here. | |
112 | ||
113 | config HPAPCI | |
114 | tristate "HP APCI serial support" | |
115 | depends on HP300 && SERIAL_8250 | |
116 | help | |
117 | If you want to use the internal "APCI" serial ports on an HP400 | |
118 | machine, say Y here. | |
119 | ||
120 | config SERIAL_CONSOLE | |
121 | bool "Support for serial port console" | |
122 | depends on AMIGA_BUILTIN_SERIAL=y | |
123 | ---help--- | |
124 | If you say Y here, it will be possible to use a serial port as the | |
125 | system console (the system console is the device which receives all | |
126 | kernel messages and warnings and which allows logins in single user | |
127 | mode). This could be useful if some terminal or printer is connected | |
128 | to that serial port. | |
129 | ||
130 | Even if you say Y here, the currently visible virtual console | |
131 | (/dev/tty0) will still be used as the system console by default, but | |
132 | you can alter that using a kernel command line option such as | |
133 | "console=ttyS1". (Try "man bootparam" or see the documentation of | |
134 | your boot loader about how to pass options to the kernel at boot | |
135 | time.) | |
136 | ||
137 | If you don't have a graphical console and you say Y here, the | |
138 | kernel will automatically use the first serial line, /dev/ttyS0, as | |
139 | system console. | |
140 | ||
141 | If unsure, say N. | |
142 | ||
143 | endmenu | |
144 | ||
145 | endif |