1 comment "Machine Types"
6 select MMU_MOTOROLA if MMU
8 This option enables support for the Amiga series of computers. If
9 you plan to use this kernel on an Amiga, say Y here and browse the
10 material available in <file:Documentation/m68k>; otherwise say N.
15 select MMU_MOTOROLA if MMU
17 This option enables support for the 68000-based Atari series of
18 computers (including the TT, Falcon and Medusa). If you plan to use
19 this kernel on an Atari, say Y here and browse the material
20 available in <file:Documentation/m68k>; otherwise say N.
23 bool "Macintosh support"
25 select MMU_MOTOROLA if MMU
27 This option enables support for the Apple Macintosh series of
28 computers (yes, there is experimental support now, at least for part
31 Say N unless you're willing to code the remaining necessary support.
37 select MMU_MOTOROLA if MMU
39 Say Y here if you want to run Linux on an MC680x0-based Apollo
40 Domain workstation such as the DN3500.
43 bool "VME (Motorola and BVM) support"
45 select MMU_MOTOROLA if MMU
47 Say Y here if you want to build a kernel for a 680x0 based VME
48 board. Boards currently supported include Motorola boards MVME147,
49 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
50 BVME6000 boards from BVM Ltd are also supported.
53 bool "MVME147 support"
57 Say Y to include support for early Motorola VME boards. This will
58 build a kernel which can run on MVME147 single-board computers. If
59 you select this option you will have to select the appropriate
60 drivers for SCSI, Ethernet and serial ports later on.
63 bool "MVME162, 166 and 167 support"
67 Say Y to include support for Motorola VME boards. This will build a
68 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
69 MVME177 boards. If you select this option you will have to select
70 the appropriate drivers for SCSI, Ethernet and serial ports later
74 bool "BVME4000 and BVME6000 support"
78 Say Y to include support for VME boards from BVM Ltd. This will
79 build a kernel which can run on BVME4000 and BVME6000 boards. If
80 you select this option you will have to select the appropriate
81 drivers for SCSI, Ethernet and serial ports later on.
84 bool "HP9000/300 and HP9000/400 support"
86 select MMU_MOTOROLA if MMU
88 This option enables support for the HP9000/300 and HP9000/400 series
89 of workstations. Support for these machines is still somewhat
90 experimental. If you plan to try to use the kernel on such a machine
92 Everybody else says N.
97 select MMU_MOTOROLA if MMU
100 This option enables support for the Sun 3x series of workstations.
101 Be warned that this support is very experimental.
102 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
103 General Linux information on the Sun 3x series (now discontinued)
104 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
106 If you don't want to compile a kernel for a Sun 3x, say N.
109 bool "Q40/Q60 support"
111 select MMU_MOTOROLA if MMU
113 The Q40 is a Motorola 68040-based successor to the Sinclair QL
114 manufactured in Germany. There is an official Q40 home page at
115 <http://www.q40.de/>. This option enables support for the Q40 and
116 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
122 depends on !MMU_MOTOROLA
123 select MMU_SUN3 if MMU
126 This option enables support for the Sun 3 series of workstations
127 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
128 that all other hardware types must be disabled, as Sun 3 kernels
129 are incompatible with all other m68k targets (including Sun 3x!).
131 If you don't want to compile a kernel exclusively for a Sun 3, say N.
137 bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support"
141 Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII.
144 bool "(X)Copilot support"
147 Support the bugs of Xcopilot.
150 bool "Arcturus Networks uC5272 dimm board support"
153 Support for the Arcturus Networks uC5272 dimm board.
156 bool "Arcturus Networks uC5282 board support"
159 Support for the Arcturus Networks uC5282 dimm board.
162 bool "uCsimm module support"
165 Support for the Arcturus Networks uCsimm module.
168 bool "uDsimm module support"
171 Support for the Arcturus Networks uDsimm module.
174 bool "DragenEngine II board support"
177 Support for the DragenEngine II board.
179 config DIRECT_IO_ACCESS
180 bool "Allow user to access IO directly"
181 depends on (UCSIMM || UCDIMM || DRAGEN2)
183 Disable the CPU internal registers protection in user mode,
184 to allow a user application to read/write them.
187 bool "Initialize LCD"
188 depends on (UCSIMM || UCDIMM || DRAGEN2)
190 Initialize the LCD controller of the 68x328 processor.
192 config MEMORY_RESERVE
193 int "Memory reservation (MiB)"
194 depends on (UCSIMM || UCDIMM)
196 Reserve certain memory regions on 68x328 based boards.
199 bool "Lineo uCquicc board support"
202 Support for the Lineo uCquicc board.
208 bool "Arnewsh 5206 board support"
212 Support for the Arnewsh 5206 board.
218 bool "Motorola M5206eC3 board support"
222 Support for the Motorola M5206eC3 board.
225 bool "Motorola M5206eLITE board support"
228 Support for the Motorola M5206eLITE board.
231 bool "Freescale M5208EVB board support"
235 Support for the Freescale Coldfire M5208EVB.
238 bool "Freescale M5235EVB support"
242 Support for the Freescale M5235EVB board.
245 bool "Motorola M5249C3 board support"
249 Support for the Motorola M5249C3 board.
252 bool "Freescale (Motorola) M5271EVB board support"
256 Support for the Freescale (Motorola) M5271EVB board.
259 bool "Freescale (Motorola) M5275EVB board support"
263 Support for the Freescale (Motorola) M5275EVB board.
266 bool "Motorola M5272C3 board support"
270 Support for the Motorola M5272C3 board.
276 bool "senTec COBRA5272 board support"
280 Support for the senTec COBRA5272 board.
286 bool "Avnet 5282 board support"
290 Support for the Avnet 5282 board.
293 bool "Motorola M5282EVB board support"
297 Support for the Motorola M5282EVB board.
300 bool "senTec COBRA5282 board support"
304 Support for the senTec COBRA5282 board.
310 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.
378 bool "Feith CLEOPATRA board support"
379 depends on (M5307 || M5407)
382 Support for the Feith Cleopatra boards.
385 bool "Feith CANCam board support"
389 Support for the Feith CANCam board.
392 bool "Feith SCALES board support"
396 Support for the Feith SCALES board.
399 bool "SecureEdge/NETtel board support"
400 depends on (M5206e || M5272 || M5307)
402 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
405 bool "SnapGear router board support"
408 Special additional support for SnapGear router boards.
414 bool "Sneha Technologies S.L. Sarasvati board support"
418 Support for the SNEHA CPU16B board.
421 bool "Netburner MOD-5272 board support"
424 Support for the Netburner MOD-5272 board.
430 bool "Savant Rosie1 board support"
434 Support for the Savant Rosie1 board.
439 comment "Machine Options"
441 config ROMFS_FROM_ROM
442 bool "ROMFS image not RAM resident"
443 depends on (NETtel || SNAPGEAR)
445 The ROMfs filesystem will stay resident in the FLASH/ROM, not be
449 bool "Support for U-Boot command line parameters"
451 If you say Y here kernel will try to collect command
452 line parameters from the initial u-boot stack.
456 bool "Use 4Kb for kernel stacks instead of 8Kb"
459 If you say Y here the kernel will use a 4Kb stacksize for the
460 kernel stack attached to each process/thread. This facilitates
461 running more threads on a system and also reduces the pressure
462 on the VM subsystem for higher order allocations.
464 comment "RAM configuration"
467 hex "Address of the base of RAM"
470 Define the address that RAM starts at. On many platforms this is
471 0, the base of the address space. And this is the default. Some
472 platforms choose to setup their RAM at other addresses within the
473 processor address space.
476 hex "Size of RAM (in bytes), or 0 for automatic"
479 Define the size of the system RAM. If you select 0 then the
480 kernel will try to probe the RAM size at runtime. This is not
481 supported on all CPU types.
484 hex "Address of the base of system vectors"
487 Define the address of the system vectors. Commonly this is
488 put at the start of RAM, but it doesn't have to be. On ColdFire
489 platforms this address is programmed into the VBR register, thus
490 actually setting the address to use.
493 hex "Address of the MBAR (internal peripherals)"
497 Define the address of the internal system peripherals. This value
498 is set in the processors MBAR register. This is generally setup by
499 the boot loader, and will not be written by the kernel. By far most
500 ColdFire boards use the default 0x10000000 value, so if unsure then
504 hex "Address of the IPSBAR (internal peripherals)"
506 depends on HAVE_IPSBAR
508 Define the address of the internal system peripherals. This value
509 is set in the processors IPSBAR register. This is generally setup by
510 the boot loader, and will not be written by the kernel. By far most
511 ColdFire boards use the default 0x40000000 value, so if unsure then
515 hex "Address of the base of kernel code"
518 Typically on m68k systems the kernel will not start at the base
519 of RAM, but usually some small offset from it. Define the start
520 address of the kernel here. The most common setup will have the
521 processor vectors at the base of RAM and then the start of the
522 kernel. On some platforms some RAM is reserved for boot loaders
523 and the kernel starts after that. The 0x400 default was based on
524 a system with the RAM based at address 0, and leaving enough room
525 for the theoretical maximum number of 256 vectors.
528 prompt "RAM bus width"
534 Select the physical RAM data bus size. Not needed on most platforms,
535 so you can generally choose AUTO.
540 Configure RAM bus to be 8 bits wide.
545 Configure RAM bus to be 16 bits wide.
550 Configure RAM bus to be 32 bits wide.
554 comment "ROM configuration"
557 bool "Specify ROM linker regions"
560 Define a ROM region for the linker script. This creates a kernel
561 that can be stored in flash, with possibly the text, and data
562 regions being copied out to RAM at startup.
565 hex "Address of the base of ROM device"
569 Define the address that the ROM region starts at. Some platforms
570 use this to set their chip select region accordingly for the boot
574 hex "Address of the base of the ROM vectors"
578 This is almost always the same as the base of the ROM. Since on all
579 68000 type variants the vectors are at the base of the boot device
583 hex "Size of ROM vector region (in bytes)"
587 Define the size of the vector region in ROM. For most 68000
588 variants this would be 0x400 bytes in size. Set to 0 if you do
589 not want a vector region at the start of the ROM.
592 hex "Address of the base of system image in ROM"
596 Define the start address of the system image in ROM. Commonly this
597 is strait after the ROM vectors.
600 hex "Size of the ROM device"
604 Size of the ROM device. On some platforms this is used to setup
605 the chip select that controls the boot ROM device.
608 prompt "Kernel executes from"
610 Choose the memory type that the kernel will be running in.
615 The kernel will be resident in RAM when running.
620 The kernel will be resident in FLASH/ROM when running. This is
621 often referred to as Execute-in-Place (XIP), since the kernel
622 code executes from the position it is stored in the FLASH/ROM.