1 comment "Machine Types"
8 select MMU_MOTOROLA if MMU
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.
17 select MMU_MOTOROLA if MMU
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.
25 bool "Macintosh support"
27 select MMU_MOTOROLA if MMU
29 This option enables support for the Apple Macintosh series of
30 computers (yes, there is experimental support now, at least for part
33 Say N unless you're willing to code the remaining necessary support.
39 select MMU_MOTOROLA if MMU
41 Say Y here if you want to run Linux on an MC680x0-based Apollo
42 Domain workstation such as the DN3500.
45 bool "VME (Motorola and BVM) support"
47 select MMU_MOTOROLA if MMU
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.
55 bool "MVME147 support"
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.
65 bool "MVME162, 166 and 167 support"
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
76 bool "BVME4000 and BVME6000 support"
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.
86 bool "HP9000/300 and HP9000/400 support"
88 select MMU_MOTOROLA if MMU
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
94 Everybody else says N.
99 select MMU_MOTOROLA if MMU
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>.
108 If you don't want to compile a kernel for a Sun 3x, say N.
111 bool "Q40/Q60 support"
113 select MMU_MOTOROLA if MMU
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
124 depends on !MMU_MOTOROLA
125 select MMU_SUN3 if MMU
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!).
133 If you don't want to compile a kernel exclusively for a Sun 3, say N.
141 bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support"
145 Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII.
148 bool "(X)Copilot support"
151 Support the bugs of Xcopilot.
154 bool "Arcturus Networks uC5272 dimm board support"
157 Support for the Arcturus Networks uC5272 dimm board.
160 bool "Arcturus Networks uC5282 board support"
163 Support for the Arcturus Networks uC5282 dimm board.
166 bool "uCsimm module support"
169 Support for the Arcturus Networks uCsimm module.
172 bool "uDsimm module support"
175 Support for the Arcturus Networks uDsimm module.
178 bool "DragenEngine II board support"
181 Support for the DragenEngine II board.
183 config DIRECT_IO_ACCESS
184 bool "Allow user to access IO directly"
185 depends on (UCSIMM || UCDIMM || DRAGEN2)
187 Disable the CPU internal registers protection in user mode,
188 to allow a user application to read/write them.
191 bool "Initialize LCD"
192 depends on (UCSIMM || UCDIMM || DRAGEN2)
194 Initialize the LCD controller of the 68x328 processor.
196 config MEMORY_RESERVE
197 int "Memory reservation (MiB)"
198 depends on (UCSIMM || UCDIMM)
200 Reserve certain memory regions on 68x328 based boards.
203 bool "Lineo uCquicc board support"
206 Support for the Lineo uCquicc board.
212 bool "Arnewsh 5206 board support"
216 Support for the Arnewsh 5206 board.
222 bool "Motorola M5206eC3 board support"
226 Support for the Motorola M5206eC3 board.
229 bool "Motorola M5206eLITE board support"
232 Support for the Motorola M5206eLITE board.
235 bool "Freescale M5208EVB board support"
239 Support for the Freescale Coldfire M5208EVB.
242 bool "Freescale M5235EVB support"
246 Support for the Freescale M5235EVB board.
249 bool "Motorola M5249C3 board support"
253 Support for the Motorola M5249C3 board.
256 bool "Freescale (Motorola) M5271EVB board support"
260 Support for the Freescale (Motorola) M5271EVB board.
263 bool "Freescale (Motorola) M5275EVB board support"
267 Support for the Freescale (Motorola) M5275EVB board.
270 bool "Motorola M5272C3 board support"
274 Support for the Motorola M5272C3 board.
280 bool "senTec COBRA5272 board support"
284 Support for the senTec COBRA5272 board.
290 bool "Avnet 5282 board support"
294 Support for the Avnet 5282 board.
297 bool "Motorola M5282EVB board support"
301 Support for the Motorola M5282EVB board.
304 bool "senTec COBRA5282 board support"
308 Support for the senTec COBRA5282 board.
311 bool "EMAC.Inc SOM5282EM board support"
314 Support for the EMAC.Inc SOM5282EM module.
317 bool "Intec Automation Inc. WildFire board support"
320 Support for the Intec Automation Inc. WildFire.
323 bool "Intec Automation Inc. WildFire module support"
326 Support for the Intec Automation Inc. WildFire module.
329 bool "Arnewsh 5307 board support"
333 Support for the Arnewsh 5307 board.
336 bool "Motorola M5307C3 board support"
340 Support for the Motorola M5307C3 board.
343 bool "SnapGear SecureEdge/MP3 platform support"
346 Support for the SnapGear SecureEdge/MP3 platform.
349 bool "Freescale (Motorola) M5329EVB board support"
353 Support for the Freescale (Motorola) M5329EVB board.
356 bool "senTec COBRA5329 board support"
359 Support for the senTec COBRA5329 board.
362 bool "Motorola M5407C3 board support"
366 Support for the Motorola M5407C3 board.
369 bool "FireBee board support"
372 Support for the FireBee ColdFire 5475 based board.
375 bool "Feith CLEOPATRA board support"
376 depends on (M5307 || M5407)
378 Support for the Feith Cleopatra boards.
381 bool "Feith CANCam board support"
384 Support for the Feith CANCam board.
387 bool "Feith SCALES board support"
390 Support for the Feith SCALES board.
393 bool "SecureEdge/NETtel board support"
394 depends on (M5206e || M5272 || M5307)
396 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
399 bool "SnapGear router board support"
402 Special additional support for SnapGear router boards.
408 bool "Sneha Technologies S.L. Sarasvati board support"
412 Support for the SNEHA CPU16B board.
415 bool "Netburner MOD-5272 board support"
418 Support for the Netburner MOD-5272 board.
424 bool "Savant Rosie1 board support"
428 Support for the Savant Rosie1 board.
433 comment "Machine Options"
436 bool "Support for U-Boot command line parameters"
438 If you say Y here kernel will try to collect command
439 line parameters from the initial u-boot stack.
443 bool "Use 4Kb for kernel stacks instead of 8Kb"
446 If you say Y here the kernel will use a 4Kb stacksize for the
447 kernel stack attached to each process/thread. This facilitates
448 running more threads on a system and also reduces the pressure
449 on the VM subsystem for higher order allocations.
451 comment "RAM configuration"
454 hex "Address of the base of RAM"
457 Define the address that RAM starts at. On many platforms this is
458 0, the base of the address space. And this is the default. Some
459 platforms choose to setup their RAM at other addresses within the
460 processor address space.
463 hex "Size of RAM (in bytes), or 0 for automatic"
466 Define the size of the system RAM. If you select 0 then the
467 kernel will try to probe the RAM size at runtime. This is not
468 supported on all CPU types.
471 hex "Address of the base of system vectors"
474 Define the address of the system vectors. Commonly this is
475 put at the start of RAM, but it doesn't have to be. On ColdFire
476 platforms this address is programmed into the VBR register, thus
477 actually setting the address to use.
480 hex "Address of the MBAR (internal peripherals)"
484 Define the address of the internal system peripherals. This value
485 is set in the processors MBAR register. This is generally setup by
486 the boot loader, and will not be written by the kernel. By far most
487 ColdFire boards use the default 0x10000000 value, so if unsure then
491 hex "Address of the IPSBAR (internal peripherals)"
493 depends on HAVE_IPSBAR
495 Define the address of the internal system peripherals. This value
496 is set in the processors IPSBAR register. This is generally setup by
497 the boot loader, and will not be written by the kernel. By far most
498 ColdFire boards use the default 0x40000000 value, so if unsure then
502 hex "Address of the base of kernel code"
505 Typically on m68k systems the kernel will not start at the base
506 of RAM, but usually some small offset from it. Define the start
507 address of the kernel here. The most common setup will have the
508 processor vectors at the base of RAM and then the start of the
509 kernel. On some platforms some RAM is reserved for boot loaders
510 and the kernel starts after that. The 0x400 default was based on
511 a system with the RAM based at address 0, and leaving enough room
512 for the theoretical maximum number of 256 vectors.
514 comment "ROM configuration"
517 bool "Specify ROM linker regions"
520 Define a ROM region for the linker script. This creates a kernel
521 that can be stored in flash, with possibly the text, and data
522 regions being copied out to RAM at startup.
525 hex "Address of the base of ROM device"
529 Define the address that the ROM region starts at. Some platforms
530 use this to set their chip select region accordingly for the boot
534 hex "Address of the base of the ROM vectors"
538 This is almost always the same as the base of the ROM. Since on all
539 68000 type variants the vectors are at the base of the boot device
543 hex "Size of ROM vector region (in bytes)"
547 Define the size of the vector region in ROM. For most 68000
548 variants this would be 0x400 bytes in size. Set to 0 if you do
549 not want a vector region at the start of the ROM.
552 hex "Address of the base of system image in ROM"
556 Define the start address of the system image in ROM. Commonly this
557 is strait after the ROM vectors.
560 hex "Size of the ROM device"
564 Size of the ROM device. On some platforms this is used to setup
565 the chip select that controls the boot ROM device.
568 prompt "Kernel executes from"
570 Choose the memory type that the kernel will be running in.
575 The kernel will be resident in RAM when running.
580 The kernel will be resident in FLASH/ROM when running. This is
581 often referred to as Execute-in-Place (XIP), since the kernel
582 code executes from the position it is stored in the FLASH/ROM.