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 HAVE_PATA_PLATFORM
37 select LEGACY_TIMER_TICK
39 This option enables support for the Apple Macintosh series of
40 computers. If you plan to use this kernel on a Mac, say Y here and
41 browse the documentation available at <http://www.mac.linux-m68k.org/>;
47 select MMU_MOTOROLA if MMU
48 select LEGACY_TIMER_TICK
50 Say Y here if you want to run Linux on an MC680x0-based Apollo
51 Domain workstation such as the DN3500.
54 bool "VME (Motorola and BVM) support"
56 select MMU_MOTOROLA if MMU
58 Say Y here if you want to build a kernel for a 680x0 based VME
59 board. Boards currently supported include Motorola boards MVME147,
60 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
61 BVME6000 boards from BVM Ltd are also supported.
64 bool "MVME147 support"
67 select LEGACY_TIMER_TICK
69 Say Y to include support for early Motorola VME boards. This will
70 build a kernel which can run on MVME147 single-board computers. If
71 you select this option you will have to select the appropriate
72 drivers for SCSI, Ethernet and serial ports later on.
75 bool "MVME162, 166 and 167 support"
78 select LEGACY_TIMER_TICK
80 Say Y to include support for Motorola VME boards. This will build a
81 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
82 MVME177 boards. If you select this option you will have to select
83 the appropriate drivers for SCSI, Ethernet and serial ports later
87 bool "BVME4000 and BVME6000 support"
90 select LEGACY_TIMER_TICK
92 Say Y to include support for VME boards from BVM Ltd. This will
93 build a kernel which can run on BVME4000 and BVME6000 boards. If
94 you select this option you will have to select the appropriate
95 drivers for SCSI, Ethernet and serial ports later on.
98 bool "HP9000/300 and HP9000/400 support"
100 select MMU_MOTOROLA if MMU
101 select LEGACY_TIMER_TICK
103 This option enables support for the HP9000/300 and HP9000/400 series
104 of workstations. Support for these machines is still somewhat
105 experimental. If you plan to try to use the kernel on such a machine
107 Everybody else says N.
112 select LEGACY_TIMER_TICK
113 select MMU_MOTOROLA if MMU
116 This option enables support for the Sun 3x series of workstations.
117 Be warned that this support is very experimental.
118 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
119 General Linux information on the Sun 3x series (now discontinued)
120 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
122 If you don't want to compile a kernel for a Sun 3x, say N.
125 bool "Q40/Q60 support"
127 select MMU_MOTOROLA if MMU
128 select LEGACY_TIMER_TICK
130 The Q40 is a Motorola 68040-based successor to the Sinclair QL
131 manufactured in Germany. There is an official Q40 home page at
132 <http://www.q40.de/>. This option enables support for the Q40 and
133 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
139 depends on !MMU_MOTOROLA
140 select MMU_SUN3 if MMU
141 select LEGACY_TIMER_TICK
145 This option enables support for the Sun 3 series of workstations
146 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
147 that all other hardware types must be disabled, as Sun 3 kernels
148 are incompatible with all other m68k targets (including Sun 3x!).
150 If you don't want to compile a kernel exclusively for a Sun 3, say N.
153 bool "Virtual M68k Machine support"
155 select GENERIC_CLOCKEVENTS
157 select GOLDFISH_TIMER
160 select MMU_MOTOROLA if MMU
162 select RTC_DRV_GOLDFISH
166 This options enable a pure virtual machine based on m68k,
167 VIRTIO MMIO devices and GOLDFISH interfaces (TTY, RTC, PIC)
173 bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support"
178 Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII.
181 bool "(X)Copilot support"
184 Support the bugs of Xcopilot.
187 bool "uCsimm module support"
191 Support for the Arcturus Networks uCsimm module.
194 bool "uDsimm module support"
198 Support for the Arcturus Networks uDsimm module.
201 bool "DragenEngine II board support"
205 Support for the DragenEngine II board.
207 config DIRECT_IO_ACCESS
208 bool "Allow user to access IO directly"
209 depends on (UCSIMM || UCDIMM || DRAGEN2)
211 Disable the CPU internal registers protection in user mode,
212 to allow a user application to read/write them.
215 bool "Initialize LCD"
216 depends on (UCSIMM || UCDIMM || DRAGEN2)
218 Initialize the LCD controller of the 68x328 processor.
220 config MEMORY_RESERVE
221 int "Memory reservation (MiB)"
222 depends on (UCSIMM || UCDIMM)
225 Reserve certain memory regions on 68x328 based boards.
230 bool "Arnewsh 5206 board support"
233 Support for the Arnewsh 5206 board.
236 bool "Motorola M5206eC3 board support"
239 Support for the Motorola M5206eC3 board.
242 bool "Motorola M5206eLITE board support"
245 Support for the Motorola M5206eLITE board.
248 bool "Freescale M5235EVB support"
251 Support for the Freescale M5235EVB board.
254 bool "Motorola M5249C3 board support"
257 Support for the Motorola M5249C3 board.
260 bool "Motorola M5272C3 board support"
263 Support for the Motorola M5272C3 board.
266 bool "Intec Automation Inc. WildFire board support"
269 Support for the Intec Automation Inc. WildFire.
272 bool "Intec Automation Inc. WildFire module support"
275 Support for the Intec Automation Inc. WildFire module.
278 bool "Arnewsh 5307 board support"
281 Support for the Arnewsh 5307 board.
284 bool "Motorola M5307C3 board support"
287 Support for the Motorola M5307C3 board.
290 bool "SnapGear SecureEdge/MP3 platform support"
293 Support for the SnapGear SecureEdge/MP3 platform.
296 bool "Motorola M5407C3 board support"
299 Support for the Motorola M5407C3 board.
302 bool "Sysam AMCORE board support"
305 Support for the Sysam AMCORE open-hardware generic board.
308 bool "Sysam stmark2 board support"
311 Support for the Sysam stmark2 open-hardware generic board.
314 bool "FireBee board support"
317 Support for the FireBee ColdFire 5475 based board.
320 bool "Feith CLEOPATRA board support"
321 depends on (M5307 || M5407)
323 Support for the Feith Cleopatra boards.
326 bool "Feith CANCam board support"
329 Support for the Feith CANCam board.
332 bool "Feith SCALES board support"
335 Support for the Feith SCALES board.
338 bool "SecureEdge/NETtel board support"
339 depends on (M5206e || M5272 || M5307)
341 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
344 bool "Netburner MOD-5272 board support"
347 Support for the Netburner MOD-5272 board.
351 comment "Machine Options"
354 bool "Support for U-Boot command line parameters"
357 If you say Y here kernel will try to collect command
358 line parameters from the initial u-boot stack.
361 bool "Use 4Kb for kernel stacks instead of 8Kb"
364 If you say Y here the kernel will use a 4Kb stacksize for the
365 kernel stack attached to each process/thread. This facilitates
366 running more threads on a system and also reduces the pressure
367 on the VM subsystem for higher order allocations.
369 comment "RAM configuration"
372 hex "Address of the base of RAM"
375 Define the address that RAM starts at. On many platforms this is
376 0, the base of the address space. And this is the default. Some
377 platforms choose to setup their RAM at other addresses within the
378 processor address space.
381 hex "Size of RAM (in bytes), or 0 for automatic"
384 Define the size of the system RAM. If you select 0 then the
385 kernel will try to probe the RAM size at runtime. This is not
386 supported on all CPU types.
389 hex "Address of the base of system vectors"
392 Define the address of the system vectors. Commonly this is
393 put at the start of RAM, but it doesn't have to be. On ColdFire
394 platforms this address is programmed into the VBR register, thus
395 actually setting the address to use.
398 hex "Address of the MBAR (internal peripherals)"
402 Define the address of the internal system peripherals. This value
403 is set in the processors MBAR register. This is generally setup by
404 the boot loader, and will not be written by the kernel. By far most
405 ColdFire boards use the default 0x10000000 value, so if unsure then
409 hex "Address of the IPSBAR (internal peripherals)"
411 depends on HAVE_IPSBAR
413 Define the address of the internal system peripherals. This value
414 is set in the processors IPSBAR register. This is generally setup by
415 the boot loader, and will not be written by the kernel. By far most
416 ColdFire boards use the default 0x40000000 value, so if unsure then
420 hex "Address of the base of kernel code"
423 Typically on m68k systems the kernel will not start at the base
424 of RAM, but usually some small offset from it. Define the start
425 address of the kernel here. The most common setup will have the
426 processor vectors at the base of RAM and then the start of the
427 kernel. On some platforms some RAM is reserved for boot loaders
428 and the kernel starts after that. The 0x400 default was based on
429 a system with the RAM based at address 0, and leaving enough room
430 for the theoretical maximum number of 256 vectors.
432 comment "ROM configuration"
435 bool "Specify ROM linker regions"
437 Define a ROM region for the linker script. This creates a kernel
438 that can be stored in flash, with possibly the text, and data
439 regions being copied out to RAM at startup.
442 hex "Address of the base of ROM device"
446 Define the address that the ROM region starts at. Some platforms
447 use this to set their chip select region accordingly for the boot
451 hex "Address of the base of the ROM vectors"
455 This is almost always the same as the base of the ROM. Since on all
456 68000 type variants the vectors are at the base of the boot device
460 hex "Address of the base of system image in ROM"
464 Define the start address of the system image in ROM. Commonly this
465 is strait after the ROM vectors.
468 hex "Size of the ROM device"
472 Size of the ROM device. On some platforms this is used to setup
473 the chip select that controls the boot ROM device.
476 prompt "Kernel executes from"
478 Choose the memory type that the kernel will be running in.
483 The kernel will be resident in RAM when running.
489 The kernel will be resident in FLASH/ROM when running. This is
490 often referred to as Execute-in-Place (XIP), since the kernel
491 code executes from the position it is stored in the FLASH/ROM.