Version:  2.0.40 2.2.26 2.4.37 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8

Linux/arch/m68k/Kconfig.machine

  1 comment "Machine Types"
  2 
  3 if M68KCLASSIC
  4 
  5 config 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 
 14 config 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 
 24 config 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 
 36 config 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 
 44 config 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 
 54 config 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 
 64 config 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 
 75 config 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 
 85 config 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 
 96 config 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 
110 config 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 
121 config 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 
135 endif # M68KCLASSIC
136 
137 config PILOT
138         bool
139 
140 config 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 
147 config XCOPILOT_BUGS
148         bool "(X)Copilot support"
149         depends on PILOT3
150         help
151           Support the bugs of Xcopilot.
152 
153 config UCSIMM
154         bool "uCsimm module support"
155         depends on M68EZ328
156         help
157           Support for the Arcturus Networks uCsimm module.
158 
159 config UCDIMM
160         bool "uDsimm module support"
161         depends on M68VZ328
162         help
163           Support for the Arcturus Networks uDsimm module.
164 
165 config DRAGEN2
166         bool "DragenEngine II board support"
167         depends on M68VZ328
168         help
169           Support for the DragenEngine II board.
170 
171 config 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 
178 config INIT_LCD
179         bool "Initialize LCD"
180         depends on (UCSIMM || UCDIMM || DRAGEN2)
181         help
182           Initialize the LCD controller of the 68x328 processor.
183 
184 config MEMORY_RESERVE
185         int "Memory reservation (MiB)"
186         depends on (UCSIMM || UCDIMM)
187         help
188           Reserve certain memory regions on 68x328 based boards.
189 
190 config ARN5206
191         bool "Arnewsh 5206 board support"
192         depends on M5206
193         help
194           Support for the Arnewsh 5206 board.
195 
196 config M5206eC3
197         bool "Motorola M5206eC3 board support"
198         depends on M5206e
199         help
200           Support for the Motorola M5206eC3 board.
201 
202 config ELITE
203         bool "Motorola M5206eLITE board support"
204         depends on M5206e
205         help
206           Support for the Motorola M5206eLITE board.
207 
208 config M5235EVB
209         bool "Freescale M5235EVB support"
210         depends on M523x
211         help
212           Support for the Freescale M5235EVB board.
213 
214 config M5249C3
215         bool "Motorola M5249C3 board support"
216         depends on M5249
217         help
218           Support for the Motorola M5249C3 board.
219 
220 config M5272C3
221         bool "Motorola M5272C3 board support"
222         depends on M5272
223         help
224           Support for the Motorola M5272C3 board.
225 
226 config WILDFIRE
227         bool "Intec Automation Inc. WildFire board support"
228         depends on M528x
229         help
230           Support for the Intec Automation Inc. WildFire.
231 
232 config WILDFIREMOD
233         bool "Intec Automation Inc. WildFire module support"
234         depends on M528x
235         help
236           Support for the Intec Automation Inc. WildFire module.
237 
238 config ARN5307
239         bool "Arnewsh 5307 board support"
240         depends on M5307
241         help
242           Support for the Arnewsh 5307 board.
243 
244 config M5307C3
245         bool "Motorola M5307C3 board support"
246         depends on M5307
247         help
248           Support for the Motorola M5307C3 board.
249 
250 config SECUREEDGEMP3
251         bool "SnapGear SecureEdge/MP3 platform support"
252         depends on M5307
253         help
254           Support for the SnapGear SecureEdge/MP3 platform.
255 
256 config M5407C3
257         bool "Motorola M5407C3 board support"
258         depends on M5407
259         help
260           Support for the Motorola M5407C3 board.
261 
262 config FIREBEE
263         bool "FireBee board support"
264         depends on M547x
265         help
266           Support for the FireBee ColdFire 5475 based board.
267 
268 config CLEOPATRA
269         bool "Feith CLEOPATRA board support"
270         depends on (M5307 || M5407)
271         help
272           Support for the Feith Cleopatra boards.
273 
274 config CANCam
275         bool "Feith CANCam board support"
276         depends on M5272
277         help
278           Support for the Feith CANCam board.
279 
280 config SCALES
281         bool "Feith SCALES board support"
282         depends on M5272
283         help
284           Support for the Feith SCALES board.
285 
286 config NETtel
287         bool "SecureEdge/NETtel board support"
288         depends on (M5206e || M5272 || M5307)
289         help
290           Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
291 
292 config MOD5272
293         bool "Netburner MOD-5272 board support"
294         depends on M5272
295         help
296           Support for the Netburner MOD-5272 board.
297 
298 if !MMU || COLDFIRE
299 
300 comment "Machine Options"
301 
302 config UBOOT
303         bool "Support for U-Boot command line parameters"
304         help
305           If you say Y here kernel will try to collect command
306           line parameters from the initial u-boot stack.
307         default n
308 
309 config 4KSTACKS
310         bool "Use 4Kb for kernel stacks instead of 8Kb"
311         default y
312         help
313           If you say Y here the kernel will use a 4Kb stacksize for the
314           kernel stack attached to each process/thread. This facilitates
315           running more threads on a system and also reduces the pressure
316           on the VM subsystem for higher order allocations.
317 
318 comment "RAM configuration"
319 
320 config RAMBASE
321         hex "Address of the base of RAM"
322         default "0"
323         help
324           Define the address that RAM starts at. On many platforms this is
325           0, the base of the address space. And this is the default. Some
326           platforms choose to setup their RAM at other addresses within the
327           processor address space.
328 
329 config RAMSIZE
330         hex "Size of RAM (in bytes), or 0 for automatic"
331         default "0x400000"
332         help
333           Define the size of the system RAM. If you select 0 then the
334           kernel will try to probe the RAM size at runtime. This is not
335           supported on all CPU types.
336 
337 config VECTORBASE
338         hex "Address of the base of system vectors"
339         default "0"
340         help
341           Define the address of the system vectors. Commonly this is
342           put at the start of RAM, but it doesn't have to be. On ColdFire
343           platforms this address is programmed into the VBR register, thus
344           actually setting the address to use.
345 
346 config MBAR
347         hex "Address of the MBAR (internal peripherals)"
348         default "0x10000000"
349         depends on HAVE_MBAR
350         help
351           Define the address of the internal system peripherals. This value
352           is set in the processors MBAR register. This is generally setup by
353           the boot loader, and will not be written by the kernel. By far most
354           ColdFire boards use the default 0x10000000 value, so if unsure then
355           use this.
356 
357 config IPSBAR
358         hex "Address of the IPSBAR (internal peripherals)"
359         default "0x40000000"
360         depends on HAVE_IPSBAR
361         help
362           Define the address of the internal system peripherals. This value
363           is set in the processors IPSBAR register. This is generally setup by
364           the boot loader, and will not be written by the kernel. By far most
365           ColdFire boards use the default 0x40000000 value, so if unsure then
366           use this.
367 
368 config KERNELBASE
369         hex "Address of the base of kernel code"
370         default "0x400"
371         help
372           Typically on m68k systems the kernel will not start at the base
373           of RAM, but usually some small offset from it. Define the start
374           address of the kernel here. The most common setup will have the
375           processor vectors at the base of RAM and then the start of the
376           kernel. On some platforms some RAM is reserved for boot loaders
377           and the kernel starts after that. The 0x400 default was based on
378           a system with the RAM based at address 0, and leaving enough room
379           for the theoretical maximum number of 256 vectors.
380 
381 comment "ROM configuration"
382 
383 config ROM
384         bool "Specify ROM linker regions"
385         default n
386         help
387           Define a ROM region for the linker script. This creates a kernel
388           that can be stored in flash, with possibly the text, and data
389           regions being copied out to RAM at startup.
390 
391 config ROMBASE
392         hex "Address of the base of ROM device"
393         default "0"
394         depends on ROM
395         help
396           Define the address that the ROM region starts at. Some platforms
397           use this to set their chip select region accordingly for the boot
398           device.
399 
400 config ROMVEC
401         hex "Address of the base of the ROM vectors"
402         default "0"
403         depends on ROM
404         help
405           This is almost always the same as the base of the ROM. Since on all
406           68000 type variants the vectors are at the base of the boot device
407           on system startup.
408 
409 config ROMSTART
410         hex "Address of the base of system image in ROM"
411         default "0x400"
412         depends on ROM
413         help
414           Define the start address of the system image in ROM. Commonly this
415           is strait after the ROM vectors.
416 
417 config ROMSIZE
418         hex "Size of the ROM device"
419         default "0x100000"
420         depends on ROM
421         help
422           Size of the ROM device. On some platforms this is used to setup
423           the chip select that controls the boot ROM device.
424 
425 choice
426         prompt "Kernel executes from"
427         ---help---
428           Choose the memory type that the kernel will be running in.
429 
430 config RAMKERNEL
431         bool "RAM"
432         help
433           The kernel will be resident in RAM when running.
434 
435 config ROMKERNEL
436         bool "ROM"
437         help
438           The kernel will be resident in FLASH/ROM when running. This is
439           often referred to as Execute-in-Place (XIP), since the kernel
440           code executes from the position it is stored in the FLASH/ROM.
441 
442 endchoice
443 
444 endif

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us