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.
29 bool "Macintosh support"
31 select MMU_MOTOROLA if MMU
32 select HAVE_ARCH_NVRAM_OPS
33 select LEGACY_TIMER_TICK
35 This option enables support for the Apple Macintosh series of
36 computers. If you plan to use this kernel on a Mac, say Y here and
37 browse the documentation available at <http://www.mac.linux-m68k.org/>;
43 select MMU_MOTOROLA if MMU
44 select LEGACY_TIMER_TICK
46 Say Y here if you want to run Linux on an MC680x0-based Apollo
47 Domain workstation such as the DN3500.
50 bool "VME (Motorola and BVM) support"
52 select MMU_MOTOROLA if MMU
54 Say Y here if you want to build a kernel for a 680x0 based VME
55 board. Boards currently supported include Motorola boards MVME147,
56 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
57 BVME6000 boards from BVM Ltd are also supported.
60 bool "MVME147 support"
63 select LEGACY_TIMER_TICK
65 Say Y to include support for early Motorola VME boards. This will
66 build a kernel which can run on MVME147 single-board computers. If
67 you select this option you will have to select the appropriate
68 drivers for SCSI, Ethernet and serial ports later on.
71 bool "MVME162, 166 and 167 support"
74 select LEGACY_TIMER_TICK
76 Say Y to include support for Motorola VME boards. This will build a
77 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
78 MVME177 boards. If you select this option you will have to select
79 the appropriate drivers for SCSI, Ethernet and serial ports later
83 bool "BVME4000 and BVME6000 support"
86 select LEGACY_TIMER_TICK
88 Say Y to include support for VME boards from BVM Ltd. This will
89 build a kernel which can run on BVME4000 and BVME6000 boards. If
90 you select this option you will have to select the appropriate
91 drivers for SCSI, Ethernet and serial ports later on.
94 bool "HP9000/300 and HP9000/400 support"
96 select MMU_MOTOROLA if MMU
97 select LEGACY_TIMER_TICK
99 This option enables support for the HP9000/300 and HP9000/400 series
100 of workstations. Support for these machines is still somewhat
101 experimental. If you plan to try to use the kernel on such a machine
103 Everybody else says N.
108 select LEGACY_TIMER_TICK
109 select MMU_MOTOROLA if MMU
112 This option enables support for the Sun 3x series of workstations.
113 Be warned that this support is very experimental.
114 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
115 General Linux information on the Sun 3x series (now discontinued)
116 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
118 If you don't want to compile a kernel for a Sun 3x, say N.
121 bool "Q40/Q60 support"
123 select MMU_MOTOROLA if MMU
124 select LEGACY_TIMER_TICK
126 The Q40 is a Motorola 68040-based successor to the Sinclair QL
127 manufactured in Germany. There is an official Q40 home page at
128 <http://www.q40.de/>. This option enables support for the Q40 and
129 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
135 depends on !MMU_MOTOROLA
136 select MMU_SUN3 if MMU
137 select LEGACY_TIMER_TICK
141 This option enables support for the Sun 3 series of workstations
142 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
143 that all other hardware types must be disabled, as Sun 3 kernels
144 are incompatible with all other m68k targets (including Sun 3x!).
146 If you don't want to compile a kernel exclusively for a Sun 3, say N.
154 bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support"
158 Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII.
161 bool "(X)Copilot support"
164 Support the bugs of Xcopilot.
167 bool "uCsimm module support"
170 Support for the Arcturus Networks uCsimm module.
173 bool "uDsimm module support"
176 Support for the Arcturus Networks uDsimm module.
179 bool "DragenEngine II board support"
182 Support for the DragenEngine II board.
184 config DIRECT_IO_ACCESS
185 bool "Allow user to access IO directly"
186 depends on (UCSIMM || UCDIMM || DRAGEN2)
188 Disable the CPU internal registers protection in user mode,
189 to allow a user application to read/write them.
192 bool "Initialize LCD"
193 depends on (UCSIMM || UCDIMM || DRAGEN2)
195 Initialize the LCD controller of the 68x328 processor.
197 config MEMORY_RESERVE
198 int "Memory reservation (MiB)"
199 depends on (UCSIMM || UCDIMM)
201 Reserve certain memory regions on 68x328 based boards.
204 bool "Arnewsh 5206 board support"
207 Support for the Arnewsh 5206 board.
210 bool "Motorola M5206eC3 board support"
213 Support for the Motorola M5206eC3 board.
216 bool "Motorola M5206eLITE board support"
219 Support for the Motorola M5206eLITE board.
222 bool "Freescale M5235EVB support"
225 Support for the Freescale M5235EVB board.
228 bool "Motorola M5249C3 board support"
231 Support for the Motorola M5249C3 board.
234 bool "Motorola M5272C3 board support"
237 Support for the Motorola M5272C3 board.
240 bool "Intec Automation Inc. WildFire board support"
243 Support for the Intec Automation Inc. WildFire.
246 bool "Intec Automation Inc. WildFire module support"
249 Support for the Intec Automation Inc. WildFire module.
252 bool "Arnewsh 5307 board support"
255 Support for the Arnewsh 5307 board.
258 bool "Motorola M5307C3 board support"
261 Support for the Motorola M5307C3 board.
264 bool "SnapGear SecureEdge/MP3 platform support"
267 Support for the SnapGear SecureEdge/MP3 platform.
270 bool "Motorola M5407C3 board support"
273 Support for the Motorola M5407C3 board.
276 bool "Sysam AMCORE board support"
279 Support for the Sysam AMCORE open-hardware generic board.
282 bool "Sysam stmark2 board support"
285 Support for the Sysam stmark2 open-hardware generic board.
288 bool "FireBee board support"
291 Support for the FireBee ColdFire 5475 based board.
294 bool "Feith CLEOPATRA board support"
295 depends on (M5307 || M5407)
297 Support for the Feith Cleopatra boards.
300 bool "Feith CANCam board support"
303 Support for the Feith CANCam board.
306 bool "Feith SCALES board support"
309 Support for the Feith SCALES board.
312 bool "SecureEdge/NETtel board support"
313 depends on (M5206e || M5272 || M5307)
315 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
318 bool "Netburner MOD-5272 board support"
321 Support for the Netburner MOD-5272 board.
325 comment "Machine Options"
328 bool "Support for U-Boot command line parameters"
330 If you say Y here kernel will try to collect command
331 line parameters from the initial u-boot stack.
334 bool "Use 4Kb for kernel stacks instead of 8Kb"
337 If you say Y here the kernel will use a 4Kb stacksize for the
338 kernel stack attached to each process/thread. This facilitates
339 running more threads on a system and also reduces the pressure
340 on the VM subsystem for higher order allocations.
342 comment "RAM configuration"
345 hex "Address of the base of RAM"
348 Define the address that RAM starts at. On many platforms this is
349 0, the base of the address space. And this is the default. Some
350 platforms choose to setup their RAM at other addresses within the
351 processor address space.
354 hex "Size of RAM (in bytes), or 0 for automatic"
357 Define the size of the system RAM. If you select 0 then the
358 kernel will try to probe the RAM size at runtime. This is not
359 supported on all CPU types.
362 hex "Address of the base of system vectors"
365 Define the address of the system vectors. Commonly this is
366 put at the start of RAM, but it doesn't have to be. On ColdFire
367 platforms this address is programmed into the VBR register, thus
368 actually setting the address to use.
371 hex "Address of the MBAR (internal peripherals)"
375 Define the address of the internal system peripherals. This value
376 is set in the processors MBAR 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 0x10000000 value, so if unsure then
382 hex "Address of the IPSBAR (internal peripherals)"
384 depends on HAVE_IPSBAR
386 Define the address of the internal system peripherals. This value
387 is set in the processors IPSBAR register. This is generally setup by
388 the boot loader, and will not be written by the kernel. By far most
389 ColdFire boards use the default 0x40000000 value, so if unsure then
393 hex "Address of the base of kernel code"
396 Typically on m68k systems the kernel will not start at the base
397 of RAM, but usually some small offset from it. Define the start
398 address of the kernel here. The most common setup will have the
399 processor vectors at the base of RAM and then the start of the
400 kernel. On some platforms some RAM is reserved for boot loaders
401 and the kernel starts after that. The 0x400 default was based on
402 a system with the RAM based at address 0, and leaving enough room
403 for the theoretical maximum number of 256 vectors.
405 comment "ROM configuration"
408 bool "Specify ROM linker regions"
410 Define a ROM region for the linker script. This creates a kernel
411 that can be stored in flash, with possibly the text, and data
412 regions being copied out to RAM at startup.
415 hex "Address of the base of ROM device"
419 Define the address that the ROM region starts at. Some platforms
420 use this to set their chip select region accordingly for the boot
424 hex "Address of the base of the ROM vectors"
428 This is almost always the same as the base of the ROM. Since on all
429 68000 type variants the vectors are at the base of the boot device
433 hex "Address of the base of system image in ROM"
437 Define the start address of the system image in ROM. Commonly this
438 is strait after the ROM vectors.
441 hex "Size of the ROM device"
445 Size of the ROM device. On some platforms this is used to setup
446 the chip select that controls the boot ROM device.
449 prompt "Kernel executes from"
451 Choose the memory type that the kernel will be running in.
456 The kernel will be resident in RAM when running.
461 The kernel will be resident in FLASH/ROM when running. This is
462 often referred to as Execute-in-Place (XIP), since the kernel
463 code executes from the position it is stored in the FLASH/ROM.