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 MMU_MOTOROLA if MMU
105 This option enables support for the Sun 3x series of workstations.
106 Be warned that this support is very experimental.
107 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
108 General Linux information on the Sun 3x series (now discontinued)
109 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
111 If you don't want to compile a kernel for a Sun 3x, say N.
114 bool "Q40/Q60 support"
116 select MMU_MOTOROLA if MMU
118 The Q40 is a Motorola 68040-based successor to the Sinclair QL
119 manufactured in Germany. There is an official Q40 home page at
120 <http://www.q40.de/>. This option enables support for the Q40 and
121 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
127 depends on !MMU_MOTOROLA
128 select MMU_SUN3 if MMU
132 This option enables support for the Sun 3 series of workstations
133 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
134 that all other hardware types must be disabled, as Sun 3 kernels
135 are incompatible with all other m68k targets (including Sun 3x!).
137 If you don't want to compile a kernel exclusively for a Sun 3, say N.
145 bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support"
149 Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII.
152 bool "(X)Copilot support"
155 Support the bugs of Xcopilot.
158 bool "uCsimm module support"
161 Support for the Arcturus Networks uCsimm module.
164 bool "uDsimm module support"
167 Support for the Arcturus Networks uDsimm module.
170 bool "DragenEngine II board support"
173 Support for the DragenEngine II board.
175 config DIRECT_IO_ACCESS
176 bool "Allow user to access IO directly"
177 depends on (UCSIMM || UCDIMM || DRAGEN2)
179 Disable the CPU internal registers protection in user mode,
180 to allow a user application to read/write them.
183 bool "Initialize LCD"
184 depends on (UCSIMM || UCDIMM || DRAGEN2)
186 Initialize the LCD controller of the 68x328 processor.
188 config MEMORY_RESERVE
189 int "Memory reservation (MiB)"
190 depends on (UCSIMM || UCDIMM)
192 Reserve certain memory regions on 68x328 based boards.
195 bool "Arnewsh 5206 board support"
198 Support for the Arnewsh 5206 board.
201 bool "Motorola M5206eC3 board support"
204 Support for the Motorola M5206eC3 board.
207 bool "Motorola M5206eLITE board support"
210 Support for the Motorola M5206eLITE board.
213 bool "Freescale M5235EVB support"
216 Support for the Freescale M5235EVB board.
219 bool "Motorola M5249C3 board support"
222 Support for the Motorola M5249C3 board.
225 bool "Motorola M5272C3 board support"
228 Support for the Motorola M5272C3 board.
231 bool "Intec Automation Inc. WildFire board support"
234 Support for the Intec Automation Inc. WildFire.
237 bool "Intec Automation Inc. WildFire module support"
240 Support for the Intec Automation Inc. WildFire module.
243 bool "Arnewsh 5307 board support"
246 Support for the Arnewsh 5307 board.
249 bool "Motorola M5307C3 board support"
252 Support for the Motorola M5307C3 board.
255 bool "SnapGear SecureEdge/MP3 platform support"
258 Support for the SnapGear SecureEdge/MP3 platform.
261 bool "Motorola M5407C3 board support"
264 Support for the Motorola M5407C3 board.
267 bool "Sysam AMCORE board support"
270 Support for the Sysam AMCORE open-hardware generic board.
273 bool "Sysam stmark2 board support"
276 Support for the Sysam stmark2 open-hardware generic board.
279 bool "FireBee board support"
282 Support for the FireBee ColdFire 5475 based board.
285 bool "Feith CLEOPATRA board support"
286 depends on (M5307 || M5407)
288 Support for the Feith Cleopatra boards.
291 bool "Feith CANCam board support"
294 Support for the Feith CANCam board.
297 bool "Feith SCALES board support"
300 Support for the Feith SCALES board.
303 bool "SecureEdge/NETtel board support"
304 depends on (M5206e || M5272 || M5307)
306 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
309 bool "Netburner MOD-5272 board support"
312 Support for the Netburner MOD-5272 board.
316 comment "Machine Options"
319 bool "Support for U-Boot command line parameters"
321 If you say Y here kernel will try to collect command
322 line parameters from the initial u-boot stack.
325 bool "Use 4Kb for kernel stacks instead of 8Kb"
328 If you say Y here the kernel will use a 4Kb stacksize for the
329 kernel stack attached to each process/thread. This facilitates
330 running more threads on a system and also reduces the pressure
331 on the VM subsystem for higher order allocations.
333 comment "RAM configuration"
336 hex "Address of the base of RAM"
339 Define the address that RAM starts at. On many platforms this is
340 0, the base of the address space. And this is the default. Some
341 platforms choose to setup their RAM at other addresses within the
342 processor address space.
345 hex "Size of RAM (in bytes), or 0 for automatic"
348 Define the size of the system RAM. If you select 0 then the
349 kernel will try to probe the RAM size at runtime. This is not
350 supported on all CPU types.
353 hex "Address of the base of system vectors"
356 Define the address of the system vectors. Commonly this is
357 put at the start of RAM, but it doesn't have to be. On ColdFire
358 platforms this address is programmed into the VBR register, thus
359 actually setting the address to use.
362 hex "Address of the MBAR (internal peripherals)"
366 Define the address of the internal system peripherals. This value
367 is set in the processors MBAR register. This is generally setup by
368 the boot loader, and will not be written by the kernel. By far most
369 ColdFire boards use the default 0x10000000 value, so if unsure then
373 hex "Address of the IPSBAR (internal peripherals)"
375 depends on HAVE_IPSBAR
377 Define the address of the internal system peripherals. This value
378 is set in the processors IPSBAR register. This is generally setup by
379 the boot loader, and will not be written by the kernel. By far most
380 ColdFire boards use the default 0x40000000 value, so if unsure then
384 hex "Address of the base of kernel code"
387 Typically on m68k systems the kernel will not start at the base
388 of RAM, but usually some small offset from it. Define the start
389 address of the kernel here. The most common setup will have the
390 processor vectors at the base of RAM and then the start of the
391 kernel. On some platforms some RAM is reserved for boot loaders
392 and the kernel starts after that. The 0x400 default was based on
393 a system with the RAM based at address 0, and leaving enough room
394 for the theoretical maximum number of 256 vectors.
396 comment "ROM configuration"
399 bool "Specify ROM linker regions"
401 Define a ROM region for the linker script. This creates a kernel
402 that can be stored in flash, with possibly the text, and data
403 regions being copied out to RAM at startup.
406 hex "Address of the base of ROM device"
410 Define the address that the ROM region starts at. Some platforms
411 use this to set their chip select region accordingly for the boot
415 hex "Address of the base of the ROM vectors"
419 This is almost always the same as the base of the ROM. Since on all
420 68000 type variants the vectors are at the base of the boot device
424 hex "Address of the base of system image in ROM"
428 Define the start address of the system image in ROM. Commonly this
429 is strait after the ROM vectors.
432 hex "Size of the ROM device"
436 Size of the ROM device. On some platforms this is used to setup
437 the chip select that controls the boot ROM device.
440 prompt "Kernel executes from"
442 Choose the memory type that the kernel will be running in.
447 The kernel will be resident in RAM when running.
452 The kernel will be resident in FLASH/ROM when running. This is
453 often referred to as Execute-in-Place (XIP), since the kernel
454 code executes from the position it is stored in the FLASH/ROM.