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
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)
195 Reserve certain memory regions on 68x328 based boards.
198 bool "Arnewsh 5206 board support"
201 Support for the Arnewsh 5206 board.
204 bool "Motorola M5206eC3 board support"
207 Support for the Motorola M5206eC3 board.
210 bool "Motorola M5206eLITE board support"
213 Support for the Motorola M5206eLITE board.
216 bool "Freescale M5235EVB support"
219 Support for the Freescale M5235EVB board.
222 bool "Motorola M5249C3 board support"
225 Support for the Motorola M5249C3 board.
228 bool "Motorola M5272C3 board support"
231 Support for the Motorola M5272C3 board.
234 bool "Intec Automation Inc. WildFire board support"
237 Support for the Intec Automation Inc. WildFire.
240 bool "Intec Automation Inc. WildFire module support"
243 Support for the Intec Automation Inc. WildFire module.
246 bool "Arnewsh 5307 board support"
249 Support for the Arnewsh 5307 board.
252 bool "Motorola M5307C3 board support"
255 Support for the Motorola M5307C3 board.
258 bool "SnapGear SecureEdge/MP3 platform support"
261 Support for the SnapGear SecureEdge/MP3 platform.
264 bool "Motorola M5407C3 board support"
267 Support for the Motorola M5407C3 board.
270 bool "Sysam AMCORE board support"
273 Support for the Sysam AMCORE open-hardware generic board.
276 bool "Sysam stmark2 board support"
279 Support for the Sysam stmark2 open-hardware generic board.
282 bool "FireBee board support"
285 Support for the FireBee ColdFire 5475 based board.
288 bool "Feith CLEOPATRA board support"
289 depends on (M5307 || M5407)
291 Support for the Feith Cleopatra boards.
294 bool "Feith CANCam board support"
297 Support for the Feith CANCam board.
300 bool "Feith SCALES board support"
303 Support for the Feith SCALES board.
306 bool "SecureEdge/NETtel board support"
307 depends on (M5206e || M5272 || M5307)
309 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
312 bool "Netburner MOD-5272 board support"
315 Support for the Netburner MOD-5272 board.
319 comment "Machine Options"
322 bool "Support for U-Boot command line parameters"
325 If you say Y here kernel will try to collect command
326 line parameters from the initial u-boot stack.
329 bool "Use 4Kb for kernel stacks instead of 8Kb"
332 If you say Y here the kernel will use a 4Kb stacksize for the
333 kernel stack attached to each process/thread. This facilitates
334 running more threads on a system and also reduces the pressure
335 on the VM subsystem for higher order allocations.
337 comment "RAM configuration"
340 hex "Address of the base of RAM"
343 Define the address that RAM starts at. On many platforms this is
344 0, the base of the address space. And this is the default. Some
345 platforms choose to setup their RAM at other addresses within the
346 processor address space.
349 hex "Size of RAM (in bytes), or 0 for automatic"
352 Define the size of the system RAM. If you select 0 then the
353 kernel will try to probe the RAM size at runtime. This is not
354 supported on all CPU types.
357 hex "Address of the base of system vectors"
360 Define the address of the system vectors. Commonly this is
361 put at the start of RAM, but it doesn't have to be. On ColdFire
362 platforms this address is programmed into the VBR register, thus
363 actually setting the address to use.
366 hex "Address of the MBAR (internal peripherals)"
370 Define the address of the internal system peripherals. This value
371 is set in the processors MBAR register. This is generally setup by
372 the boot loader, and will not be written by the kernel. By far most
373 ColdFire boards use the default 0x10000000 value, so if unsure then
377 hex "Address of the IPSBAR (internal peripherals)"
379 depends on HAVE_IPSBAR
381 Define the address of the internal system peripherals. This value
382 is set in the processors IPSBAR register. This is generally setup by
383 the boot loader, and will not be written by the kernel. By far most
384 ColdFire boards use the default 0x40000000 value, so if unsure then
388 hex "Address of the base of kernel code"
391 Typically on m68k systems the kernel will not start at the base
392 of RAM, but usually some small offset from it. Define the start
393 address of the kernel here. The most common setup will have the
394 processor vectors at the base of RAM and then the start of the
395 kernel. On some platforms some RAM is reserved for boot loaders
396 and the kernel starts after that. The 0x400 default was based on
397 a system with the RAM based at address 0, and leaving enough room
398 for the theoretical maximum number of 256 vectors.
400 comment "ROM configuration"
403 bool "Specify ROM linker regions"
405 Define a ROM region for the linker script. This creates a kernel
406 that can be stored in flash, with possibly the text, and data
407 regions being copied out to RAM at startup.
410 hex "Address of the base of ROM device"
414 Define the address that the ROM region starts at. Some platforms
415 use this to set their chip select region accordingly for the boot
419 hex "Address of the base of the ROM vectors"
423 This is almost always the same as the base of the ROM. Since on all
424 68000 type variants the vectors are at the base of the boot device
428 hex "Address of the base of system image in ROM"
432 Define the start address of the system image in ROM. Commonly this
433 is strait after the ROM vectors.
436 hex "Size of the ROM device"
440 Size of the ROM device. On some platforms this is used to setup
441 the chip select that controls the boot ROM device.
444 prompt "Kernel executes from"
446 Choose the memory type that the kernel will be running in.
451 The kernel will be resident in RAM when running.
456 The kernel will be resident in FLASH/ROM when running. This is
457 often referred to as Execute-in-Place (XIP), since the kernel
458 code executes from the position it is stored in the FLASH/ROM.