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
167 This options enable a pure virtual machine based on m68k,
168 VIRTIO MMIO devices and GOLDFISH interfaces (TTY, RTC, PIC).
174 bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support"
179 Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII.
182 bool "(X)Copilot support"
185 Support the bugs of Xcopilot.
188 bool "uCsimm module support"
192 Support for the Arcturus Networks uCsimm module.
195 bool "uDsimm module support"
199 Support for the Arcturus Networks uDsimm module.
202 bool "DragenEngine II board support"
206 Support for the DragenEngine II board.
208 config DIRECT_IO_ACCESS
209 bool "Allow user to access IO directly"
210 depends on (UCSIMM || UCDIMM || DRAGEN2)
212 Disable the CPU internal registers protection in user mode,
213 to allow a user application to read/write them.
216 bool "Initialize LCD"
217 depends on (UCSIMM || UCDIMM || DRAGEN2)
219 Initialize the LCD controller of the 68x328 processor.
221 config MEMORY_RESERVE
222 int "Memory reservation (MiB)"
223 depends on (UCSIMM || UCDIMM)
226 Reserve certain memory regions on 68x328 based boards.
231 bool "Arnewsh 5206 board support"
234 Support for the Arnewsh 5206 board.
237 bool "Motorola M5206eC3 board support"
240 Support for the Motorola M5206eC3 board.
243 bool "Motorola M5206eLITE board support"
246 Support for the Motorola M5206eLITE board.
249 bool "Freescale M5235EVB support"
252 Support for the Freescale M5235EVB board.
255 bool "Motorola M5249C3 board support"
258 Support for the Motorola M5249C3 board.
261 bool "Motorola M5272C3 board support"
264 Support for the Motorola M5272C3 board.
267 bool "Intec Automation Inc. WildFire board support"
270 Support for the Intec Automation Inc. WildFire.
273 bool "Intec Automation Inc. WildFire module support"
276 Support for the Intec Automation Inc. WildFire module.
279 bool "Arnewsh 5307 board support"
282 Support for the Arnewsh 5307 board.
285 bool "Motorola M5307C3 board support"
288 Support for the Motorola M5307C3 board.
291 bool "SnapGear SecureEdge/MP3 platform support"
294 Support for the SnapGear SecureEdge/MP3 platform.
297 bool "Motorola M5407C3 board support"
300 Support for the Motorola M5407C3 board.
303 bool "Sysam AMCORE board support"
306 Support for the Sysam AMCORE open-hardware generic board.
309 bool "Sysam stmark2 board support"
312 Support for the Sysam stmark2 open-hardware generic board.
315 bool "FireBee board support"
318 Support for the FireBee ColdFire 5475 based board.
321 bool "Feith CLEOPATRA board support"
322 depends on (M5307 || M5407)
324 Support for the Feith Cleopatra boards.
327 bool "Feith CANCam board support"
330 Support for the Feith CANCam board.
333 bool "Feith SCALES board support"
336 Support for the Feith SCALES board.
339 bool "SecureEdge/NETtel board support"
340 depends on (M5206e || M5272 || M5307)
342 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
345 bool "Netburner MOD-5272 board support"
348 Support for the Netburner MOD-5272 board.
352 comment "Machine Options"
355 bool "Support for U-Boot command line parameters"
358 If you say Y here kernel will try to collect command
359 line parameters from the initial u-boot stack.
362 bool "Use 4Kb for kernel stacks instead of 8Kb"
365 If you say Y here the kernel will use a 4Kb stacksize for the
366 kernel stack attached to each process/thread. This facilitates
367 running more threads on a system and also reduces the pressure
368 on the VM subsystem for higher order allocations.
370 comment "RAM configuration"
373 hex "Address of the base of RAM"
376 Define the address that RAM starts at. On many platforms this is
377 0, the base of the address space. And this is the default. Some
378 platforms choose to setup their RAM at other addresses within the
379 processor address space.
382 hex "Size of RAM (in bytes), or 0 for automatic"
385 Define the size of the system RAM. If you select 0 then the
386 kernel will try to probe the RAM size at runtime. This is not
387 supported on all CPU types.
390 hex "Address of the base of system vectors"
393 Define the address of the system vectors. Commonly this is
394 put at the start of RAM, but it doesn't have to be. On ColdFire
395 platforms this address is programmed into the VBR register, thus
396 actually setting the address to use.
399 hex "Address of the MBAR (internal peripherals)"
403 Define the address of the internal system peripherals. This value
404 is set in the processors MBAR register. This is generally setup by
405 the boot loader, and will not be written by the kernel. By far most
406 ColdFire boards use the default 0x10000000 value, so if unsure then
410 hex "Address of the IPSBAR (internal peripherals)"
412 depends on HAVE_IPSBAR
414 Define the address of the internal system peripherals. This value
415 is set in the processors IPSBAR register. This is generally setup by
416 the boot loader, and will not be written by the kernel. By far most
417 ColdFire boards use the default 0x40000000 value, so if unsure then
421 hex "Address of the base of kernel code"
424 Typically on m68k systems the kernel will not start at the base
425 of RAM, but usually some small offset from it. Define the start
426 address of the kernel here. The most common setup will have the
427 processor vectors at the base of RAM and then the start of the
428 kernel. On some platforms some RAM is reserved for boot loaders
429 and the kernel starts after that. The 0x400 default was based on
430 a system with the RAM based at address 0, and leaving enough room
431 for the theoretical maximum number of 256 vectors.
433 comment "ROM configuration"
436 bool "Specify ROM linker regions"
438 Define a ROM region for the linker script. This creates a kernel
439 that can be stored in flash, with possibly the text, and data
440 regions being copied out to RAM at startup.
443 hex "Address of the base of ROM device"
447 Define the address that the ROM region starts at. Some platforms
448 use this to set their chip select region accordingly for the boot
452 hex "Address of the base of the ROM vectors"
456 This is almost always the same as the base of the ROM. Since on all
457 68000 type variants the vectors are at the base of the boot device
461 hex "Address of the base of system image in ROM"
465 Define the start address of the system image in ROM. Commonly this
466 is strait after the ROM vectors.
469 hex "Size of the ROM device"
473 Size of the ROM device. On some platforms this is used to setup
474 the chip select that controls the boot ROM device.
477 prompt "Kernel executes from"
479 Choose the memory type that the kernel will be running in.
484 The kernel will be resident in RAM when running.
490 The kernel will be resident in FLASH/ROM when running. This is
491 often referred to as Execute-in-Place (XIP), since the kernel
492 code executes from the position it is stored in the FLASH/ROM.
496 endif # !MMU || COLDFIRE