xref: /openbmc/linux/arch/m68k/Kconfig.machine (revision b6bec26c) 
1comment "Machine Types"
2
3if M68KCLASSIC
4
5config 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
14config 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
24config 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
36config 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
44config 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
54config 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
64config 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
75config 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
85config 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
96config 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
110config 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
121config 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
135endif # M68KCLASSIC
136
137config PILOT
138	bool
139
140config 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
147config XCOPILOT_BUGS
148	bool "(X)Copilot support"
149	depends on PILOT3
150	help
151	  Support the bugs of Xcopilot.
152
153config UC5272
154	bool "Arcturus Networks uC5272 dimm board support"
155	depends on M5272
156	help
157	  Support for the Arcturus Networks uC5272 dimm board.
158
159config UC5282
160	bool "Arcturus Networks uC5282 board support"
161	depends on M528x
162	help
163	  Support for the Arcturus Networks uC5282 dimm board.
164
165config UCSIMM
166	bool "uCsimm module support"
167	depends on M68EZ328
168	help
169	  Support for the Arcturus Networks uCsimm module.
170
171config UCDIMM
172	bool "uDsimm module support"
173	depends on M68VZ328
174	help
175	  Support for the Arcturus Networks uDsimm module.
176
177config DRAGEN2
178	bool "DragenEngine II board support"
179	depends on M68VZ328
180	help
181	  Support for the DragenEngine II board.
182
183config DIRECT_IO_ACCESS
184	bool "Allow user to access IO directly"
185	depends on (UCSIMM || UCDIMM || DRAGEN2)
186	help
187	  Disable the CPU internal registers protection in user mode,
188	  to allow a user application to read/write them.
189
190config INIT_LCD
191	bool "Initialize LCD"
192	depends on (UCSIMM || UCDIMM || DRAGEN2)
193	help
194	  Initialize the LCD controller of the 68x328 processor.
195
196config MEMORY_RESERVE
197	int "Memory reservation (MiB)"
198	depends on (UCSIMM || UCDIMM)
199	help
200	  Reserve certain memory regions on 68x328 based boards.
201
202config UCQUICC
203	bool "Lineo uCquicc board support"
204	depends on M68360
205	help
206	  Support for the Lineo uCquicc board.
207
208config ARNEWSH
209	bool
210
211config ARN5206
212	bool "Arnewsh 5206 board support"
213	depends on M5206
214	select ARNEWSH
215	help
216	  Support for the Arnewsh 5206 board.
217
218config FREESCALE
219	bool
220
221config M5206eC3
222	bool "Motorola M5206eC3 board support"
223	depends on M5206e
224	select FREESCALE
225	help
226	  Support for the Motorola M5206eC3 board.
227
228config ELITE
229	bool "Motorola M5206eLITE board support"
230	depends on M5206e
231	help
232	  Support for the Motorola M5206eLITE board.
233
234config M5208EVB
235	bool "Freescale M5208EVB board support"
236	depends on M520x
237	select FREESCALE
238	help
239	  Support for the Freescale Coldfire M5208EVB.
240
241config M5235EVB
242	bool "Freescale M5235EVB support"
243	depends on M523x
244	select FREESCALE
245	help
246	  Support for the Freescale M5235EVB board.
247
248config M5249C3
249	bool "Motorola M5249C3 board support"
250	depends on M5249
251	select FREESCALE
252	help
253	  Support for the Motorola M5249C3 board.
254
255config M5271EVB
256	bool "Freescale (Motorola) M5271EVB board support"
257	depends on M5271
258	select FREESCALE
259	help
260	  Support for the Freescale (Motorola) M5271EVB board.
261
262config M5275EVB
263	bool "Freescale (Motorola) M5275EVB board support"
264	depends on M5275
265	select FREESCALE
266	help
267	  Support for the Freescale (Motorola) M5275EVB board.
268
269config M5272C3
270	bool "Motorola M5272C3 board support"
271	depends on M5272
272	select FREESCALE
273	help
274	  Support for the Motorola M5272C3 board.
275
276config senTec
277	bool
278
279config COBRA5272
280	bool "senTec COBRA5272 board support"
281	depends on M5272
282	select senTec
283	help
284	  Support for the senTec COBRA5272 board.
285
286config AVNET
287	bool
288
289config AVNET5282
290	bool "Avnet 5282 board support"
291	depends on M528x
292	select AVNET
293	help
294	  Support for the Avnet 5282 board.
295
296config M5282EVB
297	bool "Motorola M5282EVB board support"
298	depends on M528x
299	select FREESCALE
300	help
301	  Support for the Motorola M5282EVB board.
302
303config COBRA5282
304	bool "senTec COBRA5282 board support"
305	depends on M528x
306	select senTec
307	help
308	  Support for the senTec COBRA5282 board.
309
310config SOM5282EM
311	bool "EMAC.Inc SOM5282EM board support"
312	depends on M528x
313	select EMAC_INC
314	help
315	  Support for the EMAC.Inc SOM5282EM module.
316
317config WILDFIRE
318	bool "Intec Automation Inc. WildFire board support"
319	depends on M528x
320	help
321	  Support for the Intec Automation Inc. WildFire.
322
323config WILDFIREMOD
324	bool "Intec Automation Inc. WildFire module support"
325	depends on M528x
326	help
327	  Support for the Intec Automation Inc. WildFire module.
328
329config ARN5307
330	bool "Arnewsh 5307 board support"
331	depends on M5307
332	select ARNEWSH
333	help
334	  Support for the Arnewsh 5307 board.
335
336config M5307C3
337	bool "Motorola M5307C3 board support"
338	depends on M5307
339	select FREESCALE
340	help
341	  Support for the Motorola M5307C3 board.
342
343config SECUREEDGEMP3
344	bool "SnapGear SecureEdge/MP3 platform support"
345	depends on M5307
346	help
347	  Support for the SnapGear SecureEdge/MP3 platform.
348
349config M5329EVB
350	bool "Freescale (Motorola) M5329EVB board support"
351	depends on M532x
352	select FREESCALE
353	help
354	  Support for the Freescale (Motorola) M5329EVB board.
355
356config COBRA5329
357	bool "senTec COBRA5329 board support"
358	depends on M532x
359	help
360	  Support for the senTec COBRA5329 board.
361
362config M5407C3
363	bool "Motorola M5407C3 board support"
364	depends on M5407
365	select FREESCALE
366	help
367	  Support for the Motorola M5407C3 board.
368
369config FIREBEE
370	bool "FireBee board support"
371	depends on M547x
372	help
373	  Support for the FireBee ColdFire 5475 based board.
374
375config CLEOPATRA
376	bool "Feith CLEOPATRA board support"
377	depends on (M5307 || M5407)
378	help
379	  Support for the Feith Cleopatra boards.
380
381config CANCam
382	bool "Feith CANCam board support"
383	depends on M5272
384	help
385	  Support for the Feith CANCam board.
386
387config SCALES
388	bool "Feith SCALES board support"
389	depends on M5272
390	help
391	  Support for the Feith SCALES board.
392
393config NETtel
394	bool "SecureEdge/NETtel board support"
395	depends on (M5206e || M5272 || M5307)
396	help
397	  Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
398
399config SNAPGEAR
400	bool "SnapGear router board support"
401	depends on NETtel
402	help
403	  Special additional support for SnapGear router boards.
404
405config SNEHA
406	bool
407
408config CPU16B
409	bool "Sneha Technologies S.L. Sarasvati board support"
410	depends on M5272
411	select SNEHA
412	help
413	  Support for the SNEHA CPU16B board.
414
415config MOD5272
416	bool "Netburner MOD-5272 board support"
417	depends on M5272
418	help
419	  Support for the Netburner MOD-5272 board.
420
421config SAVANT
422	bool
423
424config SAVANTrosie1
425	bool "Savant Rosie1 board support"
426	depends on M523x
427	select SAVANT
428	help
429	  Support for the Savant Rosie1 board.
430
431
432if !MMU || COLDFIRE
433
434comment "Machine Options"
435
436config UBOOT
437	bool "Support for U-Boot command line parameters"
438	help
439	  If you say Y here kernel will try to collect command
440	  line parameters from the initial u-boot stack.
441	default n
442
443config 4KSTACKS
444	bool "Use 4Kb for kernel stacks instead of 8Kb"
445	default y
446	help
447	  If you say Y here the kernel will use a 4Kb stacksize for the
448	  kernel stack attached to each process/thread. This facilitates
449	  running more threads on a system and also reduces the pressure
450	  on the VM subsystem for higher order allocations.
451
452comment "RAM configuration"
453
454config RAMBASE
455	hex "Address of the base of RAM"
456	default "0"
457	help
458	  Define the address that RAM starts at. On many platforms this is
459	  0, the base of the address space. And this is the default. Some
460	  platforms choose to setup their RAM at other addresses within the
461	  processor address space.
462
463config RAMSIZE
464	hex "Size of RAM (in bytes), or 0 for automatic"
465	default "0x400000"
466	help
467	  Define the size of the system RAM. If you select 0 then the
468	  kernel will try to probe the RAM size at runtime. This is not
469	  supported on all CPU types.
470
471config VECTORBASE
472	hex "Address of the base of system vectors"
473	default "0"
474	help
475	  Define the address of the system vectors. Commonly this is
476	  put at the start of RAM, but it doesn't have to be. On ColdFire
477	  platforms this address is programmed into the VBR register, thus
478	  actually setting the address to use.
479
480config MBAR
481	hex "Address of the MBAR (internal peripherals)"
482	default "0x10000000"
483	depends on HAVE_MBAR
484	help
485	  Define the address of the internal system peripherals. This value
486	  is set in the processors MBAR register. This is generally setup by
487	  the boot loader, and will not be written by the kernel. By far most
488	  ColdFire boards use the default 0x10000000 value, so if unsure then
489	  use this.
490
491config IPSBAR
492	hex "Address of the IPSBAR (internal peripherals)"
493	default "0x40000000"
494	depends on HAVE_IPSBAR
495	help
496	  Define the address of the internal system peripherals. This value
497	  is set in the processors IPSBAR register. This is generally setup by
498	  the boot loader, and will not be written by the kernel. By far most
499	  ColdFire boards use the default 0x40000000 value, so if unsure then
500	  use this.
501
502config KERNELBASE
503	hex "Address of the base of kernel code"
504	default "0x400"
505	help
506	  Typically on m68k systems the kernel will not start at the base
507	  of RAM, but usually some small offset from it. Define the start
508	  address of the kernel here. The most common setup will have the
509	  processor vectors at the base of RAM and then the start of the
510	  kernel. On some platforms some RAM is reserved for boot loaders
511	  and the kernel starts after that. The 0x400 default was based on
512	  a system with the RAM based at address 0, and leaving enough room
513	  for the theoretical maximum number of 256 vectors.
514
515comment "ROM configuration"
516
517config ROM
518	bool "Specify ROM linker regions"
519	default n
520	help
521	  Define a ROM region for the linker script. This creates a kernel
522	  that can be stored in flash, with possibly the text, and data
523	  regions being copied out to RAM at startup.
524
525config ROMBASE
526	hex "Address of the base of ROM device"
527	default "0"
528	depends on ROM
529	help
530	  Define the address that the ROM region starts at. Some platforms
531	  use this to set their chip select region accordingly for the boot
532	  device.
533
534config ROMVEC
535	hex "Address of the base of the ROM vectors"
536	default "0"
537	depends on ROM
538	help
539	  This is almost always the same as the base of the ROM. Since on all
540	  68000 type variants the vectors are at the base of the boot device
541	  on system startup.
542
543config ROMVECSIZE
544	hex "Size of ROM vector region (in bytes)"
545	default "0x400"
546	depends on ROM
547	help
548	  Define the size of the vector region in ROM. For most 68000
549	  variants this would be 0x400 bytes in size. Set to 0 if you do
550	  not want a vector region at the start of the ROM.
551
552config ROMSTART
553	hex "Address of the base of system image in ROM"
554	default "0x400"
555	depends on ROM
556	help
557	  Define the start address of the system image in ROM. Commonly this
558	  is strait after the ROM vectors.
559
560config ROMSIZE
561	hex "Size of the ROM device"
562	default "0x100000"
563	depends on ROM
564	help
565	  Size of the ROM device. On some platforms this is used to setup
566	  the chip select that controls the boot ROM device.
567
568choice
569	prompt "Kernel executes from"
570	---help---
571	  Choose the memory type that the kernel will be running in.
572
573config RAMKERNEL
574	bool "RAM"
575	help
576	  The kernel will be resident in RAM when running.
577
578config ROMKERNEL
579	bool "ROM"
580	help
581	  The kernel will be resident in FLASH/ROM when running. This is
582	  often referred to as Execute-in-Place (XIP), since the kernel
583	  code executes from the position it is stored in the FLASH/ROM.
584
585endchoice
586
587endif
588