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)
189 Reserve certain memory regions on 68x328 based boards.
192 bool "Arnewsh 5206 board support"
195 Support for the Arnewsh 5206 board.
198 bool "Motorola M5206eC3 board support"
201 Support for the Motorola M5206eC3 board.
204 bool "Motorola M5206eLITE board support"
207 Support for the Motorola M5206eLITE board.
210 bool "Freescale M5235EVB support"
213 Support for the Freescale M5235EVB board.
216 bool "Motorola M5249C3 board support"
219 Support for the Motorola M5249C3 board.
222 bool "Motorola M5272C3 board support"
225 Support for the Motorola M5272C3 board.
228 bool "Intec Automation Inc. WildFire board support"
231 Support for the Intec Automation Inc. WildFire.
234 bool "Intec Automation Inc. WildFire module support"
237 Support for the Intec Automation Inc. WildFire module.
240 bool "Arnewsh 5307 board support"
243 Support for the Arnewsh 5307 board.
246 bool "Motorola M5307C3 board support"
249 Support for the Motorola M5307C3 board.
252 bool "SnapGear SecureEdge/MP3 platform support"
255 Support for the SnapGear SecureEdge/MP3 platform.
258 bool "Motorola M5407C3 board support"
261 Support for the Motorola M5407C3 board.
264 bool "FireBee board support"
267 Support for the FireBee ColdFire 5475 based board.
270 bool "Feith CLEOPATRA board support"
271 depends on (M5307 || M5407)
273 Support for the Feith Cleopatra boards.
276 bool "Feith CANCam board support"
279 Support for the Feith CANCam board.
282 bool "Feith SCALES board support"
285 Support for the Feith SCALES board.
288 bool "SecureEdge/NETtel board support"
289 depends on (M5206e || M5272 || M5307)
291 Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
294 bool "Netburner MOD-5272 board support"
297 Support for the Netburner MOD-5272 board.
301 comment "Machine Options"
304 bool "Support for U-Boot command line parameters"
306 If you say Y here kernel will try to collect command
307 line parameters from the initial u-boot stack.
311 bool "Use 4Kb for kernel stacks instead of 8Kb"
314 If you say Y here the kernel will use a 4Kb stacksize for the
315 kernel stack attached to each process/thread. This facilitates
316 running more threads on a system and also reduces the pressure
317 on the VM subsystem for higher order allocations.
319 comment "RAM configuration"
322 hex "Address of the base of RAM"
325 Define the address that RAM starts at. On many platforms this is
326 0, the base of the address space. And this is the default. Some
327 platforms choose to setup their RAM at other addresses within the
328 processor address space.
331 hex "Size of RAM (in bytes), or 0 for automatic"
334 Define the size of the system RAM. If you select 0 then the
335 kernel will try to probe the RAM size at runtime. This is not
336 supported on all CPU types.
339 hex "Address of the base of system vectors"
342 Define the address of the system vectors. Commonly this is
343 put at the start of RAM, but it doesn't have to be. On ColdFire
344 platforms this address is programmed into the VBR register, thus
345 actually setting the address to use.
348 hex "Address of the MBAR (internal peripherals)"
352 Define the address of the internal system peripherals. This value
353 is set in the processors MBAR register. This is generally setup by
354 the boot loader, and will not be written by the kernel. By far most
355 ColdFire boards use the default 0x10000000 value, so if unsure then
359 hex "Address of the IPSBAR (internal peripherals)"
361 depends on HAVE_IPSBAR
363 Define the address of the internal system peripherals. This value
364 is set in the processors IPSBAR register. This is generally setup by
365 the boot loader, and will not be written by the kernel. By far most
366 ColdFire boards use the default 0x40000000 value, so if unsure then
370 hex "Address of the base of kernel code"
373 Typically on m68k systems the kernel will not start at the base
374 of RAM, but usually some small offset from it. Define the start
375 address of the kernel here. The most common setup will have the
376 processor vectors at the base of RAM and then the start of the
377 kernel. On some platforms some RAM is reserved for boot loaders
378 and the kernel starts after that. The 0x400 default was based on
379 a system with the RAM based at address 0, and leaving enough room
380 for the theoretical maximum number of 256 vectors.
382 comment "ROM configuration"
385 bool "Specify ROM linker regions"
388 Define a ROM region for the linker script. This creates a kernel
389 that can be stored in flash, with possibly the text, and data
390 regions being copied out to RAM at startup.
393 hex "Address of the base of ROM device"
397 Define the address that the ROM region starts at. Some platforms
398 use this to set their chip select region accordingly for the boot
402 hex "Address of the base of the ROM vectors"
406 This is almost always the same as the base of the ROM. Since on all
407 68000 type variants the vectors are at the base of the boot device
411 hex "Address of the base of system image in ROM"
415 Define the start address of the system image in ROM. Commonly this
416 is strait after the ROM vectors.
419 hex "Size of the ROM device"
423 Size of the ROM device. On some platforms this is used to setup
424 the chip select that controls the boot ROM device.
427 prompt "Kernel executes from"
429 Choose the memory type that the kernel will be running in.
434 The kernel will be resident in RAM when running.
439 The kernel will be resident in FLASH/ROM when running. This is
440 often referred to as Execute-in-Place (XIP), since the kernel
441 code executes from the position it is stored in the FLASH/ROM.