1# SPDX-License-Identifier: GPL-2.0 2comment "Machine Types" 3 4if M68KCLASSIC 5 6config AMIGA 7 bool "Amiga support" 8 depends on MMU 9 select MMU_MOTOROLA if MMU 10 select LEGACY_TIMER_TICK 11 help 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. 15 16config ATARI 17 bool "Atari support" 18 depends on MMU 19 select MMU_MOTOROLA if MMU 20 select HAVE_ARCH_NVRAM_OPS 21 select LEGACY_TIMER_TICK 22 help 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. 27 28config ATARI_KBD_CORE 29 bool 30 31config MAC 32 bool "Macintosh support" 33 depends on MMU 34 select MMU_MOTOROLA if MMU 35 select HAVE_ARCH_NVRAM_OPS 36 select HAVE_PATA_PLATFORM 37 select LEGACY_TIMER_TICK 38 help 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/>; 42 otherwise say N. 43 44config APOLLO 45 bool "Apollo support" 46 depends on MMU 47 select MMU_MOTOROLA if MMU 48 select LEGACY_TIMER_TICK 49 help 50 Say Y here if you want to run Linux on an MC680x0-based Apollo 51 Domain workstation such as the DN3500. 52 53config VME 54 bool "VME (Motorola and BVM) support" 55 depends on MMU 56 select MMU_MOTOROLA if MMU 57 help 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. 62 63config MVME147 64 bool "MVME147 support" 65 depends on MMU 66 depends on VME 67 select LEGACY_TIMER_TICK 68 help 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. 73 74config MVME16x 75 bool "MVME162, 166 and 167 support" 76 depends on MMU 77 depends on VME 78 select LEGACY_TIMER_TICK 79 help 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 84 on. 85 86config BVME6000 87 bool "BVME4000 and BVME6000 support" 88 depends on MMU 89 depends on VME 90 select LEGACY_TIMER_TICK 91 help 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. 96 97config HP300 98 bool "HP9000/300 and HP9000/400 support" 99 depends on MMU 100 select MMU_MOTOROLA if MMU 101 select LEGACY_TIMER_TICK 102 help 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 106 say Y here. 107 Everybody else says N. 108 109config SUN3X 110 bool "Sun3x support" 111 depends on MMU 112 select LEGACY_TIMER_TICK 113 select MMU_MOTOROLA if MMU 114 select M68030 115 help 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>. 121 122 If you don't want to compile a kernel for a Sun 3x, say N. 123 124config Q40 125 bool "Q40/Q60 support" 126 depends on MMU 127 select MMU_MOTOROLA if MMU 128 select LEGACY_TIMER_TICK 129 help 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 134 emulation. 135 136config SUN3 137 bool "Sun3 support" 138 depends on MMU 139 depends on !MMU_MOTOROLA 140 select MMU_SUN3 if MMU 141 select LEGACY_TIMER_TICK 142 select NO_DMA 143 select M68020 144 help 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!). 149 150 If you don't want to compile a kernel exclusively for a Sun 3, say N. 151 152config PILOT 153 bool 154 155config PILOT3 156 bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support" 157 depends on !MMU 158 select M68328 159 select PILOT 160 help 161 Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII. 162 163config XCOPILOT_BUGS 164 bool "(X)Copilot support" 165 depends on PILOT3 166 help 167 Support the bugs of Xcopilot. 168 169config UCSIMM 170 bool "uCsimm module support" 171 depends on !MMU 172 select M68EZ328 173 help 174 Support for the Arcturus Networks uCsimm module. 175 176config UCDIMM 177 bool "uDsimm module support" 178 depends on !MMU 179 select M68VZ328 180 help 181 Support for the Arcturus Networks uDsimm module. 182 183config DRAGEN2 184 bool "DragenEngine II board support" 185 depends on !MMU 186 select M68VZ328 187 help 188 Support for the DragenEngine II board. 189 190config DIRECT_IO_ACCESS 191 bool "Allow user to access IO directly" 192 depends on (UCSIMM || UCDIMM || DRAGEN2) 193 help 194 Disable the CPU internal registers protection in user mode, 195 to allow a user application to read/write them. 196 197config INIT_LCD 198 bool "Initialize LCD" 199 depends on (UCSIMM || UCDIMM || DRAGEN2) 200 help 201 Initialize the LCD controller of the 68x328 processor. 202 203config MEMORY_RESERVE 204 int "Memory reservation (MiB)" 205 depends on (UCSIMM || UCDIMM) 206 default 0 207 help 208 Reserve certain memory regions on 68x328 based boards. 209 210endif # M68KCLASSIC 211 212config ARN5206 213 bool "Arnewsh 5206 board support" 214 depends on M5206 215 help 216 Support for the Arnewsh 5206 board. 217 218config M5206eC3 219 bool "Motorola M5206eC3 board support" 220 depends on M5206e 221 help 222 Support for the Motorola M5206eC3 board. 223 224config ELITE 225 bool "Motorola M5206eLITE board support" 226 depends on M5206e 227 help 228 Support for the Motorola M5206eLITE board. 229 230config M5235EVB 231 bool "Freescale M5235EVB support" 232 depends on M523x 233 help 234 Support for the Freescale M5235EVB board. 235 236config M5249C3 237 bool "Motorola M5249C3 board support" 238 depends on M5249 239 help 240 Support for the Motorola M5249C3 board. 241 242config M5272C3 243 bool "Motorola M5272C3 board support" 244 depends on M5272 245 help 246 Support for the Motorola M5272C3 board. 247 248config WILDFIRE 249 bool "Intec Automation Inc. WildFire board support" 250 depends on M528x 251 help 252 Support for the Intec Automation Inc. WildFire. 253 254config WILDFIREMOD 255 bool "Intec Automation Inc. WildFire module support" 256 depends on M528x 257 help 258 Support for the Intec Automation Inc. WildFire module. 259 260config ARN5307 261 bool "Arnewsh 5307 board support" 262 depends on M5307 263 help 264 Support for the Arnewsh 5307 board. 265 266config M5307C3 267 bool "Motorola M5307C3 board support" 268 depends on M5307 269 help 270 Support for the Motorola M5307C3 board. 271 272config SECUREEDGEMP3 273 bool "SnapGear SecureEdge/MP3 platform support" 274 depends on M5307 275 help 276 Support for the SnapGear SecureEdge/MP3 platform. 277 278config M5407C3 279 bool "Motorola M5407C3 board support" 280 depends on M5407 281 help 282 Support for the Motorola M5407C3 board. 283 284config AMCORE 285 bool "Sysam AMCORE board support" 286 depends on M5307 287 help 288 Support for the Sysam AMCORE open-hardware generic board. 289 290config STMARK2 291 bool "Sysam stmark2 board support" 292 depends on M5441x 293 help 294 Support for the Sysam stmark2 open-hardware generic board. 295 296config FIREBEE 297 bool "FireBee board support" 298 depends on M547x 299 help 300 Support for the FireBee ColdFire 5475 based board. 301 302config CLEOPATRA 303 bool "Feith CLEOPATRA board support" 304 depends on (M5307 || M5407) 305 help 306 Support for the Feith Cleopatra boards. 307 308config CANCam 309 bool "Feith CANCam board support" 310 depends on M5272 311 help 312 Support for the Feith CANCam board. 313 314config SCALES 315 bool "Feith SCALES board support" 316 depends on M5272 317 help 318 Support for the Feith SCALES board. 319 320config NETtel 321 bool "SecureEdge/NETtel board support" 322 depends on (M5206e || M5272 || M5307) 323 help 324 Support for the SnapGear NETtel/SecureEdge/SnapGear boards. 325 326config MOD5272 327 bool "Netburner MOD-5272 board support" 328 depends on M5272 329 help 330 Support for the Netburner MOD-5272 board. 331 332if !MMU || COLDFIRE 333 334comment "Machine Options" 335 336config UBOOT 337 bool "Support for U-Boot command line parameters" 338 help 339 If you say Y here kernel will try to collect command 340 line parameters from the initial u-boot stack. 341 342config 4KSTACKS 343 bool "Use 4Kb for kernel stacks instead of 8Kb" 344 default y 345 help 346 If you say Y here the kernel will use a 4Kb stacksize for the 347 kernel stack attached to each process/thread. This facilitates 348 running more threads on a system and also reduces the pressure 349 on the VM subsystem for higher order allocations. 350 351comment "RAM configuration" 352 353config RAMBASE 354 hex "Address of the base of RAM" 355 default "0" 356 help 357 Define the address that RAM starts at. On many platforms this is 358 0, the base of the address space. And this is the default. Some 359 platforms choose to setup their RAM at other addresses within the 360 processor address space. 361 362config RAMSIZE 363 hex "Size of RAM (in bytes), or 0 for automatic" 364 default "0x400000" 365 help 366 Define the size of the system RAM. If you select 0 then the 367 kernel will try to probe the RAM size at runtime. This is not 368 supported on all CPU types. 369 370config VECTORBASE 371 hex "Address of the base of system vectors" 372 default "0" 373 help 374 Define the address of the system vectors. Commonly this is 375 put at the start of RAM, but it doesn't have to be. On ColdFire 376 platforms this address is programmed into the VBR register, thus 377 actually setting the address to use. 378 379config MBAR 380 hex "Address of the MBAR (internal peripherals)" 381 default "0x10000000" 382 depends on HAVE_MBAR 383 help 384 Define the address of the internal system peripherals. This value 385 is set in the processors MBAR register. This is generally setup by 386 the boot loader, and will not be written by the kernel. By far most 387 ColdFire boards use the default 0x10000000 value, so if unsure then 388 use this. 389 390config IPSBAR 391 hex "Address of the IPSBAR (internal peripherals)" 392 default "0x40000000" 393 depends on HAVE_IPSBAR 394 help 395 Define the address of the internal system peripherals. This value 396 is set in the processors IPSBAR register. This is generally setup by 397 the boot loader, and will not be written by the kernel. By far most 398 ColdFire boards use the default 0x40000000 value, so if unsure then 399 use this. 400 401config KERNELBASE 402 hex "Address of the base of kernel code" 403 default "0x400" 404 help 405 Typically on m68k systems the kernel will not start at the base 406 of RAM, but usually some small offset from it. Define the start 407 address of the kernel here. The most common setup will have the 408 processor vectors at the base of RAM and then the start of the 409 kernel. On some platforms some RAM is reserved for boot loaders 410 and the kernel starts after that. The 0x400 default was based on 411 a system with the RAM based at address 0, and leaving enough room 412 for the theoretical maximum number of 256 vectors. 413 414comment "ROM configuration" 415 416config ROM 417 bool "Specify ROM linker regions" 418 help 419 Define a ROM region for the linker script. This creates a kernel 420 that can be stored in flash, with possibly the text, and data 421 regions being copied out to RAM at startup. 422 423config ROMBASE 424 hex "Address of the base of ROM device" 425 default "0" 426 depends on ROM 427 help 428 Define the address that the ROM region starts at. Some platforms 429 use this to set their chip select region accordingly for the boot 430 device. 431 432config ROMVEC 433 hex "Address of the base of the ROM vectors" 434 default "0" 435 depends on ROM 436 help 437 This is almost always the same as the base of the ROM. Since on all 438 68000 type variants the vectors are at the base of the boot device 439 on system startup. 440 441config ROMSTART 442 hex "Address of the base of system image in ROM" 443 default "0x400" 444 depends on ROM 445 help 446 Define the start address of the system image in ROM. Commonly this 447 is strait after the ROM vectors. 448 449config ROMSIZE 450 hex "Size of the ROM device" 451 default "0x100000" 452 depends on ROM 453 help 454 Size of the ROM device. On some platforms this is used to setup 455 the chip select that controls the boot ROM device. 456 457choice 458 prompt "Kernel executes from" 459 help 460 Choose the memory type that the kernel will be running in. 461 462config RAMKERNEL 463 bool "RAM" 464 help 465 The kernel will be resident in RAM when running. 466 467config ROMKERNEL 468 bool "ROM" 469 depends on ROM 470 help 471 The kernel will be resident in FLASH/ROM when running. This is 472 often referred to as Execute-in-Place (XIP), since the kernel 473 code executes from the position it is stored in the FLASH/ROM. 474 475endchoice 476 477endif 478