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 (yes, there is experimental support now, at least for part
36 Say N unless you're willing to code the remaining necessary support.
42 select MMU_MOTOROLA if MMU
44 Say Y here if you want to run Linux on an MC680x0-based Apollo
45 Domain workstation such as the DN3500.
48 bool "VME (Motorola and BVM) support"
50 select MMU_MOTOROLA if MMU
52 Say Y here if you want to build a kernel for a 680x0 based VME
53 board. Boards currently supported include Motorola boards MVME147,
54 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
55 BVME6000 boards from BVM Ltd are also supported.
58 bool "MVME147 support"
62 Say Y to include support for early Motorola VME boards. This will
63 build a kernel which can run on MVME147 single-board computers. If
64 you select this option you will have to select the appropriate
65 drivers for SCSI, Ethernet and serial ports later on.
68 bool "MVME162, 166 and 167 support"
72 Say Y to include support for Motorola VME boards. This will build a
73 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
74 MVME177 boards. If you select this option you will have to select
75 the appropriate drivers for SCSI, Ethernet and serial ports later
79 bool "BVME4000 and BVME6000 support"
83 Say Y to include support for VME boards from BVM Ltd. This will
84 build a kernel which can run on BVME4000 and BVME6000 boards. If
85 you select this option you will have to select the appropriate
86 drivers for SCSI, Ethernet and serial ports later on.
89 bool "HP9000/300 and HP9000/400 support"
91 select MMU_MOTOROLA if MMU
93 This option enables support for the HP9000/300 and HP9000/400 series
94 of workstations. Support for these machines is still somewhat
95 experimental. If you plan to try to use the kernel on such a machine
97 Everybody else says N.
102 select LEGACY_TIMER_TICK
103 select MMU_MOTOROLA if MMU
106 This option enables support for the Sun 3x series of workstations.
107 Be warned that this support is very experimental.
108 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
109 General Linux information on the Sun 3x series (now discontinued)
110 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
112 If you don't want to compile a kernel for a Sun 3x, say N.
115 bool "Q40/Q60 support"
117 select MMU_MOTOROLA if MMU
119 The Q40 is a Motorola 68040-based successor to the Sinclair QL
120 manufactured in Germany. There is an official Q40 home page at
121 <http://www.q40.de/>. This option enables support for the Q40 and
122 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
128 depends on !MMU_MOTOROLA
129 select MMU_SUN3 if MMU
130 select LEGACY_TIMER_TICK
134 This option enables support for the Sun 3 series of workstations
135 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
136 that all other hardware types must be disabled, as Sun 3 kernels
137 are incompatible with all other m68k targets (including Sun 3x!).
139 If you don't want to compile a kernel exclusively for a Sun 3, say N.
147 bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support"
151 Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII.
154 bool "(X)Copilot support"
157 Support the bugs of Xcopilot.
160 bool "uCsimm module support"
163 Support for the Arcturus Networks uCsimm module.
166 bool "uDsimm module support"
169 Support for the Arcturus Networks uDsimm module.
172 bool "DragenEngine II board support"
175 Support for the DragenEngine II board.
177 config DIRECT_IO_ACCESS
178 bool "Allow user to access IO directly"
179 depends on (UCSIMM || UCDIMM || DRAGEN2)
181 Disable the CPU internal registers protection in user mode,
182 to allow a user application to read/write them.
185 bool "Initialize LCD"
186 depends on (UCSIMM || UCDIMM || DRAGEN2)
188 Initialize the LCD controller of the 68x328 processor.
190 config MEMORY_RESERVE
191 int "Memory reservation (MiB)"
192 depends on (UCSIMM || UCDIMM)
194 Reserve certain memory regions on 68x328 based boards.
197 bool "Arnewsh 5206 board support"
200 Support for the Arnewsh 5206 board.
203 bool "Motorola M5206eC3 board support"
206 Support for the Motorola M5206eC3 board.
209 bool "Motorola M5206eLITE board support"
212 Support for the Motorola M5206eLITE board.
215 bool "Freescale M5235EVB support"
218 Support for the Freescale M5235EVB board.
221 bool "Motorola M5249C3 board support"
224 Support for the Motorola M5249C3 board.
227 bool "Motorola M5272C3 board support"
230 Support for the Motorola M5272C3 board.
233 bool "Intec Automation Inc. WildFire board support"
236 Support for the Intec Automation Inc. WildFire.
239 bool "Intec Automation Inc. WildFire module support"
242 Support for the Intec Automation Inc. WildFire module.
245 bool "Arnewsh 5307 board support"
248 Support for the Arnewsh 5307 board.
251 bool "Motorola M5307C3 board support"
254 Support for the Motorola M5307C3 board.
257 bool "SnapGear SecureEdge/MP3 platform support"
260 Support for the SnapGear SecureEdge/MP3 platform.
263 bool "Motorola M5407C3 board support"
266 Support for the Motorola M5407C3 board.
269 bool "Sysam AMCORE board support"
272 Support for the Sysam AMCORE open-hardware generic board.
275 bool "Sysam stmark2 board support"
278 Support for the Sysam stmark2 open-hardware generic board.
281 bool "FireBee board support"
284 Support for the FireBee ColdFire 5475 based board.
287 bool "Feith CLEOPATRA board support"
288 depends on (M5307 || M5407)
290 Support for the Feith Cleopatra boards.
293 bool "Feith CANCam board support"
296 Support for the Feith CANCam board.
299 bool "Feith SCALES board support"
302 Support for the Feith SCALES board.
305 bool "SecureEdge/NETtel board support"
306 depends on (M5206e || M5272 || M5307)
308 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
311 bool "Netburner MOD-5272 board support"
314 Support for the Netburner MOD-5272 board.
318 comment "Machine Options"
321 bool "Support for U-Boot command line parameters"
323 If you say Y here kernel will try to collect command
324 line parameters from the initial u-boot stack.
327 bool "Use 4Kb for kernel stacks instead of 8Kb"
330 If you say Y here the kernel will use a 4Kb stacksize for the
331 kernel stack attached to each process/thread. This facilitates
332 running more threads on a system and also reduces the pressure
333 on the VM subsystem for higher order allocations.
335 comment "RAM configuration"
338 hex "Address of the base of RAM"
341 Define the address that RAM starts at. On many platforms this is
342 0, the base of the address space. And this is the default. Some
343 platforms choose to setup their RAM at other addresses within the
344 processor address space.
347 hex "Size of RAM (in bytes), or 0 for automatic"
350 Define the size of the system RAM. If you select 0 then the
351 kernel will try to probe the RAM size at runtime. This is not
352 supported on all CPU types.
355 hex "Address of the base of system vectors"
358 Define the address of the system vectors. Commonly this is
359 put at the start of RAM, but it doesn't have to be. On ColdFire
360 platforms this address is programmed into the VBR register, thus
361 actually setting the address to use.
364 hex "Address of the MBAR (internal peripherals)"
368 Define the address of the internal system peripherals. This value
369 is set in the processors MBAR register. This is generally setup by
370 the boot loader, and will not be written by the kernel. By far most
371 ColdFire boards use the default 0x10000000 value, so if unsure then
375 hex "Address of the IPSBAR (internal peripherals)"
377 depends on HAVE_IPSBAR
379 Define the address of the internal system peripherals. This value
380 is set in the processors IPSBAR register. This is generally setup by
381 the boot loader, and will not be written by the kernel. By far most
382 ColdFire boards use the default 0x40000000 value, so if unsure then
386 hex "Address of the base of kernel code"
389 Typically on m68k systems the kernel will not start at the base
390 of RAM, but usually some small offset from it. Define the start
391 address of the kernel here. The most common setup will have the
392 processor vectors at the base of RAM and then the start of the
393 kernel. On some platforms some RAM is reserved for boot loaders
394 and the kernel starts after that. The 0x400 default was based on
395 a system with the RAM based at address 0, and leaving enough room
396 for the theoretical maximum number of 256 vectors.
398 comment "ROM configuration"
401 bool "Specify ROM linker regions"
403 Define a ROM region for the linker script. This creates a kernel
404 that can be stored in flash, with possibly the text, and data
405 regions being copied out to RAM at startup.
408 hex "Address of the base of ROM device"
412 Define the address that the ROM region starts at. Some platforms
413 use this to set their chip select region accordingly for the boot
417 hex "Address of the base of the ROM vectors"
421 This is almost always the same as the base of the ROM. Since on all
422 68000 type variants the vectors are at the base of the boot device
426 hex "Address of the base of system image in ROM"
430 Define the start address of the system image in ROM. Commonly this
431 is strait after the ROM vectors.
434 hex "Size of the ROM device"
438 Size of the ROM device. On some platforms this is used to setup
439 the chip select that controls the boot ROM device.
442 prompt "Kernel executes from"
444 Choose the memory type that the kernel will be running in.
449 The kernel will be resident in RAM when running.
454 The kernel will be resident in FLASH/ROM when running. This is
455 often referred to as Execute-in-Place (XIP), since the kernel
456 code executes from the position it is stored in the FLASH/ROM.