1 # SPDX-License-Identifier: GPL-2.0
2 comment "Machine Types"
9 select MMU_MOTOROLA if MMU
10 select LEGACY_TIMER_TICK
12 This option enables support for the Amiga series of computers. If
13 you plan to use this kernel on an Amiga, say Y here and browse the
14 material available in <file:Documentation/m68k>; otherwise say N.
19 select MMU_MOTOROLA if MMU
20 select HAVE_ARCH_NVRAM_OPS
21 select LEGACY_TIMER_TICK
23 This option enables support for the 68000-based Atari series of
24 computers (including the TT, Falcon and Medusa). If you plan to use
25 this kernel on an Atari, say Y here and browse the material
26 available in <file:Documentation/m68k>; otherwise say N.
32 bool "Macintosh support"
34 select MMU_MOTOROLA if MMU
35 select HAVE_ARCH_NVRAM_OPS
36 select LEGACY_TIMER_TICK
38 This option enables support for the Apple Macintosh series of
39 computers. If you plan to use this kernel on a Mac, say Y here and
40 browse the documentation available at <http://www.mac.linux-m68k.org/>;
46 select MMU_MOTOROLA if MMU
47 select LEGACY_TIMER_TICK
49 Say Y here if you want to run Linux on an MC680x0-based Apollo
50 Domain workstation such as the DN3500.
53 bool "VME (Motorola and BVM) support"
55 select MMU_MOTOROLA if MMU
57 Say Y here if you want to build a kernel for a 680x0 based VME
58 board. Boards currently supported include Motorola boards MVME147,
59 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
60 BVME6000 boards from BVM Ltd are also supported.
63 bool "MVME147 support"
66 select LEGACY_TIMER_TICK
68 Say Y to include support for early Motorola VME boards. This will
69 build a kernel which can run on MVME147 single-board computers. If
70 you select this option you will have to select the appropriate
71 drivers for SCSI, Ethernet and serial ports later on.
74 bool "MVME162, 166 and 167 support"
77 select LEGACY_TIMER_TICK
79 Say Y to include support for Motorola VME boards. This will build a
80 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
81 MVME177 boards. If you select this option you will have to select
82 the appropriate drivers for SCSI, Ethernet and serial ports later
86 bool "BVME4000 and BVME6000 support"
89 select LEGACY_TIMER_TICK
91 Say Y to include support for VME boards from BVM Ltd. This will
92 build a kernel which can run on BVME4000 and BVME6000 boards. If
93 you select this option you will have to select the appropriate
94 drivers for SCSI, Ethernet and serial ports later on.
97 bool "HP9000/300 and HP9000/400 support"
99 select MMU_MOTOROLA if MMU
100 select LEGACY_TIMER_TICK
102 This option enables support for the HP9000/300 and HP9000/400 series
103 of workstations. Support for these machines is still somewhat
104 experimental. If you plan to try to use the kernel on such a machine
106 Everybody else says N.
111 select LEGACY_TIMER_TICK
112 select MMU_MOTOROLA if MMU
115 This option enables support for the Sun 3x series of workstations.
116 Be warned that this support is very experimental.
117 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
118 General Linux information on the Sun 3x series (now discontinued)
119 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
121 If you don't want to compile a kernel for a Sun 3x, say N.
124 bool "Q40/Q60 support"
126 select MMU_MOTOROLA if MMU
127 select LEGACY_TIMER_TICK
129 The Q40 is a Motorola 68040-based successor to the Sinclair QL
130 manufactured in Germany. There is an official Q40 home page at
131 <http://www.q40.de/>. This option enables support for the Q40 and
132 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
138 depends on !MMU_MOTOROLA
139 select MMU_SUN3 if MMU
140 select LEGACY_TIMER_TICK
144 This option enables support for the Sun 3 series of workstations
145 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
146 that all other hardware types must be disabled, as Sun 3 kernels
147 are incompatible with all other m68k targets (including Sun 3x!).
149 If you don't want to compile a kernel exclusively for a Sun 3, say N.
155 bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support"
160 Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII.
163 bool "(X)Copilot support"
166 Support the bugs of Xcopilot.
169 bool "uCsimm module support"
173 Support for the Arcturus Networks uCsimm module.
176 bool "uDsimm module support"
180 Support for the Arcturus Networks uDsimm module.
183 bool "DragenEngine II board support"
187 Support for the DragenEngine II board.
189 config DIRECT_IO_ACCESS
190 bool "Allow user to access IO directly"
191 depends on (UCSIMM || UCDIMM || DRAGEN2)
193 Disable the CPU internal registers protection in user mode,
194 to allow a user application to read/write them.
197 bool "Initialize LCD"
198 depends on (UCSIMM || UCDIMM || DRAGEN2)
200 Initialize the LCD controller of the 68x328 processor.
202 config MEMORY_RESERVE
203 int "Memory reservation (MiB)"
204 depends on (UCSIMM || UCDIMM)
206 Reserve certain memory regions on 68x328 based boards.
211 bool "Arnewsh 5206 board support"
214 Support for the Arnewsh 5206 board.
217 bool "Motorola M5206eC3 board support"
220 Support for the Motorola M5206eC3 board.
223 bool "Motorola M5206eLITE board support"
226 Support for the Motorola M5206eLITE board.
229 bool "Freescale M5235EVB support"
232 Support for the Freescale M5235EVB board.
235 bool "Motorola M5249C3 board support"
238 Support for the Motorola M5249C3 board.
241 bool "Motorola M5272C3 board support"
244 Support for the Motorola M5272C3 board.
247 bool "Intec Automation Inc. WildFire board support"
250 Support for the Intec Automation Inc. WildFire.
253 bool "Intec Automation Inc. WildFire module support"
256 Support for the Intec Automation Inc. WildFire module.
259 bool "Arnewsh 5307 board support"
262 Support for the Arnewsh 5307 board.
265 bool "Motorola M5307C3 board support"
268 Support for the Motorola M5307C3 board.
271 bool "SnapGear SecureEdge/MP3 platform support"
274 Support for the SnapGear SecureEdge/MP3 platform.
277 bool "Motorola M5407C3 board support"
280 Support for the Motorola M5407C3 board.
283 bool "Sysam AMCORE board support"
286 Support for the Sysam AMCORE open-hardware generic board.
289 bool "Sysam stmark2 board support"
292 Support for the Sysam stmark2 open-hardware generic board.
295 bool "FireBee board support"
298 Support for the FireBee ColdFire 5475 based board.
301 bool "Feith CLEOPATRA board support"
302 depends on (M5307 || M5407)
304 Support for the Feith Cleopatra boards.
307 bool "Feith CANCam board support"
310 Support for the Feith CANCam board.
313 bool "Feith SCALES board support"
316 Support for the Feith SCALES board.
319 bool "SecureEdge/NETtel board support"
320 depends on (M5206e || M5272 || M5307)
322 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
325 bool "Netburner MOD-5272 board support"
328 Support for the Netburner MOD-5272 board.
332 comment "Machine Options"
335 bool "Support for U-Boot command line parameters"
337 If you say Y here kernel will try to collect command
338 line parameters from the initial u-boot stack.
341 bool "Use 4Kb for kernel stacks instead of 8Kb"
344 If you say Y here the kernel will use a 4Kb stacksize for the
345 kernel stack attached to each process/thread. This facilitates
346 running more threads on a system and also reduces the pressure
347 on the VM subsystem for higher order allocations.
349 comment "RAM configuration"
352 hex "Address of the base of RAM"
355 Define the address that RAM starts at. On many platforms this is
356 0, the base of the address space. And this is the default. Some
357 platforms choose to setup their RAM at other addresses within the
358 processor address space.
361 hex "Size of RAM (in bytes), or 0 for automatic"
364 Define the size of the system RAM. If you select 0 then the
365 kernel will try to probe the RAM size at runtime. This is not
366 supported on all CPU types.
369 hex "Address of the base of system vectors"
372 Define the address of the system vectors. Commonly this is
373 put at the start of RAM, but it doesn't have to be. On ColdFire
374 platforms this address is programmed into the VBR register, thus
375 actually setting the address to use.
378 hex "Address of the MBAR (internal peripherals)"
382 Define the address of the internal system peripherals. This value
383 is set in the processors MBAR register. This is generally setup by
384 the boot loader, and will not be written by the kernel. By far most
385 ColdFire boards use the default 0x10000000 value, so if unsure then
389 hex "Address of the IPSBAR (internal peripherals)"
391 depends on HAVE_IPSBAR
393 Define the address of the internal system peripherals. This value
394 is set in the processors IPSBAR register. This is generally setup by
395 the boot loader, and will not be written by the kernel. By far most
396 ColdFire boards use the default 0x40000000 value, so if unsure then
400 hex "Address of the base of kernel code"
403 Typically on m68k systems the kernel will not start at the base
404 of RAM, but usually some small offset from it. Define the start
405 address of the kernel here. The most common setup will have the
406 processor vectors at the base of RAM and then the start of the
407 kernel. On some platforms some RAM is reserved for boot loaders
408 and the kernel starts after that. The 0x400 default was based on
409 a system with the RAM based at address 0, and leaving enough room
410 for the theoretical maximum number of 256 vectors.
412 comment "ROM configuration"
415 bool "Specify ROM linker regions"
417 Define a ROM region for the linker script. This creates a kernel
418 that can be stored in flash, with possibly the text, and data
419 regions being copied out to RAM at startup.
422 hex "Address of the base of ROM device"
426 Define the address that the ROM region starts at. Some platforms
427 use this to set their chip select region accordingly for the boot
431 hex "Address of the base of the ROM vectors"
435 This is almost always the same as the base of the ROM. Since on all
436 68000 type variants the vectors are at the base of the boot device
440 hex "Address of the base of system image in ROM"
444 Define the start address of the system image in ROM. Commonly this
445 is strait after the ROM vectors.
448 hex "Size of the ROM device"
452 Size of the ROM device. On some platforms this is used to setup
453 the chip select that controls the boot ROM device.
456 prompt "Kernel executes from"
458 Choose the memory type that the kernel will be running in.
463 The kernel will be resident in RAM when running.
468 The kernel will be resident in FLASH/ROM when running. This is
469 often referred to as Execute-in-Place (XIP), since the kernel
470 code executes from the position it is stored in the FLASH/ROM.