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 "uCsimm module support"
157 Support for the Arcturus Networks uCsimm module.
160 bool "uDsimm module support"
163 Support for the Arcturus Networks uDsimm module.
166 bool "DragenEngine II board support"
169 Support for the DragenEngine II board.
171 config DIRECT_IO_ACCESS
172 bool "Allow user to access IO directly"
173 depends on (UCSIMM || UCDIMM || DRAGEN2)
175 Disable the CPU internal registers protection in user mode,
176 to allow a user application to read/write them.
179 bool "Initialize LCD"
180 depends on (UCSIMM || UCDIMM || DRAGEN2)
182 Initialize the LCD controller of the 68x328 processor.
184 config MEMORY_RESERVE
185 int "Memory reservation (MiB)"
186 depends on (UCSIMM || UCDIMM)
188 Reserve certain memory regions on 68x328 based boards.
191 bool "Arnewsh 5206 board support"
194 Support for the Arnewsh 5206 board.
197 bool "Motorola M5206eC3 board support"
200 Support for the Motorola M5206eC3 board.
203 bool "Motorola M5206eLITE board support"
206 Support for the Motorola M5206eLITE board.
209 bool "Freescale M5235EVB support"
212 Support for the Freescale M5235EVB board.
215 bool "Motorola M5249C3 board support"
218 Support for the Motorola M5249C3 board.
221 bool "Motorola M5272C3 board support"
224 Support for the Motorola M5272C3 board.
227 bool "Intec Automation Inc. WildFire board support"
230 Support for the Intec Automation Inc. WildFire.
233 bool "Intec Automation Inc. WildFire module support"
236 Support for the Intec Automation Inc. WildFire module.
239 bool "Arnewsh 5307 board support"
242 Support for the Arnewsh 5307 board.
245 bool "Motorola M5307C3 board support"
248 Support for the Motorola M5307C3 board.
251 bool "SnapGear SecureEdge/MP3 platform support"
254 Support for the SnapGear SecureEdge/MP3 platform.
257 bool "Motorola M5407C3 board support"
260 Support for the Motorola M5407C3 board.
263 bool "Sysam AMCORE board support"
266 Support for the Sysam AMCORE open-hardware generic board.
269 bool "FireBee board support"
272 Support for the FireBee ColdFire 5475 based board.
275 bool "Feith CLEOPATRA board support"
276 depends on (M5307 || M5407)
278 Support for the Feith Cleopatra boards.
281 bool "Feith CANCam board support"
284 Support for the Feith CANCam board.
287 bool "Feith SCALES board support"
290 Support for the Feith SCALES board.
293 bool "SecureEdge/NETtel board support"
294 depends on (M5206e || M5272 || M5307)
296 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
299 bool "Netburner MOD-5272 board support"
302 Support for the Netburner MOD-5272 board.
306 comment "Machine Options"
309 bool "Support for U-Boot command line parameters"
311 If you say Y here kernel will try to collect command
312 line parameters from the initial u-boot stack.
316 bool "Use 4Kb for kernel stacks instead of 8Kb"
319 If you say Y here the kernel will use a 4Kb stacksize for the
320 kernel stack attached to each process/thread. This facilitates
321 running more threads on a system and also reduces the pressure
322 on the VM subsystem for higher order allocations.
324 comment "RAM configuration"
327 hex "Address of the base of RAM"
330 Define the address that RAM starts at. On many platforms this is
331 0, the base of the address space. And this is the default. Some
332 platforms choose to setup their RAM at other addresses within the
333 processor address space.
336 hex "Size of RAM (in bytes), or 0 for automatic"
339 Define the size of the system RAM. If you select 0 then the
340 kernel will try to probe the RAM size at runtime. This is not
341 supported on all CPU types.
344 hex "Address of the base of system vectors"
347 Define the address of the system vectors. Commonly this is
348 put at the start of RAM, but it doesn't have to be. On ColdFire
349 platforms this address is programmed into the VBR register, thus
350 actually setting the address to use.
353 hex "Address of the MBAR (internal peripherals)"
357 Define the address of the internal system peripherals. This value
358 is set in the processors MBAR register. This is generally setup by
359 the boot loader, and will not be written by the kernel. By far most
360 ColdFire boards use the default 0x10000000 value, so if unsure then
364 hex "Address of the IPSBAR (internal peripherals)"
366 depends on HAVE_IPSBAR
368 Define the address of the internal system peripherals. This value
369 is set in the processors IPSBAR register. This is generally setup by
370 the boot loader, and will not be written by the kernel. By far most
371 ColdFire boards use the default 0x40000000 value, so if unsure then
375 hex "Address of the base of kernel code"
378 Typically on m68k systems the kernel will not start at the base
379 of RAM, but usually some small offset from it. Define the start
380 address of the kernel here. The most common setup will have the
381 processor vectors at the base of RAM and then the start of the
382 kernel. On some platforms some RAM is reserved for boot loaders
383 and the kernel starts after that. The 0x400 default was based on
384 a system with the RAM based at address 0, and leaving enough room
385 for the theoretical maximum number of 256 vectors.
387 comment "ROM configuration"
390 bool "Specify ROM linker regions"
393 Define a ROM region for the linker script. This creates a kernel
394 that can be stored in flash, with possibly the text, and data
395 regions being copied out to RAM at startup.
398 hex "Address of the base of ROM device"
402 Define the address that the ROM region starts at. Some platforms
403 use this to set their chip select region accordingly for the boot
407 hex "Address of the base of the ROM vectors"
411 This is almost always the same as the base of the ROM. Since on all
412 68000 type variants the vectors are at the base of the boot device
416 hex "Address of the base of system image in ROM"
420 Define the start address of the system image in ROM. Commonly this
421 is strait after the ROM vectors.
424 hex "Size of the ROM device"
428 Size of the ROM device. On some platforms this is used to setup
429 the chip select that controls the boot ROM device.
432 prompt "Kernel executes from"
434 Choose the memory type that the kernel will be running in.
439 The kernel will be resident in RAM when running.
444 The kernel will be resident in FLASH/ROM when running. This is
445 often referred to as Execute-in-Place (XIP), since the kernel
446 code executes from the position it is stored in the FLASH/ROM.