xref: /openbmc/linux/arch/m68k/Kconfig.machine (revision 2209fda3) 
1# SPDX-License-Identifier: GPL-2.0
2comment "Machine Types"
3
4if M68KCLASSIC
5
6config AMIGA
7	bool "Amiga support"
8	depends on MMU
9	select MMU_MOTOROLA if MMU
10	help
11	  This option enables support for the Amiga series of computers. If
12	  you plan to use this kernel on an Amiga, say Y here and browse the
13	  material available in <file:Documentation/m68k>; otherwise say N.
14
15config ATARI
16	bool "Atari support"
17	depends on MMU
18	select MMU_MOTOROLA if MMU
19	help
20	  This option enables support for the 68000-based Atari series of
21	  computers (including the TT, Falcon and Medusa). If you plan to use
22	  this kernel on an Atari, say Y here and browse the material
23	  available in <file:Documentation/m68k>; otherwise say N.
24
25config MAC
26	bool "Macintosh support"
27	depends on MMU
28	select MMU_MOTOROLA if MMU
29	help
30	  This option enables support for the Apple Macintosh series of
31	  computers (yes, there is experimental support now, at least for part
32	  of the series).
33
34	  Say N unless you're willing to code the remaining necessary support.
35	  ;)
36
37config APOLLO
38	bool "Apollo support"
39	depends on MMU
40	select MMU_MOTOROLA if MMU
41	help
42	  Say Y here if you want to run Linux on an MC680x0-based Apollo
43	  Domain workstation such as the DN3500.
44
45config VME
46	bool "VME (Motorola and BVM) support"
47	depends on MMU
48	select MMU_MOTOROLA if MMU
49	help
50	  Say Y here if you want to build a kernel for a 680x0 based VME
51	  board.  Boards currently supported include Motorola boards MVME147,
52	  MVME162, MVME166, MVME167, MVME172, and MVME177.  BVME4000 and
53	  BVME6000 boards from BVM Ltd are also supported.
54
55config MVME147
56	bool "MVME147 support"
57	depends on MMU
58	depends on VME
59	help
60	  Say Y to include support for early Motorola VME boards.  This will
61	  build a kernel which can run on MVME147 single-board computers.  If
62	  you select this option you will have to select the appropriate
63	  drivers for SCSI, Ethernet and serial ports later on.
64
65config MVME16x
66	bool "MVME162, 166 and 167 support"
67	depends on MMU
68	depends on VME
69	help
70	  Say Y to include support for Motorola VME boards.  This will build a
71	  kernel which can run on MVME162, MVME166, MVME167, MVME172, and
72	  MVME177 boards.  If you select this option you will have to select
73	  the appropriate drivers for SCSI, Ethernet and serial ports later
74	  on.
75
76config BVME6000
77	bool "BVME4000 and BVME6000 support"
78	depends on MMU
79	depends on VME
80	help
81	  Say Y to include support for VME boards from BVM Ltd.  This will
82	  build a kernel which can run on BVME4000 and BVME6000 boards.  If
83	  you select this option you will have to select the appropriate
84	  drivers for SCSI, Ethernet and serial ports later on.
85
86config HP300
87	bool "HP9000/300 and HP9000/400 support"
88	depends on MMU
89	select MMU_MOTOROLA if MMU
90	help
91	  This option enables support for the HP9000/300 and HP9000/400 series
92	  of workstations. Support for these machines is still somewhat
93	  experimental. If you plan to try to use the kernel on such a machine
94	  say Y here.
95	  Everybody else says N.
96
97config SUN3X
98	bool "Sun3x support"
99	depends on MMU
100	select MMU_MOTOROLA if MMU
101	select M68030
102	help
103	  This option enables support for the Sun 3x series of workstations.
104	  Be warned that this support is very experimental.
105	  Note that Sun 3x kernels are not compatible with Sun 3 hardware.
106	  General Linux information on the Sun 3x series (now discontinued)
107	  is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
108
109	  If you don't want to compile a kernel for a Sun 3x, say N.
110
111config Q40
112	bool "Q40/Q60 support"
113	depends on MMU
114	select MMU_MOTOROLA if MMU
115	help
116	  The Q40 is a Motorola 68040-based successor to the Sinclair QL
117	  manufactured in Germany.  There is an official Q40 home page at
118	  <http://www.q40.de/>.  This option enables support for the Q40 and
119	  Q60. Select your CPU below.  For 68LC060 don't forget to enable FPU
120	  emulation.
121
122config SUN3
123	bool "Sun3 support"
124	depends on MMU
125	depends on !MMU_MOTOROLA
126	select MMU_SUN3 if MMU
127	select M68020
128	help
129	  This option enables support for the Sun 3 series of workstations
130	  (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
131	  that all other hardware types must be disabled, as Sun 3 kernels
132	  are incompatible with all other m68k targets (including Sun 3x!).
133
134	  If you don't want to compile a kernel exclusively for a Sun 3, say N.
135
136endif # M68KCLASSIC
137
138config PILOT
139	bool
140
141config PILOT3
142	bool "Pilot 1000/5000, PalmPilot Personal/Pro, or PalmIII support"
143	depends on M68328
144	select PILOT
145	help
146	  Support for the Palm Pilot 1000/5000, Personal/Pro and PalmIII.
147
148config XCOPILOT_BUGS
149	bool "(X)Copilot support"
150	depends on PILOT3
151	help
152	  Support the bugs of Xcopilot.
153
154config UCSIMM
155	bool "uCsimm module support"
156	depends on M68EZ328
157	help
158	  Support for the Arcturus Networks uCsimm module.
159
160config UCDIMM
161	bool "uDsimm module support"
162	depends on M68VZ328
163	help
164	  Support for the Arcturus Networks uDsimm module.
165
166config DRAGEN2
167	bool "DragenEngine II board support"
168	depends on M68VZ328
169	help
170	  Support for the DragenEngine II board.
171
172config DIRECT_IO_ACCESS
173	bool "Allow user to access IO directly"
174	depends on (UCSIMM || UCDIMM || DRAGEN2)
175	help
176	  Disable the CPU internal registers protection in user mode,
177	  to allow a user application to read/write them.
178
179config INIT_LCD
180	bool "Initialize LCD"
181	depends on (UCSIMM || UCDIMM || DRAGEN2)
182	help
183	  Initialize the LCD controller of the 68x328 processor.
184
185config MEMORY_RESERVE
186	int "Memory reservation (MiB)"
187	depends on (UCSIMM || UCDIMM)
188	help
189	  Reserve certain memory regions on 68x328 based boards.
190
191config ARN5206
192	bool "Arnewsh 5206 board support"
193	depends on M5206
194	help
195	  Support for the Arnewsh 5206 board.
196
197config M5206eC3
198	bool "Motorola M5206eC3 board support"
199	depends on M5206e
200	help
201	  Support for the Motorola M5206eC3 board.
202
203config ELITE
204	bool "Motorola M5206eLITE board support"
205	depends on M5206e
206	help
207	  Support for the Motorola M5206eLITE board.
208
209config M5235EVB
210	bool "Freescale M5235EVB support"
211	depends on M523x
212	help
213	  Support for the Freescale M5235EVB board.
214
215config M5249C3
216	bool "Motorola M5249C3 board support"
217	depends on M5249
218	help
219	  Support for the Motorola M5249C3 board.
220
221config M5272C3
222	bool "Motorola M5272C3 board support"
223	depends on M5272
224	help
225	  Support for the Motorola M5272C3 board.
226
227config WILDFIRE
228	bool "Intec Automation Inc. WildFire board support"
229	depends on M528x
230	help
231	  Support for the Intec Automation Inc. WildFire.
232
233config WILDFIREMOD
234	bool "Intec Automation Inc. WildFire module support"
235	depends on M528x
236	help
237	  Support for the Intec Automation Inc. WildFire module.
238
239config ARN5307
240	bool "Arnewsh 5307 board support"
241	depends on M5307
242	help
243	  Support for the Arnewsh 5307 board.
244
245config M5307C3
246	bool "Motorola M5307C3 board support"
247	depends on M5307
248	help
249	  Support for the Motorola M5307C3 board.
250
251config SECUREEDGEMP3
252	bool "SnapGear SecureEdge/MP3 platform support"
253	depends on M5307
254	help
255	  Support for the SnapGear SecureEdge/MP3 platform.
256
257config M5407C3
258	bool "Motorola M5407C3 board support"
259	depends on M5407
260	help
261	  Support for the Motorola M5407C3 board.
262
263config AMCORE
264	bool "Sysam AMCORE board support"
265	depends on M5307
266	help
267	  Support for the Sysam AMCORE open-hardware generic board.
268
269config STMARK2
270        bool "Sysam stmark2 board support"
271        depends on M5441x
272        help
273          Support for the Sysam stmark2 open-hardware generic board.
274
275config FIREBEE
276	bool "FireBee board support"
277	depends on M547x
278	help
279	  Support for the FireBee ColdFire 5475 based board.
280
281config CLEOPATRA
282	bool "Feith CLEOPATRA board support"
283	depends on (M5307 || M5407)
284	help
285	  Support for the Feith Cleopatra boards.
286
287config CANCam
288	bool "Feith CANCam board support"
289	depends on M5272
290	help
291	  Support for the Feith CANCam board.
292
293config SCALES
294	bool "Feith SCALES board support"
295	depends on M5272
296	help
297	  Support for the Feith SCALES board.
298
299config NETtel
300	bool "SecureEdge/NETtel board support"
301	depends on (M5206e || M5272 || M5307)
302	help
303	  Support for the SnapGear NETtel/SecureEdge/SnapGear boards.
304
305config MOD5272
306	bool "Netburner MOD-5272 board support"
307	depends on M5272
308	help
309	  Support for the Netburner MOD-5272 board.
310
311if !MMU || COLDFIRE
312
313comment "Machine Options"
314
315config UBOOT
316	bool "Support for U-Boot command line parameters"
317	help
318	  If you say Y here kernel will try to collect command
319	  line parameters from the initial u-boot stack.
320	default n
321
322config 4KSTACKS
323	bool "Use 4Kb for kernel stacks instead of 8Kb"
324	default y
325	help
326	  If you say Y here the kernel will use a 4Kb stacksize for the
327	  kernel stack attached to each process/thread. This facilitates
328	  running more threads on a system and also reduces the pressure
329	  on the VM subsystem for higher order allocations.
330
331comment "RAM configuration"
332
333config RAMBASE
334	hex "Address of the base of RAM"
335	default "0"
336	help
337	  Define the address that RAM starts at. On many platforms this is
338	  0, the base of the address space. And this is the default. Some
339	  platforms choose to setup their RAM at other addresses within the
340	  processor address space.
341
342config RAMSIZE
343	hex "Size of RAM (in bytes), or 0 for automatic"
344	default "0x400000"
345	help
346	  Define the size of the system RAM. If you select 0 then the
347	  kernel will try to probe the RAM size at runtime. This is not
348	  supported on all CPU types.
349
350config VECTORBASE
351	hex "Address of the base of system vectors"
352	default "0"
353	help
354	  Define the address of the system vectors. Commonly this is
355	  put at the start of RAM, but it doesn't have to be. On ColdFire
356	  platforms this address is programmed into the VBR register, thus
357	  actually setting the address to use.
358
359config MBAR
360	hex "Address of the MBAR (internal peripherals)"
361	default "0x10000000"
362	depends on HAVE_MBAR
363	help
364	  Define the address of the internal system peripherals. This value
365	  is set in the processors MBAR register. This is generally setup by
366	  the boot loader, and will not be written by the kernel. By far most
367	  ColdFire boards use the default 0x10000000 value, so if unsure then
368	  use this.
369
370config IPSBAR
371	hex "Address of the IPSBAR (internal peripherals)"
372	default "0x40000000"
373	depends on HAVE_IPSBAR
374	help
375	  Define the address of the internal system peripherals. This value
376	  is set in the processors IPSBAR register. This is generally setup by
377	  the boot loader, and will not be written by the kernel. By far most
378	  ColdFire boards use the default 0x40000000 value, so if unsure then
379	  use this.
380
381config KERNELBASE
382	hex "Address of the base of kernel code"
383	default "0x400"
384	help
385	  Typically on m68k systems the kernel will not start at the base
386	  of RAM, but usually some small offset from it. Define the start
387	  address of the kernel here. The most common setup will have the
388	  processor vectors at the base of RAM and then the start of the
389	  kernel. On some platforms some RAM is reserved for boot loaders
390	  and the kernel starts after that. The 0x400 default was based on
391	  a system with the RAM based at address 0, and leaving enough room
392	  for the theoretical maximum number of 256 vectors.
393
394comment "ROM configuration"
395
396config ROM
397	bool "Specify ROM linker regions"
398	default n
399	help
400	  Define a ROM region for the linker script. This creates a kernel
401	  that can be stored in flash, with possibly the text, and data
402	  regions being copied out to RAM at startup.
403
404config ROMBASE
405	hex "Address of the base of ROM device"
406	default "0"
407	depends on ROM
408	help
409	  Define the address that the ROM region starts at. Some platforms
410	  use this to set their chip select region accordingly for the boot
411	  device.
412
413config ROMVEC
414	hex "Address of the base of the ROM vectors"
415	default "0"
416	depends on ROM
417	help
418	  This is almost always the same as the base of the ROM. Since on all
419	  68000 type variants the vectors are at the base of the boot device
420	  on system startup.
421
422config ROMSTART
423	hex "Address of the base of system image in ROM"
424	default "0x400"
425	depends on ROM
426	help
427	  Define the start address of the system image in ROM. Commonly this
428	  is strait after the ROM vectors.
429
430config ROMSIZE
431	hex "Size of the ROM device"
432	default "0x100000"
433	depends on ROM
434	help
435	  Size of the ROM device. On some platforms this is used to setup
436	  the chip select that controls the boot ROM device.
437
438choice
439	prompt "Kernel executes from"
440	---help---
441	  Choose the memory type that the kernel will be running in.
442
443config RAMKERNEL
444	bool "RAM"
445	help
446	  The kernel will be resident in RAM when running.
447
448config ROMKERNEL
449	bool "ROM"
450	help
451	  The kernel will be resident in FLASH/ROM when running. This is
452	  often referred to as Execute-in-Place (XIP), since the kernel
453	  code executes from the position it is stored in the FLASH/ROM.
454
455endchoice
456
457endif
458