1 # SPDX-License-Identifier: GPL-2.0
2 comment "Machine Types"
9 select MMU_MOTOROLA if MMU
11 This option enables support for the Amiga series of computers. If
12 you plan to use this kernel on an Amiga, say Y here and browse the
13 material available in <file:Documentation/m68k>; otherwise say N.
18 select MMU_MOTOROLA if MMU
19 select HAVE_ARCH_NVRAM_OPS
21 This option enables support for the 68000-based Atari series of
22 computers (including the TT, Falcon and Medusa). If you plan to use
23 this kernel on an Atari, say Y here and browse the material
24 available in <file:Documentation/m68k>; otherwise say N.
27 bool "Macintosh support"
29 select MMU_MOTOROLA if MMU
30 select HAVE_ARCH_NVRAM_OPS
32 This option enables support for the Apple Macintosh series of
33 computers. If you plan to use this kernel on a Mac, say Y here and
34 browse the documentation available at <http://www.mac.linux-m68k.org/>;
40 select MMU_MOTOROLA if MMU
42 Say Y here if you want to run Linux on an MC680x0-based Apollo
43 Domain workstation such as the DN3500.
46 bool "VME (Motorola and BVM) support"
48 select MMU_MOTOROLA if MMU
50 Say Y here if you want to build a kernel for a 680x0 based VME
51 board. Boards currently supported include Motorola boards MVME147,
52 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
53 BVME6000 boards from BVM Ltd are also supported.
56 bool "MVME147 support"
60 Say Y to include support for early Motorola VME boards. This will
61 build a kernel which can run on MVME147 single-board computers. If
62 you select this option you will have to select the appropriate
63 drivers for SCSI, Ethernet and serial ports later on.
66 bool "MVME162, 166 and 167 support"
70 Say Y to include support for Motorola VME boards. This will build a
71 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
72 MVME177 boards. If you select this option you will have to select
73 the appropriate drivers for SCSI, Ethernet and serial ports later
77 bool "BVME4000 and BVME6000 support"
81 Say Y to include support for VME boards from BVM Ltd. This will
82 build a kernel which can run on BVME4000 and BVME6000 boards. If
83 you select this option you will have to select the appropriate
84 drivers for SCSI, Ethernet and serial ports later on.
87 bool "HP9000/300 and HP9000/400 support"
89 select MMU_MOTOROLA if MMU
91 This option enables support for the HP9000/300 and HP9000/400 series
92 of workstations. Support for these machines is still somewhat
93 experimental. If you plan to try to use the kernel on such a machine
95 Everybody else says N.
100 select MMU_MOTOROLA if MMU
103 This option enables support for the Sun 3x series of workstations.
104 Be warned that this support is very experimental.
105 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
106 General Linux information on the Sun 3x series (now discontinued)
107 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
109 If you don't want to compile a kernel for a Sun 3x, say N.
112 bool "Q40/Q60 support"
114 select MMU_MOTOROLA if MMU
116 The Q40 is a Motorola 68040-based successor to the Sinclair QL
117 manufactured in Germany. There is an official Q40 home page at
118 <http://www.q40.de/>. This option enables support for the Q40 and
119 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
125 depends on !MMU_MOTOROLA
126 select MMU_SUN3 if MMU
130 This option enables support for the Sun 3 series of workstations
131 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
132 that all other hardware types must be disabled, as Sun 3 kernels
133 are incompatible with all other m68k targets (including Sun 3x!).
135 If you don't want to compile a kernel exclusively for a Sun 3, say N.
143 bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support"
147 Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII.
150 bool "(X)Copilot support"
153 Support the bugs of Xcopilot.
156 bool "uCsimm module support"
159 Support for the Arcturus Networks uCsimm module.
162 bool "uDsimm module support"
165 Support for the Arcturus Networks uDsimm module.
168 bool "DragenEngine II board support"
171 Support for the DragenEngine II board.
173 config DIRECT_IO_ACCESS
174 bool "Allow user to access IO directly"
175 depends on (UCSIMM || UCDIMM || DRAGEN2)
177 Disable the CPU internal registers protection in user mode,
178 to allow a user application to read/write them.
181 bool "Initialize LCD"
182 depends on (UCSIMM || UCDIMM || DRAGEN2)
184 Initialize the LCD controller of the 68x328 processor.
186 config MEMORY_RESERVE
187 int "Memory reservation (MiB)"
188 depends on (UCSIMM || UCDIMM)
190 Reserve certain memory regions on 68x328 based boards.
193 bool "Arnewsh 5206 board support"
196 Support for the Arnewsh 5206 board.
199 bool "Motorola M5206eC3 board support"
202 Support for the Motorola M5206eC3 board.
205 bool "Motorola M5206eLITE board support"
208 Support for the Motorola M5206eLITE board.
211 bool "Freescale M5235EVB support"
214 Support for the Freescale M5235EVB board.
217 bool "Motorola M5249C3 board support"
220 Support for the Motorola M5249C3 board.
223 bool "Motorola M5272C3 board support"
226 Support for the Motorola M5272C3 board.
229 bool "Intec Automation Inc. WildFire board support"
232 Support for the Intec Automation Inc. WildFire.
235 bool "Intec Automation Inc. WildFire module support"
238 Support for the Intec Automation Inc. WildFire module.
241 bool "Arnewsh 5307 board support"
244 Support for the Arnewsh 5307 board.
247 bool "Motorola M5307C3 board support"
250 Support for the Motorola M5307C3 board.
253 bool "SnapGear SecureEdge/MP3 platform support"
256 Support for the SnapGear SecureEdge/MP3 platform.
259 bool "Motorola M5407C3 board support"
262 Support for the Motorola M5407C3 board.
265 bool "Sysam AMCORE board support"
268 Support for the Sysam AMCORE open-hardware generic board.
271 bool "Sysam stmark2 board support"
274 Support for the Sysam stmark2 open-hardware generic board.
277 bool "FireBee board support"
280 Support for the FireBee ColdFire 5475 based board.
283 bool "Feith CLEOPATRA board support"
284 depends on (M5307 || M5407)
286 Support for the Feith Cleopatra boards.
289 bool "Feith CANCam board support"
292 Support for the Feith CANCam board.
295 bool "Feith SCALES board support"
298 Support for the Feith SCALES board.
301 bool "SecureEdge/NETtel board support"
302 depends on (M5206e || M5272 || M5307)
304 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
307 bool "Netburner MOD-5272 board support"
310 Support for the Netburner MOD-5272 board.
314 comment "Machine Options"
317 bool "Support for U-Boot command line parameters"
319 If you say Y here kernel will try to collect command
320 line parameters from the initial u-boot stack.
323 bool "Use 4Kb for kernel stacks instead of 8Kb"
326 If you say Y here the kernel will use a 4Kb stacksize for the
327 kernel stack attached to each process/thread. This facilitates
328 running more threads on a system and also reduces the pressure
329 on the VM subsystem for higher order allocations.
331 comment "RAM configuration"
334 hex "Address of the base of RAM"
337 Define the address that RAM starts at. On many platforms this is
338 0, the base of the address space. And this is the default. Some
339 platforms choose to setup their RAM at other addresses within the
340 processor address space.
343 hex "Size of RAM (in bytes), or 0 for automatic"
346 Define the size of the system RAM. If you select 0 then the
347 kernel will try to probe the RAM size at runtime. This is not
348 supported on all CPU types.
351 hex "Address of the base of system vectors"
354 Define the address of the system vectors. Commonly this is
355 put at the start of RAM, but it doesn't have to be. On ColdFire
356 platforms this address is programmed into the VBR register, thus
357 actually setting the address to use.
360 hex "Address of the MBAR (internal peripherals)"
364 Define the address of the internal system peripherals. This value
365 is set in the processors MBAR register. This is generally setup by
366 the boot loader, and will not be written by the kernel. By far most
367 ColdFire boards use the default 0x10000000 value, so if unsure then
371 hex "Address of the IPSBAR (internal peripherals)"
373 depends on HAVE_IPSBAR
375 Define the address of the internal system peripherals. This value
376 is set in the processors IPSBAR register. This is generally setup by
377 the boot loader, and will not be written by the kernel. By far most
378 ColdFire boards use the default 0x40000000 value, so if unsure then
382 hex "Address of the base of kernel code"
385 Typically on m68k systems the kernel will not start at the base
386 of RAM, but usually some small offset from it. Define the start
387 address of the kernel here. The most common setup will have the
388 processor vectors at the base of RAM and then the start of the
389 kernel. On some platforms some RAM is reserved for boot loaders
390 and the kernel starts after that. The 0x400 default was based on
391 a system with the RAM based at address 0, and leaving enough room
392 for the theoretical maximum number of 256 vectors.
394 comment "ROM configuration"
397 bool "Specify ROM linker regions"
399 Define a ROM region for the linker script. This creates a kernel
400 that can be stored in flash, with possibly the text, and data
401 regions being copied out to RAM at startup.
404 hex "Address of the base of ROM device"
408 Define the address that the ROM region starts at. Some platforms
409 use this to set their chip select region accordingly for the boot
413 hex "Address of the base of the ROM vectors"
417 This is almost always the same as the base of the ROM. Since on all
418 68000 type variants the vectors are at the base of the boot device
422 hex "Address of the base of system image in ROM"
426 Define the start address of the system image in ROM. Commonly this
427 is strait after the ROM vectors.
430 hex "Size of the ROM device"
434 Size of the ROM device. On some platforms this is used to setup
435 the chip select that controls the boot ROM device.
438 prompt "Kernel executes from"
440 Choose the memory type that the kernel will be running in.
445 The kernel will be resident in RAM when running.
450 The kernel will be resident in FLASH/ROM when running. This is
451 often referred to as Execute-in-Place (XIP), since the kernel
452 code executes from the position it is stored in the FLASH/ROM.