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