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.
30 bool "Macintosh support"
32 select MMU_MOTOROLA if MMU
33 select HAVE_ARCH_NVRAM_OPS
35 This option enables support for the Apple Macintosh series of
36 computers (yes, there is experimental support now, at least for part
39 Say N unless you're willing to code the remaining necessary support.
45 select MMU_MOTOROLA if MMU
47 Say Y here if you want to run Linux on an MC680x0-based Apollo
48 Domain workstation such as the DN3500.
51 bool "VME (Motorola and BVM) support"
53 select MMU_MOTOROLA if MMU
55 Say Y here if you want to build a kernel for a 680x0 based VME
56 board. Boards currently supported include Motorola boards MVME147,
57 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
58 BVME6000 boards from BVM Ltd are also supported.
61 bool "MVME147 support"
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"
75 Say Y to include support for Motorola VME boards. This will build a
76 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
77 MVME177 boards. If you select this option you will have to select
78 the appropriate drivers for SCSI, Ethernet and serial ports later
82 bool "BVME4000 and BVME6000 support"
86 Say Y to include support for VME boards from BVM Ltd. This will
87 build a kernel which can run on BVME4000 and BVME6000 boards. If
88 you select this option you will have to select the appropriate
89 drivers for SCSI, Ethernet and serial ports later on.
92 bool "HP9000/300 and HP9000/400 support"
94 select MMU_MOTOROLA if MMU
96 This option enables support for the HP9000/300 and HP9000/400 series
97 of workstations. Support for these machines is still somewhat
98 experimental. If you plan to try to use the kernel on such a machine
100 Everybody else says N.
105 select MMU_MOTOROLA if MMU
108 This option enables support for the Sun 3x series of workstations.
109 Be warned that this support is very experimental.
110 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
111 General Linux information on the Sun 3x series (now discontinued)
112 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
114 If you don't want to compile a kernel for a Sun 3x, say N.
117 bool "Q40/Q60 support"
119 select MMU_MOTOROLA if MMU
121 The Q40 is a Motorola 68040-based successor to the Sinclair QL
122 manufactured in Germany. There is an official Q40 home page at
123 <http://www.q40.de/>. This option enables support for the Q40 and
124 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
130 depends on !MMU_MOTOROLA
131 select MMU_SUN3 if MMU
135 This option enables support for the Sun 3 series of workstations
136 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
137 that all other hardware types must be disabled, as Sun 3 kernels
138 are incompatible with all other m68k targets (including Sun 3x!).
140 If you don't want to compile a kernel exclusively for a Sun 3, say N.
148 bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support"
152 Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII.
155 bool "(X)Copilot support"
158 Support the bugs of Xcopilot.
161 bool "uCsimm module support"
164 Support for the Arcturus Networks uCsimm module.
167 bool "uDsimm module support"
170 Support for the Arcturus Networks uDsimm module.
173 bool "DragenEngine II board support"
176 Support for the DragenEngine II board.
178 config DIRECT_IO_ACCESS
179 bool "Allow user to access IO directly"
180 depends on (UCSIMM || UCDIMM || DRAGEN2)
182 Disable the CPU internal registers protection in user mode,
183 to allow a user application to read/write them.
186 bool "Initialize LCD"
187 depends on (UCSIMM || UCDIMM || DRAGEN2)
189 Initialize the LCD controller of the 68x328 processor.
191 config MEMORY_RESERVE
192 int "Memory reservation (MiB)"
193 depends on (UCSIMM || UCDIMM)
196 Reserve certain memory regions on 68x328 based boards.
199 bool "Arnewsh 5206 board support"
202 Support for the Arnewsh 5206 board.
205 bool "Motorola M5206eC3 board support"
208 Support for the Motorola M5206eC3 board.
211 bool "Motorola M5206eLITE board support"
214 Support for the Motorola M5206eLITE board.
217 bool "Freescale M5235EVB support"
220 Support for the Freescale M5235EVB board.
223 bool "Motorola M5249C3 board support"
226 Support for the Motorola M5249C3 board.
229 bool "Motorola M5272C3 board support"
232 Support for the Motorola M5272C3 board.
235 bool "Intec Automation Inc. WildFire board support"
238 Support for the Intec Automation Inc. WildFire.
241 bool "Intec Automation Inc. WildFire module support"
244 Support for the Intec Automation Inc. WildFire module.
247 bool "Arnewsh 5307 board support"
250 Support for the Arnewsh 5307 board.
253 bool "Motorola M5307C3 board support"
256 Support for the Motorola M5307C3 board.
259 bool "SnapGear SecureEdge/MP3 platform support"
262 Support for the SnapGear SecureEdge/MP3 platform.
265 bool "Motorola M5407C3 board support"
268 Support for the Motorola M5407C3 board.
271 bool "Sysam AMCORE board support"
274 Support for the Sysam AMCORE open-hardware generic board.
277 bool "Sysam stmark2 board support"
280 Support for the Sysam stmark2 open-hardware generic board.
283 bool "FireBee board support"
286 Support for the FireBee ColdFire 5475 based board.
289 bool "Feith CLEOPATRA board support"
290 depends on (M5307 || M5407)
292 Support for the Feith Cleopatra boards.
295 bool "Feith CANCam board support"
298 Support for the Feith CANCam board.
301 bool "Feith SCALES board support"
304 Support for the Feith SCALES board.
307 bool "SecureEdge/NETtel board support"
308 depends on (M5206e || M5272 || M5307)
310 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
313 bool "Netburner MOD-5272 board support"
316 Support for the Netburner MOD-5272 board.
320 comment "Machine Options"
323 bool "Support for U-Boot command line parameters"
326 If you say Y here kernel will try to collect command
327 line parameters from the initial u-boot stack.
330 bool "Use 4Kb for kernel stacks instead of 8Kb"
333 If you say Y here the kernel will use a 4Kb stacksize for the
334 kernel stack attached to each process/thread. This facilitates
335 running more threads on a system and also reduces the pressure
336 on the VM subsystem for higher order allocations.
338 comment "RAM configuration"
341 hex "Address of the base of RAM"
344 Define the address that RAM starts at. On many platforms this is
345 0, the base of the address space. And this is the default. Some
346 platforms choose to setup their RAM at other addresses within the
347 processor address space.
350 hex "Size of RAM (in bytes), or 0 for automatic"
353 Define the size of the system RAM. If you select 0 then the
354 kernel will try to probe the RAM size at runtime. This is not
355 supported on all CPU types.
358 hex "Address of the base of system vectors"
361 Define the address of the system vectors. Commonly this is
362 put at the start of RAM, but it doesn't have to be. On ColdFire
363 platforms this address is programmed into the VBR register, thus
364 actually setting the address to use.
367 hex "Address of the MBAR (internal peripherals)"
371 Define the address of the internal system peripherals. This value
372 is set in the processors MBAR register. This is generally setup by
373 the boot loader, and will not be written by the kernel. By far most
374 ColdFire boards use the default 0x10000000 value, so if unsure then
378 hex "Address of the IPSBAR (internal peripherals)"
380 depends on HAVE_IPSBAR
382 Define the address of the internal system peripherals. This value
383 is set in the processors IPSBAR 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 0x40000000 value, so if unsure then
389 hex "Address of the base of kernel code"
392 Typically on m68k systems the kernel will not start at the base
393 of RAM, but usually some small offset from it. Define the start
394 address of the kernel here. The most common setup will have the
395 processor vectors at the base of RAM and then the start of the
396 kernel. On some platforms some RAM is reserved for boot loaders
397 and the kernel starts after that. The 0x400 default was based on
398 a system with the RAM based at address 0, and leaving enough room
399 for the theoretical maximum number of 256 vectors.
401 comment "ROM configuration"
404 bool "Specify ROM linker regions"
406 Define a ROM region for the linker script. This creates a kernel
407 that can be stored in flash, with possibly the text, and data
408 regions being copied out to RAM at startup.
411 hex "Address of the base of ROM device"
415 Define the address that the ROM region starts at. Some platforms
416 use this to set their chip select region accordingly for the boot
420 hex "Address of the base of the ROM vectors"
424 This is almost always the same as the base of the ROM. Since on all
425 68000 type variants the vectors are at the base of the boot device
429 hex "Address of the base of system image in ROM"
433 Define the start address of the system image in ROM. Commonly this
434 is strait after the ROM vectors.
437 hex "Size of the ROM device"
441 Size of the ROM device. On some platforms this is used to setup
442 the chip select that controls the boot ROM device.
445 prompt "Kernel executes from"
447 Choose the memory type that the kernel will be running in.
452 The kernel will be resident in RAM when running.
457 The kernel will be resident in FLASH/ROM when running. This is
458 often referred to as Execute-in-Place (XIP), since the kernel
459 code executes from the position it is stored in the FLASH/ROM.