1 =================================== 1 ===================================
2 Command Line Options for Linux/m68k 2 Command Line Options for Linux/m68k
3 =================================== 3 ===================================
4 4
5 Last Update: 2 May 1999 5 Last Update: 2 May 1999
6 6
7 Linux/m68k version: 2.2.6 7 Linux/m68k version: 2.2.6
8 8
9 Author: Roman.Hodek@informatik.uni-erlangen.de 9 Author: Roman.Hodek@informatik.uni-erlangen.de (Roman Hodek)
10 10
11 Update: jds@kom.auc.dk (Jes Sorensen) and faq@ 11 Update: jds@kom.auc.dk (Jes Sorensen) and faq@linux-m68k.org (Chris Lawrence)
12 12
13 0) Introduction 13 0) Introduction
14 =============== 14 ===============
15 15
16 Often I've been asked which command line optio 16 Often I've been asked which command line options the Linux/m68k
17 kernel understands, or how the exact syntax fo 17 kernel understands, or how the exact syntax for the ... option is, or
18 ... about the option ... . I hope, this docume 18 ... about the option ... . I hope, this document supplies all the
19 answers... 19 answers...
20 20
21 Note that some options might be outdated, thei 21 Note that some options might be outdated, their descriptions being
22 incomplete or missing. Please update the infor 22 incomplete or missing. Please update the information and send in the
23 patches. 23 patches.
24 24
25 25
26 1) Overview of the Kernel's Option Processing 26 1) Overview of the Kernel's Option Processing
27 ============================================= 27 =============================================
28 28
29 The kernel knows three kinds of options on its 29 The kernel knows three kinds of options on its command line:
30 30
31 1) kernel options 31 1) kernel options
32 2) environment settings 32 2) environment settings
33 3) arguments for init 33 3) arguments for init
34 34
35 To which of these classes an argument belongs 35 To which of these classes an argument belongs is determined as
36 follows: If the option is known to the kernel 36 follows: If the option is known to the kernel itself, i.e. if the name
37 (the part before the '=') or, in some cases, t 37 (the part before the '=') or, in some cases, the whole argument string
38 is known to the kernel, it belongs to class 1. 38 is known to the kernel, it belongs to class 1. Otherwise, if the
39 argument contains an '=', it is of class 2, an 39 argument contains an '=', it is of class 2, and the definition is put
40 into init's environment. All other arguments a 40 into init's environment. All other arguments are passed to init as
41 command line options. 41 command line options.
42 42
43 This document describes the valid kernel optio 43 This document describes the valid kernel options for Linux/m68k in
44 the version mentioned at the start of this fil 44 the version mentioned at the start of this file. Later revisions may
45 add new such options, and some may be missing 45 add new such options, and some may be missing in older versions.
46 46
47 In general, the value (the part after the '=') 47 In general, the value (the part after the '=') of an option is a
48 list of values separated by commas. The interp 48 list of values separated by commas. The interpretation of these values
49 is up to the driver that "owns" the option. Th 49 is up to the driver that "owns" the option. This association of
50 options with drivers is also the reason that s 50 options with drivers is also the reason that some are further
51 subdivided. 51 subdivided.
52 52
53 53
54 2) General Kernel Options 54 2) General Kernel Options
55 ========================= 55 =========================
56 56
57 2.1) root= 57 2.1) root=
58 ---------- 58 ----------
59 59
60 :Syntax: root=/dev/<device> 60 :Syntax: root=/dev/<device>
61 :or: root=<hex_number> 61 :or: root=<hex_number>
62 62
63 This tells the kernel which device it should m 63 This tells the kernel which device it should mount as the root
64 filesystem. The device must be a block device 64 filesystem. The device must be a block device with a valid filesystem
65 on it. 65 on it.
66 66
67 The first syntax gives the device by name. The 67 The first syntax gives the device by name. These names are converted
68 into a major/minor number internally in the ke 68 into a major/minor number internally in the kernel in an unusual way.
69 Normally, this "conversion" is done by the dev 69 Normally, this "conversion" is done by the device files in /dev, but
70 this isn't possible here, because the root fil 70 this isn't possible here, because the root filesystem (with /dev)
71 isn't mounted yet... So the kernel parses the 71 isn't mounted yet... So the kernel parses the name itself, with some
72 hardcoded name to number mappings. The name mu 72 hardcoded name to number mappings. The name must always be a
73 combination of two or three letters, followed 73 combination of two or three letters, followed by a decimal number.
74 Valid names are:: 74 Valid names are::
75 75
76 /dev/ram: -> 0x0100 (initial ramdisk) 76 /dev/ram: -> 0x0100 (initial ramdisk)
77 /dev/hda: -> 0x0300 (first IDE disk) 77 /dev/hda: -> 0x0300 (first IDE disk)
78 /dev/hdb: -> 0x0340 (second IDE disk) 78 /dev/hdb: -> 0x0340 (second IDE disk)
79 /dev/sda: -> 0x0800 (first SCSI disk) 79 /dev/sda: -> 0x0800 (first SCSI disk)
80 /dev/sdb: -> 0x0810 (second SCSI disk) 80 /dev/sdb: -> 0x0810 (second SCSI disk)
81 /dev/sdc: -> 0x0820 (third SCSI disk) 81 /dev/sdc: -> 0x0820 (third SCSI disk)
82 /dev/sdd: -> 0x0830 (forth SCSI disk) 82 /dev/sdd: -> 0x0830 (forth SCSI disk)
83 /dev/sde: -> 0x0840 (fifth SCSI disk) 83 /dev/sde: -> 0x0840 (fifth SCSI disk)
84 /dev/fd : -> 0x0200 (floppy disk) 84 /dev/fd : -> 0x0200 (floppy disk)
85 85
86 The name must be followed by a decimal number, 86 The name must be followed by a decimal number, that stands for the
87 partition number. Internally, the value of the 87 partition number. Internally, the value of the number is just
88 added to the device number mentioned in the ta 88 added to the device number mentioned in the table above. The
89 exceptions are /dev/ram and /dev/fd, where /de 89 exceptions are /dev/ram and /dev/fd, where /dev/ram refers to an
90 initial ramdisk loaded by your bootstrap progr 90 initial ramdisk loaded by your bootstrap program (please consult the
91 instructions for your bootstrap program to fin 91 instructions for your bootstrap program to find out how to load an
92 initial ramdisk). As of kernel version 2.0.18 92 initial ramdisk). As of kernel version 2.0.18 you must specify
93 /dev/ram as the root device if you want to boo 93 /dev/ram as the root device if you want to boot from an initial
94 ramdisk. For the floppy devices, /dev/fd, the 94 ramdisk. For the floppy devices, /dev/fd, the number stands for the
95 floppy drive number (there are no partitions o 95 floppy drive number (there are no partitions on floppy disks). I.e.,
96 /dev/fd0 stands for the first drive, /dev/fd1 96 /dev/fd0 stands for the first drive, /dev/fd1 for the second, and so
97 on. Since the number is just added, you can al 97 on. Since the number is just added, you can also force the disk format
98 by adding a number greater than 3. If you look 98 by adding a number greater than 3. If you look into your /dev
99 directory, use can see the /dev/fd0D720 has ma 99 directory, use can see the /dev/fd0D720 has major 2 and minor 16. You
100 can specify this device for the root FS by wri 100 can specify this device for the root FS by writing "root=/dev/fd16" on
101 the kernel command line. 101 the kernel command line.
102 102
103 [Strange and maybe uninteresting stuff ON] 103 [Strange and maybe uninteresting stuff ON]
104 104
105 This unusual translation of device names has s 105 This unusual translation of device names has some strange
106 consequences: If, for example, you have a symb 106 consequences: If, for example, you have a symbolic link from /dev/fd
107 to /dev/fd0D720 as an abbreviation for floppy 107 to /dev/fd0D720 as an abbreviation for floppy driver #0 in DD format,
108 you cannot use this name for specifying the ro 108 you cannot use this name for specifying the root device, because the
109 kernel cannot see this symlink before mounting 109 kernel cannot see this symlink before mounting the root FS and it
110 isn't in the table above. If you use it, the r 110 isn't in the table above. If you use it, the root device will not be
111 set at all, without an error message. Another 111 set at all, without an error message. Another example: You cannot use a
112 partition on e.g. the sixth SCSI disk as the r 112 partition on e.g. the sixth SCSI disk as the root filesystem, if you
113 want to specify it by name. This is, because o 113 want to specify it by name. This is, because only the devices up to
114 /dev/sde are in the table above, but not /dev/ 114 /dev/sde are in the table above, but not /dev/sdf. Although, you can
115 use the sixth SCSI disk for the root FS, but y 115 use the sixth SCSI disk for the root FS, but you have to specify the
116 device by number... (see below). Or, even more 116 device by number... (see below). Or, even more strange, you can use the
117 fact that there is no range checking of the pa 117 fact that there is no range checking of the partition number, and your
118 knowledge that each disk uses 16 minors, and w 118 knowledge that each disk uses 16 minors, and write "root=/dev/sde17"
119 (for /dev/sdf1). 119 (for /dev/sdf1).
120 120
121 [Strange and maybe uninteresting stuff OFF] 121 [Strange and maybe uninteresting stuff OFF]
122 122
123 If the device containing your root partition i 123 If the device containing your root partition isn't in the table
124 above, you can also specify it by major and mi 124 above, you can also specify it by major and minor numbers. These are
125 written in hex, with no prefix and no separato 125 written in hex, with no prefix and no separator between. E.g., if you
126 have a CD with contents appropriate as a root 126 have a CD with contents appropriate as a root filesystem in the first
127 SCSI CD-ROM drive, you boot from it by "root=0 127 SCSI CD-ROM drive, you boot from it by "root=0b00". Here, hex "0b" =
128 decimal 11 is the major of SCSI CD-ROMs, and t 128 decimal 11 is the major of SCSI CD-ROMs, and the minor 0 stands for
129 the first of these. You can find out all valid 129 the first of these. You can find out all valid major numbers by
130 looking into include/linux/major.h. 130 looking into include/linux/major.h.
131 131
132 In addition to major and minor numbers, if the 132 In addition to major and minor numbers, if the device containing your
133 root partition uses a partition table format w 133 root partition uses a partition table format with unique partition
134 identifiers, then you may use them. For insta 134 identifiers, then you may use them. For instance,
135 "root=PARTUUID=00112233-4455-6677-8899-AABBCCD 135 "root=PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF". It is also
136 possible to reference another partition on the 136 possible to reference another partition on the same device using a
137 known partition UUID as the starting point. F 137 known partition UUID as the starting point. For example,
138 if partition 5 of the device has the UUID of 138 if partition 5 of the device has the UUID of
139 00112233-4455-6677-8899-AABBCCDDEEFF then part 139 00112233-4455-6677-8899-AABBCCDDEEFF then partition 3 may be found as
140 follows: 140 follows:
141 141
142 PARTUUID=00112233-4455-6677-8899-AABBCCDDEEF 142 PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF/PARTNROFF=-2
143 143
144 Authoritative information can be found in 144 Authoritative information can be found in
145 "Documentation/admin-guide/kernel-parameters.r 145 "Documentation/admin-guide/kernel-parameters.rst".
146 146
147 147
148 2.2) ro, rw 148 2.2) ro, rw
149 ----------- 149 -----------
150 150
151 :Syntax: ro 151 :Syntax: ro
152 :or: rw 152 :or: rw
153 153
154 These two options tell the kernel whether it s 154 These two options tell the kernel whether it should mount the root
155 filesystem read-only or read-write. The defaul 155 filesystem read-only or read-write. The default is read-only, except
156 for ramdisks, which default to read-write. 156 for ramdisks, which default to read-write.
157 157
158 158
159 2.3) debug 159 2.3) debug
160 ---------- 160 ----------
161 161
162 :Syntax: debug 162 :Syntax: debug
163 163
164 This raises the kernel log level to 10 (the de 164 This raises the kernel log level to 10 (the default is 7). This is the
165 same level as set by the "dmesg" command, just 165 same level as set by the "dmesg" command, just that the maximum level
166 selectable by dmesg is 8. 166 selectable by dmesg is 8.
167 167
168 168
169 2.4) debug= 169 2.4) debug=
170 ----------- 170 -----------
171 171
172 :Syntax: debug=<device> 172 :Syntax: debug=<device>
173 173
174 This option causes certain kernel messages be 174 This option causes certain kernel messages be printed to the selected
175 debugging device. This can aid debugging the k 175 debugging device. This can aid debugging the kernel, since the
176 messages can be captured and analyzed on some 176 messages can be captured and analyzed on some other machine. Which
177 devices are possible depends on the machine ty 177 devices are possible depends on the machine type. There are no checks
178 for the validity of the device name. If the de 178 for the validity of the device name. If the device isn't implemented,
179 nothing happens. 179 nothing happens.
180 180
181 Messages logged this way are in general stack 181 Messages logged this way are in general stack dumps after kernel
182 memory faults or bad kernel traps, and kernel 182 memory faults or bad kernel traps, and kernel panics. To be exact: all
183 messages of level 0 (panic messages) and all m 183 messages of level 0 (panic messages) and all messages printed while
184 the log level is 8 or more (their level doesn' 184 the log level is 8 or more (their level doesn't matter). Before stack
185 dumps, the kernel sets the log level to 10 aut 185 dumps, the kernel sets the log level to 10 automatically. A level of
186 at least 8 can also be set by the "debug" comm 186 at least 8 can also be set by the "debug" command line option (see
187 2.3) and at run time with "dmesg -n 8". 187 2.3) and at run time with "dmesg -n 8".
188 188
189 Devices possible for Amiga: 189 Devices possible for Amiga:
190 190
191 - "ser": 191 - "ser":
192 built-in serial port; parameters: 96 192 built-in serial port; parameters: 9600bps, 8N1
193 - "mem": 193 - "mem":
194 Save the messages to a reserved area 194 Save the messages to a reserved area in chip mem. After
195 rebooting, they can be read under Am 195 rebooting, they can be read under AmigaOS with the tool
196 'dmesg'. 196 'dmesg'.
197 197
198 Devices possible for Atari: 198 Devices possible for Atari:
199 199
200 - "ser1": 200 - "ser1":
201 ST-MFP serial port ("Modem1"); para 201 ST-MFP serial port ("Modem1"); parameters: 9600bps, 8N1
202 - "ser2": 202 - "ser2":
203 SCC channel B serial port ("Modem2" 203 SCC channel B serial port ("Modem2"); parameters: 9600bps, 8N1
204 - "ser" : 204 - "ser" :
205 default serial port 205 default serial port
206 This is "ser2" for a Falcon, and "s 206 This is "ser2" for a Falcon, and "ser1" for any other machine
207 - "midi": 207 - "midi":
208 The MIDI port; parameters: 31250bps 208 The MIDI port; parameters: 31250bps, 8N1
209 - "par" : 209 - "par" :
210 parallel port 210 parallel port
211 211
212 The printing routine for this imple 212 The printing routine for this implements a timeout for the
213 case there's no printer connected ( 213 case there's no printer connected (else the kernel would
214 lock up). The timeout is not exact, 214 lock up). The timeout is not exact, but usually a few
215 seconds. 215 seconds.
216 216
217 217
218 2.6) ramdisk_size= 218 2.6) ramdisk_size=
219 ------------------ 219 ------------------
220 220
221 :Syntax: ramdisk_size=<size> 221 :Syntax: ramdisk_size=<size>
222 222
223 This option instructs the kernel to set up a r 223 This option instructs the kernel to set up a ramdisk of the given
224 size in KBytes. Do not use this option if the 224 size in KBytes. Do not use this option if the ramdisk contents are
225 passed by bootstrap! In this case, the size is 225 passed by bootstrap! In this case, the size is selected automatically
226 and should not be overwritten. 226 and should not be overwritten.
227 227
228 The only application is for root filesystems o 228 The only application is for root filesystems on floppy disks, that
229 should be loaded into memory. To do that, sele 229 should be loaded into memory. To do that, select the corresponding
230 size of the disk as ramdisk size, and set the 230 size of the disk as ramdisk size, and set the root device to the disk
231 drive (with "root="). 231 drive (with "root=").
232 232
233 233
234 2.7) swap= 234 2.7) swap=
235 235
236 I can't find any sign of this option in 2.2. 236 I can't find any sign of this option in 2.2.6.
237 237
238 2.8) buff= 238 2.8) buff=
239 ----------- 239 -----------
240 240
241 I can't find any sign of this option in 2.2. 241 I can't find any sign of this option in 2.2.6.
242 242
243 243
244 3) General Device Options (Amiga and Atari) 244 3) General Device Options (Amiga and Atari)
245 =========================================== 245 ===========================================
246 246
247 3.1) ether= 247 3.1) ether=
248 ----------- 248 -----------
249 249
250 :Syntax: ether=[<irq>[,<base_addr>[,<mem_start 250 :Syntax: ether=[<irq>[,<base_addr>[,<mem_start>[,<mem_end>]]]],<dev-name>
251 251
252 <dev-name> is the name of a net driver, as spe 252 <dev-name> is the name of a net driver, as specified in
253 drivers/net/Space.c in the Linux source. Most 253 drivers/net/Space.c in the Linux source. Most prominent are eth0, ...
254 eth3, sl0, ... sl3, ppp0, ..., ppp3, dummy, an 254 eth3, sl0, ... sl3, ppp0, ..., ppp3, dummy, and lo.
255 255
256 The non-ethernet drivers (sl, ppp, dummy, lo) 256 The non-ethernet drivers (sl, ppp, dummy, lo) obviously ignore the
257 settings by this options. Also, the existing e 257 settings by this options. Also, the existing ethernet drivers for
258 Linux/m68k (ariadne, a2065, hydra) don't use t 258 Linux/m68k (ariadne, a2065, hydra) don't use them because Zorro boards
259 are really Plug-'n-Play, so the "ether=" optio 259 are really Plug-'n-Play, so the "ether=" option is useless altogether
260 for Linux/m68k. 260 for Linux/m68k.
261 261
262 262
263 3.2) hd= 263 3.2) hd=
264 -------- 264 --------
265 265
266 :Syntax: hd=<cylinders>,<heads>,<sectors> 266 :Syntax: hd=<cylinders>,<heads>,<sectors>
267 267
268 This option sets the disk geometry of an IDE d 268 This option sets the disk geometry of an IDE disk. The first hd=
269 option is for the first IDE disk, the second f 269 option is for the first IDE disk, the second for the second one.
270 (I.e., you can give this option twice.) In mos 270 (I.e., you can give this option twice.) In most cases, you won't have
271 to use this option, since the kernel can obtai 271 to use this option, since the kernel can obtain the geometry data
272 itself. It exists just for the case that this 272 itself. It exists just for the case that this fails for one of your
273 disks. 273 disks.
274 274
275 275
276 3.3) max_scsi_luns= 276 3.3) max_scsi_luns=
277 ------------------- 277 -------------------
278 278
279 :Syntax: max_scsi_luns=<n> 279 :Syntax: max_scsi_luns=<n>
280 280
281 Sets the maximum number of LUNs (logical units 281 Sets the maximum number of LUNs (logical units) of SCSI devices to
282 be scanned. Valid values for <n> are between 1 282 be scanned. Valid values for <n> are between 1 and 8. Default is 8 if
283 "Probe all LUNs on each SCSI device" was selec 283 "Probe all LUNs on each SCSI device" was selected during the kernel
284 configuration, else 1. 284 configuration, else 1.
285 285
286 286
287 3.4) st= 287 3.4) st=
288 -------- 288 --------
289 289
290 :Syntax: st=<buffer_size>,[<write_thres>,[<max 290 :Syntax: st=<buffer_size>,[<write_thres>,[<max_buffers>]]
291 291
292 Sets several parameters of the SCSI tape drive 292 Sets several parameters of the SCSI tape driver. <buffer_size> is
293 the number of 512-byte buffers reserved for ta 293 the number of 512-byte buffers reserved for tape operations for each
294 device. <write_thres> sets the number of block 294 device. <write_thres> sets the number of blocks which must be filled
295 to start an actual write operation to the tape 295 to start an actual write operation to the tape. Maximum value is the
296 total number of buffers. <max_buffer> limits t 296 total number of buffers. <max_buffer> limits the total number of
297 buffers allocated for all tape devices. 297 buffers allocated for all tape devices.
298 298
299 299
300 3.5) dmasound= 300 3.5) dmasound=
301 -------------- 301 --------------
302 302
303 :Syntax: dmasound=[<buffers>,<buffer-size>[,<c 303 :Syntax: dmasound=[<buffers>,<buffer-size>[,<catch-radius>]]
304 304
305 This option controls some configurations of th 305 This option controls some configurations of the Linux/m68k DMA sound
306 driver (Amiga and Atari): <buffers> is the num 306 driver (Amiga and Atari): <buffers> is the number of buffers you want
307 to use (minimum 4, default 4), <buffer-size> i 307 to use (minimum 4, default 4), <buffer-size> is the size of each
308 buffer in kilobytes (minimum 4, default 32) an 308 buffer in kilobytes (minimum 4, default 32) and <catch-radius> says
309 how much percent of error will be tolerated wh 309 how much percent of error will be tolerated when setting a frequency
310 (maximum 10, default 0). For example with 3% y 310 (maximum 10, default 0). For example with 3% you can play 8000Hz
311 AU-Files on the Falcon with its hardware frequ 311 AU-Files on the Falcon with its hardware frequency of 8195Hz and thus
312 don't need to expand the sound. 312 don't need to expand the sound.
313 313
314 314
315 315
316 4) Options for Atari Only 316 4) Options for Atari Only
317 ========================= 317 =========================
318 318
319 4.1) video= 319 4.1) video=
320 ----------- 320 -----------
321 321
322 :Syntax: video=<fbname>:<sub-options...> 322 :Syntax: video=<fbname>:<sub-options...>
323 323
324 The <fbname> parameter specifies the name of t 324 The <fbname> parameter specifies the name of the frame buffer,
325 eg. most atari users will want to specify `ata 325 eg. most atari users will want to specify `atafb` here. The
326 <sub-options> is a comma-separated list of the 326 <sub-options> is a comma-separated list of the sub-options listed
327 below. 327 below.
328 328
329 NB: 329 NB:
330 Please notice that this option was renamed 330 Please notice that this option was renamed from `atavideo` to
331 `video` during the development of the 1.3. 331 `video` during the development of the 1.3.x kernels, thus you
332 might need to update your boot-scripts if 332 might need to update your boot-scripts if upgrading to 2.x from
333 an 1.2.x kernel. 333 an 1.2.x kernel.
334 334
335 NBB: 335 NBB:
336 The behavior of video= was changed in 2.1. 336 The behavior of video= was changed in 2.1.57 so the recommended
337 option is to specify the name of the frame 337 option is to specify the name of the frame buffer.
338 338
339 4.1.1) Video Mode 339 4.1.1) Video Mode
340 ----------------- 340 -----------------
341 341
342 This sub-option may be any of the predefined v 342 This sub-option may be any of the predefined video modes, as listed
343 in atari/atafb.c in the Linux/m68k source tree 343 in atari/atafb.c in the Linux/m68k source tree. The kernel will
344 activate the given video mode at boot time and 344 activate the given video mode at boot time and make it the default
345 mode, if the hardware allows. Currently define 345 mode, if the hardware allows. Currently defined names are:
346 346
347 - stlow : 320x200x4 347 - stlow : 320x200x4
348 - stmid, default5 : 640x200x2 348 - stmid, default5 : 640x200x2
349 - sthigh, default4: 640x400x1 349 - sthigh, default4: 640x400x1
350 - ttlow : 320x480x8, TT only 350 - ttlow : 320x480x8, TT only
351 - ttmid, default1 : 640x480x4, TT only 351 - ttmid, default1 : 640x480x4, TT only
352 - tthigh, default2: 1280x960x1, TT only 352 - tthigh, default2: 1280x960x1, TT only
353 - vga2 : 640x480x1, Falcon only 353 - vga2 : 640x480x1, Falcon only
354 - vga4 : 640x480x2, Falcon only 354 - vga4 : 640x480x2, Falcon only
355 - vga16, default3 : 640x480x4, Falcon only 355 - vga16, default3 : 640x480x4, Falcon only
356 - vga256 : 640x480x8, Falcon only 356 - vga256 : 640x480x8, Falcon only
357 - falh2 : 896x608x1, Falcon only 357 - falh2 : 896x608x1, Falcon only
358 - falh16 : 896x608x4, Falcon only 358 - falh16 : 896x608x4, Falcon only
359 359
360 If no video mode is given on the command line, 360 If no video mode is given on the command line, the kernel tries the
361 modes names "default<n>" in turn, until one is 361 modes names "default<n>" in turn, until one is possible with the
362 hardware in use. 362 hardware in use.
363 363
364 A video mode setting doesn't make sense, if th 364 A video mode setting doesn't make sense, if the external driver is
365 activated by a "external:" sub-option. 365 activated by a "external:" sub-option.
366 366
367 4.1.2) inverse 367 4.1.2) inverse
368 -------------- 368 --------------
369 369
370 Invert the display. This affects only text con 370 Invert the display. This affects only text consoles.
371 Usually, the background is chosen to be black. 371 Usually, the background is chosen to be black. With this
372 option, you can make the background white. 372 option, you can make the background white.
373 373
374 4.1.3) font 374 4.1.3) font
375 ----------- 375 -----------
376 376
377 :Syntax: font:<fontname> 377 :Syntax: font:<fontname>
378 378
379 Specify the font to use in text modes. Current 379 Specify the font to use in text modes. Currently you can choose only
380 between `VGA8x8`, `VGA8x16` and `PEARL8x8`. `V 380 between `VGA8x8`, `VGA8x16` and `PEARL8x8`. `VGA8x8` is default, if the
381 vertical size of the display is less than 400 381 vertical size of the display is less than 400 pixel rows. Otherwise, the
382 `VGA8x16` font is the default. 382 `VGA8x16` font is the default.
383 383
384 4.1.4) `hwscroll_` 384 4.1.4) `hwscroll_`
385 ------------------ 385 ------------------
386 386
387 :Syntax: `hwscroll_<n>` 387 :Syntax: `hwscroll_<n>`
388 388
389 The number of additional lines of video memory 389 The number of additional lines of video memory to reserve for
390 speeding up the scrolling ("hardware scrolling 390 speeding up the scrolling ("hardware scrolling"). Hardware scrolling
391 is possible only if the kernel can set the vid 391 is possible only if the kernel can set the video base address in steps
392 fine enough. This is true for STE, MegaSTE, TT 392 fine enough. This is true for STE, MegaSTE, TT, and Falcon. It is not
393 possible with plain STs and graphics cards (Th 393 possible with plain STs and graphics cards (The former because the
394 base address must be on a 256 byte boundary th 394 base address must be on a 256 byte boundary there, the latter because
395 the kernel doesn't know how to set the base ad 395 the kernel doesn't know how to set the base address at all.)
396 396
397 By default, <n> is set to the number of visibl 397 By default, <n> is set to the number of visible text lines on the
398 display. Thus, the amount of video memory is d 398 display. Thus, the amount of video memory is doubled, compared to no
399 hardware scrolling. You can turn off the hardw 399 hardware scrolling. You can turn off the hardware scrolling altogether
400 by setting <n> to 0. 400 by setting <n> to 0.
401 401
402 4.1.5) internal: 402 4.1.5) internal:
403 ---------------- 403 ----------------
404 404
405 :Syntax: internal:<xres>;<yres>[;<xres_max>;<y 405 :Syntax: internal:<xres>;<yres>[;<xres_max>;<yres_max>;<offset>]
406 406
407 This option specifies the capabilities of some 407 This option specifies the capabilities of some extended internal video
408 hardware, like e.g. OverScan. <xres> and <yres 408 hardware, like e.g. OverScan. <xres> and <yres> give the (extended)
409 dimensions of the screen. 409 dimensions of the screen.
410 410
411 If your OverScan needs a black border, you hav 411 If your OverScan needs a black border, you have to write the last
412 three arguments of the "internal:". <xres_max> 412 three arguments of the "internal:". <xres_max> is the maximum line
413 length the hardware allows, <yres_max> the max 413 length the hardware allows, <yres_max> the maximum number of lines.
414 <offset> is the offset of the visible part of 414 <offset> is the offset of the visible part of the screen memory to its
415 physical start, in bytes. 415 physical start, in bytes.
416 416
417 Often, extended interval video hardware has to 417 Often, extended interval video hardware has to be activated somehow.
418 For this, see the "sw_*" options below. 418 For this, see the "sw_*" options below.
419 419
420 4.1.6) external: 420 4.1.6) external:
421 ---------------- 421 ----------------
422 422
423 :Syntax: 423 :Syntax:
424 external:<xres>;<yres>;<depth>;<org>;<scrmem 424 external:<xres>;<yres>;<depth>;<org>;<scrmem>[;<scrlen>[;<vgabase>
425 [;<colw>[;<coltype>[;<xres_virtual>]]]]] 425 [;<colw>[;<coltype>[;<xres_virtual>]]]]]
426 426
427 .. I had to break this line... 427 .. I had to break this line...
428 428
429 This is probably the most complicated paramete 429 This is probably the most complicated parameter... It specifies that
430 you have some external video hardware (a graph 430 you have some external video hardware (a graphics board), and how to
431 use it under Linux/m68k. The kernel cannot kno 431 use it under Linux/m68k. The kernel cannot know more about the hardware
432 than you tell it here! The kernel also is unab 432 than you tell it here! The kernel also is unable to set or change any
433 video modes, since it doesn't know about any b 433 video modes, since it doesn't know about any board internal. So, you
434 have to switch to that video mode before you s 434 have to switch to that video mode before you start Linux, and cannot
435 switch to another mode once Linux has started. 435 switch to another mode once Linux has started.
436 436
437 The first 3 parameters of this sub-option shou 437 The first 3 parameters of this sub-option should be obvious: <xres>,
438 <yres> and <depth> give the dimensions of the 438 <yres> and <depth> give the dimensions of the screen and the number of
439 planes (depth). The depth is the logarithm to 439 planes (depth). The depth is the logarithm to base 2 of the number
440 of colors possible. (Or, the other way round: 440 of colors possible. (Or, the other way round: The number of colors is
441 2^depth). 441 2^depth).
442 442
443 You have to tell the kernel furthermore how th 443 You have to tell the kernel furthermore how the video memory is
444 organized. This is done by a letter as <org> p 444 organized. This is done by a letter as <org> parameter:
445 445
446 'n': 446 'n':
447 "normal planes", i.e. one whole plane af 447 "normal planes", i.e. one whole plane after another
448 'i': 448 'i':
449 "interleaved planes", i.e. 16 bit of the 449 "interleaved planes", i.e. 16 bit of the first plane, than 16 bit
450 of the next, and so on... This mode is u 450 of the next, and so on... This mode is used only with the
451 built-in Atari video modes, I think ther 451 built-in Atari video modes, I think there is no card that
452 supports this mode. 452 supports this mode.
453 'p': 453 'p':
454 "packed pixels", i.e. <depth> consecutiv 454 "packed pixels", i.e. <depth> consecutive bits stand for all
455 planes of one pixel; this is the most co 455 planes of one pixel; this is the most common mode for 8 planes
456 (256 colors) on graphic cards 456 (256 colors) on graphic cards
457 't': 457 't':
458 "true color" (more or less packed pixels 458 "true color" (more or less packed pixels, but without a color
459 lookup table); usually depth is 24 459 lookup table); usually depth is 24
460 460
461 For monochrome modes (i.e., <depth> is 1), the 461 For monochrome modes (i.e., <depth> is 1), the <org> letter has a
462 different meaning: 462 different meaning:
463 463
464 'n': 464 'n':
465 normal colors, i.e. 0=white, 1=black 465 normal colors, i.e. 0=white, 1=black
466 'i': 466 'i':
467 inverted colors, i.e. 0=black, 1=white 467 inverted colors, i.e. 0=black, 1=white
468 468
469 The next important information about the video 469 The next important information about the video hardware is the base
470 address of the video memory. That is given in 470 address of the video memory. That is given in the <scrmem> parameter,
471 as a hexadecimal number with a "0x" prefix. Yo 471 as a hexadecimal number with a "0x" prefix. You have to find out this
472 address in the documentation of your hardware. 472 address in the documentation of your hardware.
473 473
474 The next parameter, <scrlen>, tells the kernel 474 The next parameter, <scrlen>, tells the kernel about the size of the
475 video memory. If it's missing, the size is cal 475 video memory. If it's missing, the size is calculated from <xres>,
476 <yres>, and <depth>. For now, it is not useful 476 <yres>, and <depth>. For now, it is not useful to write a value here.
477 It would be used only for hardware scrolling ( 477 It would be used only for hardware scrolling (which isn't possible
478 with the external driver, because the kernel c 478 with the external driver, because the kernel cannot set the video base
479 address), or for virtual resolutions under X ( 479 address), or for virtual resolutions under X (which the X server
480 doesn't support yet). So, it's currently best 480 doesn't support yet). So, it's currently best to leave this field
481 empty, either by ending the "external:" after 481 empty, either by ending the "external:" after the video address or by
482 writing two consecutive semicolons, if you wan 482 writing two consecutive semicolons, if you want to give a <vgabase>
483 (it is allowed to leave this parameter empty). 483 (it is allowed to leave this parameter empty).
484 484
485 The <vgabase> parameter is optional. If it is 485 The <vgabase> parameter is optional. If it is not given, the kernel
486 cannot read or write any color registers of th 486 cannot read or write any color registers of the video hardware, and
487 thus you have to set appropriate colors before 487 thus you have to set appropriate colors before you start Linux. But if
488 your card is somehow VGA compatible, you can t 488 your card is somehow VGA compatible, you can tell the kernel the base
489 address of the VGA register set, so it can cha 489 address of the VGA register set, so it can change the color lookup
490 table. You have to look up this address in you 490 table. You have to look up this address in your board's documentation.
491 To avoid misunderstandings: <vgabase> is the _ 491 To avoid misunderstandings: <vgabase> is the _base_ address, i.e. a 4k
492 aligned address. For read/writing the color re 492 aligned address. For read/writing the color registers, the kernel
493 uses the addresses vgabase+0x3c7...vgabase+0x3 493 uses the addresses vgabase+0x3c7...vgabase+0x3c9. The <vgabase>
494 parameter is written in hexadecimal with a "0x 494 parameter is written in hexadecimal with a "0x" prefix, just as
495 <scrmem>. 495 <scrmem>.
496 496
497 <colw> is meaningful only if <vgabase> is spec 497 <colw> is meaningful only if <vgabase> is specified. It tells the
498 kernel how wide each of the color register is, 498 kernel how wide each of the color register is, i.e. the number of bits
499 per single color (red/green/blue). Default is 499 per single color (red/green/blue). Default is 6, another quite usual
500 value is 8. 500 value is 8.
501 501
502 Also <coltype> is used together with <vgabase> 502 Also <coltype> is used together with <vgabase>. It tells the kernel
503 about the color register model of your gfx boa 503 about the color register model of your gfx board. Currently, the types
504 "vga" (which is also the default) and "mv300" 504 "vga" (which is also the default) and "mv300" (SANG MV300) are
505 implemented. 505 implemented.
506 506
507 Parameter <xres_virtual> is required for ProMS 507 Parameter <xres_virtual> is required for ProMST or ET4000 cards where
508 the physical linelength differs from the visib 508 the physical linelength differs from the visible length. With ProMST,
509 xres_virtual must be set to 2048. For ET4000, 509 xres_virtual must be set to 2048. For ET4000, xres_virtual depends on the
510 initialisation of the video-card. 510 initialisation of the video-card.
511 If you're missing a corresponding yres_virtual 511 If you're missing a corresponding yres_virtual: the external part is legacy,
512 therefore we don't support hardware-dependent 512 therefore we don't support hardware-dependent functions like hardware-scroll,
513 panning or blanking. 513 panning or blanking.
514 514
515 4.1.7) eclock: 515 4.1.7) eclock:
516 -------------- 516 --------------
517 517
518 The external pixel clock attached to the Falco 518 The external pixel clock attached to the Falcon VIDEL shifter. This
519 currently works only with the ScreenWonder! 519 currently works only with the ScreenWonder!
520 520
521 4.1.8) monitorcap: 521 4.1.8) monitorcap:
522 ------------------- 522 -------------------
523 523
524 :Syntax: monitorcap:<vmin>;<vmax>;<hmin>;<hmax 524 :Syntax: monitorcap:<vmin>;<vmax>;<hmin>;<hmax>
525 525
526 This describes the capabilities of a multisync 526 This describes the capabilities of a multisync monitor. Don't use it
527 with a fixed-frequency monitor! For now, only 527 with a fixed-frequency monitor! For now, only the Falcon frame buffer
528 uses the settings of "monitorcap:". 528 uses the settings of "monitorcap:".
529 529
530 <vmin> and <vmax> are the minimum and maximum, 530 <vmin> and <vmax> are the minimum and maximum, resp., vertical frequencies
531 your monitor can work with, in Hz. <hmin> and 531 your monitor can work with, in Hz. <hmin> and <hmax> are the same for
532 the horizontal frequency, in kHz. 532 the horizontal frequency, in kHz.
533 533
534 The defaults are 58;62;31;32 (VGA compatible 534 The defaults are 58;62;31;32 (VGA compatible).
535 535
536 The defaults for TV/SC1224/SC1435 cover both 536 The defaults for TV/SC1224/SC1435 cover both PAL and NTSC standards.
537 537
538 4.1.9) keep 538 4.1.9) keep
539 ------------ 539 ------------
540 540
541 If this option is given, the framebuffer devic 541 If this option is given, the framebuffer device doesn't do any video
542 mode calculations and settings on its own. The 542 mode calculations and settings on its own. The only Atari fb device
543 that does this currently is the Falcon. 543 that does this currently is the Falcon.
544 544
545 What you reach with this: Settings for unknown 545 What you reach with this: Settings for unknown video extensions
546 aren't overridden by the driver, so you can st 546 aren't overridden by the driver, so you can still use the mode found
547 when booting, when the driver doesn't know to 547 when booting, when the driver doesn't know to set this mode itself.
548 But this also means, that you can't switch vid 548 But this also means, that you can't switch video modes anymore...
549 549
550 An example where you may want to use "keep" is 550 An example where you may want to use "keep" is the ScreenBlaster for
551 the Falcon. 551 the Falcon.
552 552
553 553
554 4.2) atamouse= 554 4.2) atamouse=
555 -------------- 555 --------------
556 556
557 :Syntax: atamouse=<x-threshold>,[<y-threshold> 557 :Syntax: atamouse=<x-threshold>,[<y-threshold>]
558 558
559 With this option, you can set the mouse moveme 559 With this option, you can set the mouse movement reporting threshold.
560 This is the number of pixels of mouse movement 560 This is the number of pixels of mouse movement that have to accumulate
561 before the IKBD sends a new mouse packet to th 561 before the IKBD sends a new mouse packet to the kernel. Higher values
562 reduce the mouse interrupt load and thus reduc 562 reduce the mouse interrupt load and thus reduce the chance of keyboard
563 overruns. Lower values give a slightly faster 563 overruns. Lower values give a slightly faster mouse responses and
564 slightly better mouse tracking. 564 slightly better mouse tracking.
565 565
566 You can set the threshold in x and y separatel 566 You can set the threshold in x and y separately, but usually this is
567 of little practical use. If there's just one n 567 of little practical use. If there's just one number in the option, it
568 is used for both dimensions. The default value 568 is used for both dimensions. The default value is 2 for both
569 thresholds. 569 thresholds.
570 570
571 571
572 4.3) ataflop= 572 4.3) ataflop=
573 ------------- 573 -------------
574 574
575 :Syntax: ataflop=<drive type>[,<trackbuffering 575 :Syntax: ataflop=<drive type>[,<trackbuffering>[,<steprateA>[,<steprateB>]]]
576 576
577 The drive type may be 0, 1, or 2, for DD, H 577 The drive type may be 0, 1, or 2, for DD, HD, and ED, resp. This
578 setting affects how many buffers are reserv 578 setting affects how many buffers are reserved and which formats are
579 probed (see also below). The default is 1 ( 579 probed (see also below). The default is 1 (HD). Only one drive type
580 can be selected. If you have two disk drive 580 can be selected. If you have two disk drives, select the "better"
581 type. 581 type.
582 582
583 The second parameter <trackbuffer> tells th 583 The second parameter <trackbuffer> tells the kernel whether to use
584 track buffering (1) or not (0). The default 584 track buffering (1) or not (0). The default is machine-dependent:
585 no for the Medusa and yes for all others. 585 no for the Medusa and yes for all others.
586 586
587 With the two following parameters, you can 587 With the two following parameters, you can change the default
588 steprate used for drive A and B, resp. 588 steprate used for drive A and B, resp.
589 589
590 590
591 4.4) atascsi= 591 4.4) atascsi=
592 ------------- 592 -------------
593 593
594 :Syntax: atascsi=<can_queue>[,<cmd_per_lun>[,< 594 :Syntax: atascsi=<can_queue>[,<cmd_per_lun>[,<scat-gat>[,<host-id>[,<tagged>]]]]
595 595
596 This option sets some parameters for the Atari 596 This option sets some parameters for the Atari native SCSI driver.
597 Generally, any number of arguments can be omit 597 Generally, any number of arguments can be omitted from the end. And
598 for each of the numbers, a negative value mean 598 for each of the numbers, a negative value means "use default". The
599 defaults depend on whether TT-style or Falcon- 599 defaults depend on whether TT-style or Falcon-style SCSI is used.
600 Below, defaults are noted as n/m, where the fi 600 Below, defaults are noted as n/m, where the first value refers to
601 TT-SCSI and the latter to Falcon-SCSI. If an i 601 TT-SCSI and the latter to Falcon-SCSI. If an illegal value is given
602 for one parameter, an error message is printed 602 for one parameter, an error message is printed and that one setting is
603 ignored (others aren't affected). 603 ignored (others aren't affected).
604 604
605 <can_queue>: 605 <can_queue>:
606 This is the maximum number of SCSI command 606 This is the maximum number of SCSI commands queued internally to the
607 Atari SCSI driver. A value of 1 effectivel 607 Atari SCSI driver. A value of 1 effectively turns off the driver
608 internal multitasking (if it causes proble 608 internal multitasking (if it causes problems). Legal values are >=
609 1. <can_queue> can be as high as you like, 609 1. <can_queue> can be as high as you like, but values greater than
610 <cmd_per_lun> times the number of SCSI tar 610 <cmd_per_lun> times the number of SCSI targets (LUNs) you have
611 don't make sense. Default: 16/8. 611 don't make sense. Default: 16/8.
612 612
613 <cmd_per_lun>: 613 <cmd_per_lun>:
614 Maximum number of SCSI commands issued to 614 Maximum number of SCSI commands issued to the driver for one
615 logical unit (LUN, usually one SCSI target 615 logical unit (LUN, usually one SCSI target). Legal values start
616 from 1. If tagged queuing (see below) is n 616 from 1. If tagged queuing (see below) is not used, values greater
617 than 2 don't make sense, but waste memory. 617 than 2 don't make sense, but waste memory. Otherwise, the maximum
618 is the number of command tags available to 618 is the number of command tags available to the driver (currently
619 32). Default: 8/1. (Note: Values > 1 seem 619 32). Default: 8/1. (Note: Values > 1 seem to cause problems on a
620 Falcon, cause not yet known.) 620 Falcon, cause not yet known.)
621 621
622 The <cmd_per_lun> value at a great part de 622 The <cmd_per_lun> value at a great part determines the amount of
623 memory SCSI reserves for itself. The formu 623 memory SCSI reserves for itself. The formula is rather
624 complicated, but I can give you some hints 624 complicated, but I can give you some hints:
625 625
626 no scatter-gather: 626 no scatter-gather:
627 cmd_per_lun * 232 bytes 627 cmd_per_lun * 232 bytes
628 full scatter-gather: 628 full scatter-gather:
629 cmd_per_lun * approx. 17 Kbytes 629 cmd_per_lun * approx. 17 Kbytes
630 630
631 <scat-gat>: 631 <scat-gat>:
632 Size of the scatter-gather table, i.e. the 632 Size of the scatter-gather table, i.e. the number of requests
633 consecutive on the disk that can be merged 633 consecutive on the disk that can be merged into one SCSI command.
634 Legal values are between 0 and 255. Defaul 634 Legal values are between 0 and 255. Default: 255/0. Note: This
635 value is forced to 0 on a Falcon, since sc 635 value is forced to 0 on a Falcon, since scatter-gather isn't
636 possible with the ST-DMA. Not using scatte 636 possible with the ST-DMA. Not using scatter-gather hurts
637 performance significantly. 637 performance significantly.
638 638
639 <host-id>: 639 <host-id>:
640 The SCSI ID to be used by the initiator (y 640 The SCSI ID to be used by the initiator (your Atari). This is
641 usually 7, the highest possible ID. Every 641 usually 7, the highest possible ID. Every ID on the SCSI bus must
642 be unique. Default: determined at run time 642 be unique. Default: determined at run time: If the NV-RAM checksum
643 is valid, and bit 7 in byte 30 of the NV-R 643 is valid, and bit 7 in byte 30 of the NV-RAM is set, the lower 3
644 bits of this byte are used as the host ID. 644 bits of this byte are used as the host ID. (This method is defined
645 by Atari and also used by some TOS HD driv 645 by Atari and also used by some TOS HD drivers.) If the above
646 isn't given, the default ID is 7. (both, T 646 isn't given, the default ID is 7. (both, TT and Falcon).
647 647
648 <tagged>: 648 <tagged>:
649 0 means turn off tagged queuing support, a 649 0 means turn off tagged queuing support, all other values > 0 mean
650 use tagged queuing for targets that suppor 650 use tagged queuing for targets that support it. Default: currently
651 off, but this may change when tagged queui 651 off, but this may change when tagged queuing handling has been
652 proved to be reliable. 652 proved to be reliable.
653 653
654 Tagged queuing means that more than one co 654 Tagged queuing means that more than one command can be issued to
655 one LUN, and the SCSI device itself orders 655 one LUN, and the SCSI device itself orders the requests so they
656 can be performed in optimal order. Not all 656 can be performed in optimal order. Not all SCSI devices support
657 tagged queuing (:-(). 657 tagged queuing (:-().
658 658
659 4.5 switches= 659 4.5 switches=
660 ------------- 660 -------------
661 661
662 :Syntax: switches=<list of switches> 662 :Syntax: switches=<list of switches>
663 663
664 With this option you can switch some hardware 664 With this option you can switch some hardware lines that are often
665 used to enable/disable certain hardware extens 665 used to enable/disable certain hardware extensions. Examples are
666 OverScan, overclocking, ... 666 OverScan, overclocking, ...
667 667
668 The <list of switches> is a comma-separated li 668 The <list of switches> is a comma-separated list of the following
669 items: 669 items:
670 670
671 ikbd: 671 ikbd:
672 set RTS of the keyboard ACIA high 672 set RTS of the keyboard ACIA high
673 midi: 673 midi:
674 set RTS of the MIDI ACIA high 674 set RTS of the MIDI ACIA high
675 snd6: 675 snd6:
676 set bit 6 of the PSG port A 676 set bit 6 of the PSG port A
677 snd7: 677 snd7:
678 set bit 6 of the PSG port A 678 set bit 6 of the PSG port A
679 679
680 It doesn't make sense to mention a switch more 680 It doesn't make sense to mention a switch more than once (no
681 difference to only once), but you can give as 681 difference to only once), but you can give as many switches as you
682 want to enable different features. The switch 682 want to enable different features. The switch lines are set as early
683 as possible during kernel initialization (even 683 as possible during kernel initialization (even before determining the
684 present hardware.) 684 present hardware.)
685 685
686 All of the items can also be prefixed with `ov 686 All of the items can also be prefixed with `ov_`, i.e. `ov_ikbd`,
687 `ov_midi`, ... These options are meant for swi 687 `ov_midi`, ... These options are meant for switching on an OverScan
688 video extension. The difference to the bare op 688 video extension. The difference to the bare option is that the
689 switch-on is done after video initialization, 689 switch-on is done after video initialization, and somehow synchronized
690 to the HBLANK. A speciality is that ov_ikbd an 690 to the HBLANK. A speciality is that ov_ikbd and ov_midi are switched
691 off before rebooting, so that OverScan is disa 691 off before rebooting, so that OverScan is disabled and TOS boots
692 correctly. 692 correctly.
693 693
694 If you give an option both, with and without t 694 If you give an option both, with and without the `ov_` prefix, the
695 earlier initialization (`ov_`-less) takes prec 695 earlier initialization (`ov_`-less) takes precedence. But the
696 switching-off on reset still happens in this c 696 switching-off on reset still happens in this case.
697 697
698 5) Options for Amiga Only: 698 5) Options for Amiga Only:
699 ========================== 699 ==========================
700 700
701 5.1) video= 701 5.1) video=
702 ----------- 702 -----------
703 703
704 :Syntax: video=<fbname>:<sub-options...> 704 :Syntax: video=<fbname>:<sub-options...>
705 705
706 The <fbname> parameter specifies the name of t 706 The <fbname> parameter specifies the name of the frame buffer, valid
707 options are `amifb`, `cyber`, 'virge', `retz3` 707 options are `amifb`, `cyber`, 'virge', `retz3` and `clgen`, provided
708 that the respective frame buffer devices have 708 that the respective frame buffer devices have been compiled into the
709 kernel (or compiled as loadable modules). The 709 kernel (or compiled as loadable modules). The behavior of the <fbname>
710 option was changed in 2.1.57 so it is now reco 710 option was changed in 2.1.57 so it is now recommended to specify this
711 option. 711 option.
712 712
713 The <sub-options> is a comma-separated list of 713 The <sub-options> is a comma-separated list of the sub-options listed
714 below. This option is organized similar to the 714 below. This option is organized similar to the Atari version of the
715 "video"-option (4.1), but knows fewer sub-opti 715 "video"-option (4.1), but knows fewer sub-options.
716 716
717 5.1.1) video mode 717 5.1.1) video mode
718 ----------------- 718 -----------------
719 719
720 Again, similar to the video mode for the Atari 720 Again, similar to the video mode for the Atari (see 4.1.1). Predefined
721 modes depend on the used frame buffer device. 721 modes depend on the used frame buffer device.
722 722
723 OCS, ECS and AGA machines all use the color fr 723 OCS, ECS and AGA machines all use the color frame buffer. The following
724 predefined video modes are available: 724 predefined video modes are available:
725 725
726 NTSC modes: 726 NTSC modes:
727 - ntsc : 640x200, 15 kHz, 60 Hz 727 - ntsc : 640x200, 15 kHz, 60 Hz
728 - ntsc-lace : 640x400, 15 kHz, 60 Hz in 728 - ntsc-lace : 640x400, 15 kHz, 60 Hz interlaced
729 729
730 PAL modes: 730 PAL modes:
731 - pal : 640x256, 15 kHz, 50 Hz 731 - pal : 640x256, 15 kHz, 50 Hz
732 - pal-lace : 640x512, 15 kHz, 50 Hz in 732 - pal-lace : 640x512, 15 kHz, 50 Hz interlaced
733 733
734 ECS modes: 734 ECS modes:
735 - multiscan : 640x480, 29 kHz, 57 Hz 735 - multiscan : 640x480, 29 kHz, 57 Hz
736 - multiscan-lace : 640x960, 29 kHz, 57 Hz in 736 - multiscan-lace : 640x960, 29 kHz, 57 Hz interlaced
737 - euro36 : 640x200, 15 kHz, 72 Hz 737 - euro36 : 640x200, 15 kHz, 72 Hz
738 - euro36-lace : 640x400, 15 kHz, 72 Hz in 738 - euro36-lace : 640x400, 15 kHz, 72 Hz interlaced
739 - euro72 : 640x400, 29 kHz, 68 Hz 739 - euro72 : 640x400, 29 kHz, 68 Hz
740 - euro72-lace : 640x800, 29 kHz, 68 Hz in 740 - euro72-lace : 640x800, 29 kHz, 68 Hz interlaced
741 - super72 : 800x300, 23 kHz, 70 Hz 741 - super72 : 800x300, 23 kHz, 70 Hz
742 - super72-lace : 800x600, 23 kHz, 70 Hz in 742 - super72-lace : 800x600, 23 kHz, 70 Hz interlaced
743 - dblntsc-ff : 640x400, 27 kHz, 57 Hz 743 - dblntsc-ff : 640x400, 27 kHz, 57 Hz
744 - dblntsc-lace : 640x800, 27 kHz, 57 Hz in 744 - dblntsc-lace : 640x800, 27 kHz, 57 Hz interlaced
745 - dblpal-ff : 640x512, 27 kHz, 47 Hz 745 - dblpal-ff : 640x512, 27 kHz, 47 Hz
746 - dblpal-lace : 640x1024, 27 kHz, 47 Hz i 746 - dblpal-lace : 640x1024, 27 kHz, 47 Hz interlaced
747 - dblntsc : 640x200, 27 kHz, 57 Hz do 747 - dblntsc : 640x200, 27 kHz, 57 Hz doublescan
748 - dblpal : 640x256, 27 kHz, 47 Hz do 748 - dblpal : 640x256, 27 kHz, 47 Hz doublescan
749 749
750 VGA modes: 750 VGA modes:
751 - vga : 640x480, 31 kHz, 60 Hz 751 - vga : 640x480, 31 kHz, 60 Hz
752 - vga70 : 640x400, 31 kHz, 70 Hz 752 - vga70 : 640x400, 31 kHz, 70 Hz
753 753
754 Please notice that the ECS and VGA modes requi 754 Please notice that the ECS and VGA modes require either an ECS or AGA
755 chipset, and that these modes are limited to 2 755 chipset, and that these modes are limited to 2-bit color for the ECS
756 chipset and 8-bit color for the AGA chipset. 756 chipset and 8-bit color for the AGA chipset.
757 757
758 5.1.2) depth 758 5.1.2) depth
759 ------------ 759 ------------
760 760
761 :Syntax: depth:<nr. of bit-planes> 761 :Syntax: depth:<nr. of bit-planes>
762 762
763 Specify the number of bit-planes for the selec 763 Specify the number of bit-planes for the selected video-mode.
764 764
765 5.1.3) inverse 765 5.1.3) inverse
766 -------------- 766 --------------
767 767
768 Use inverted display (black on white). Functio 768 Use inverted display (black on white). Functionally the same as the
769 "inverse" sub-option for the Atari. 769 "inverse" sub-option for the Atari.
770 770
771 5.1.4) font 771 5.1.4) font
772 ----------- 772 -----------
773 773
774 :Syntax: font:<fontname> 774 :Syntax: font:<fontname>
775 775
776 Specify the font to use in text modes. Functio 776 Specify the font to use in text modes. Functionally the same as the
777 "font" sub-option for the Atari, except that ` 777 "font" sub-option for the Atari, except that `PEARL8x8` is used instead
778 of `VGA8x8` if the vertical size of the displa 778 of `VGA8x8` if the vertical size of the display is less than 400 pixel
779 rows. 779 rows.
780 780
781 5.1.5) monitorcap: 781 5.1.5) monitorcap:
782 ------------------- 782 -------------------
783 783
784 :Syntax: monitorcap:<vmin>;<vmax>;<hmin>;<hmax 784 :Syntax: monitorcap:<vmin>;<vmax>;<hmin>;<hmax>
785 785
786 This describes the capabilities of a multisync 786 This describes the capabilities of a multisync monitor. For now, only
787 the color frame buffer uses the settings of "m 787 the color frame buffer uses the settings of "monitorcap:".
788 788
789 <vmin> and <vmax> are the minimum and maximum, 789 <vmin> and <vmax> are the minimum and maximum, resp., vertical frequencies
790 your monitor can work with, in Hz. <hmin> and 790 your monitor can work with, in Hz. <hmin> and <hmax> are the same for
791 the horizontal frequency, in kHz. 791 the horizontal frequency, in kHz.
792 792
793 The defaults are 50;90;15;38 (Generic Amiga mu 793 The defaults are 50;90;15;38 (Generic Amiga multisync monitor).
794 794
795 795
796 5.2) fd_def_df0= 796 5.2) fd_def_df0=
797 ---------------- 797 ----------------
798 798
799 :Syntax: fd_def_df0=<value> 799 :Syntax: fd_def_df0=<value>
800 800
801 Sets the df0 value for "silent" floppy drives. 801 Sets the df0 value for "silent" floppy drives. The value should be in
802 hexadecimal with "0x" prefix. 802 hexadecimal with "0x" prefix.
803 803
804 804
805 5.3) wd33c93= 805 5.3) wd33c93=
806 ------------- 806 -------------
807 807
808 :Syntax: wd33c93=<sub-options...> 808 :Syntax: wd33c93=<sub-options...>
809 809
810 These options affect the A590/A2091, A3000 and 810 These options affect the A590/A2091, A3000 and GVP Series II SCSI
811 controllers. 811 controllers.
812 812
813 The <sub-options> is a comma-separated list of 813 The <sub-options> is a comma-separated list of the sub-options listed
814 below. 814 below.
815 815
816 5.3.1) nosync 816 5.3.1) nosync
817 ------------- 817 -------------
818 818
819 :Syntax: nosync:bitmask 819 :Syntax: nosync:bitmask
820 820
821 bitmask is a byte where the 1st 7 bits corresp 821 bitmask is a byte where the 1st 7 bits correspond with the 7
822 possible SCSI devices. Set a bit to prevent sy 822 possible SCSI devices. Set a bit to prevent sync negotiation on that
823 device. To maintain backwards compatibility, a 823 device. To maintain backwards compatibility, a command-line such as
824 "wd33c93=255" will be automatically translated 824 "wd33c93=255" will be automatically translated to
825 "wd33c93=nosync:0xff". The default is to disab 825 "wd33c93=nosync:0xff". The default is to disable sync negotiation for
826 all devices, eg. nosync:0xff. 826 all devices, eg. nosync:0xff.
827 827
828 5.3.2) period 828 5.3.2) period
829 ------------- 829 -------------
830 830
831 :Syntax: period:ns 831 :Syntax: period:ns
832 832
833 `ns` is the minimum # of nanoseconds in a SCSI 833 `ns` is the minimum # of nanoseconds in a SCSI data transfer
834 period. Default is 500; acceptable values are 834 period. Default is 500; acceptable values are 250 - 1000.
835 835
836 5.3.3) disconnect 836 5.3.3) disconnect
837 ----------------- 837 -----------------
838 838
839 :Syntax: disconnect:x 839 :Syntax: disconnect:x
840 840
841 Specify x = 0 to never allow disconnects, 2 to 841 Specify x = 0 to never allow disconnects, 2 to always allow them.
842 x = 1 does 'adaptive' disconnects, which is th 842 x = 1 does 'adaptive' disconnects, which is the default and generally
843 the best choice. 843 the best choice.
844 844
845 5.3.4) debug 845 5.3.4) debug
846 ------------ 846 ------------
847 847
848 :Syntax: debug:x 848 :Syntax: debug:x
849 849
850 If `DEBUGGING_ON` is defined, x is a bit mask 850 If `DEBUGGING_ON` is defined, x is a bit mask that causes various
851 types of debug output to printed - see the DB_ 851 types of debug output to printed - see the DB_xxx defines in
852 wd33c93.h. 852 wd33c93.h.
853 853
854 5.3.5) clock 854 5.3.5) clock
855 ------------ 855 ------------
856 856
857 :Syntax: clock:x 857 :Syntax: clock:x
858 858
859 x = clock input in MHz for WD33c93 chip. Norma 859 x = clock input in MHz for WD33c93 chip. Normal values would be from
860 8 through 20. The default value depends on you 860 8 through 20. The default value depends on your hostadapter(s),
861 default for the A3000 internal controller is 1 861 default for the A3000 internal controller is 14, for the A2091 it's 8
862 and for the GVP hostadapters it's either 8 or 862 and for the GVP hostadapters it's either 8 or 14, depending on the
863 hostadapter and the SCSI-clock jumper present 863 hostadapter and the SCSI-clock jumper present on some GVP
864 hostadapters. 864 hostadapters.
865 865
866 5.3.6) next 866 5.3.6) next
867 ----------- 867 -----------
868 868
869 No argument. Used to separate blocks of keywor 869 No argument. Used to separate blocks of keywords when there's more
870 than one wd33c93-based host adapter in the sys 870 than one wd33c93-based host adapter in the system.
871 871
872 5.3.7) nodma 872 5.3.7) nodma
873 ------------ 873 ------------
874 874
875 :Syntax: nodma:x 875 :Syntax: nodma:x
876 876
877 If x is 1 (or if the option is just written as 877 If x is 1 (or if the option is just written as "nodma"), the WD33c93
878 controller will not use DMA (= direct memory a 878 controller will not use DMA (= direct memory access) to access the
879 Amiga's memory. This is useful for some syste 879 Amiga's memory. This is useful for some systems (like A3000's and
880 A4000's with the A3640 accelerator, revision 3 880 A4000's with the A3640 accelerator, revision 3.0) that have problems
881 using DMA to chip memory. The default is 0, i 881 using DMA to chip memory. The default is 0, i.e. to use DMA if
882 possible. 882 possible.
883 883
884 884
885 5.4) gvp11= 885 5.4) gvp11=
886 ----------- 886 -----------
887 887
888 :Syntax: gvp11=<addr-mask> 888 :Syntax: gvp11=<addr-mask>
889 889
890 The earlier versions of the GVP driver did not 890 The earlier versions of the GVP driver did not handle DMA
891 address-mask settings correctly which made it 891 address-mask settings correctly which made it necessary for some
892 people to use this option, in order to get the 892 people to use this option, in order to get their GVP controller
893 running under Linux. These problems have hopef 893 running under Linux. These problems have hopefully been solved and the
894 use of this option is now highly unrecommended 894 use of this option is now highly unrecommended!
895 895
896 Incorrect use can lead to unpredictable behavi 896 Incorrect use can lead to unpredictable behavior, so please only use
897 this option if you *know* what you are doing a 897 this option if you *know* what you are doing and have a reason to do
898 so. In any case if you experience problems and 898 so. In any case if you experience problems and need to use this
899 option, please inform us about it by mailing t 899 option, please inform us about it by mailing to the Linux/68k kernel
900 mailing list. 900 mailing list.
901 901
902 The address mask set by this option specifies 902 The address mask set by this option specifies which addresses are
903 valid for DMA with the GVP Series II SCSI cont 903 valid for DMA with the GVP Series II SCSI controller. An address is
904 valid, if no bits are set except the bits that 904 valid, if no bits are set except the bits that are set in the mask,
905 too. 905 too.
906 906
907 Some versions of the GVP can only DMA into a 2 907 Some versions of the GVP can only DMA into a 24 bit address range,
908 some can address a 25 bit address range while 908 some can address a 25 bit address range while others can use the whole
909 32 bit address range for DMA. The correct sett 909 32 bit address range for DMA. The correct setting depends on your
910 controller and should be autodetected by the d 910 controller and should be autodetected by the driver. An example is the
911 24 bit region which is specified by a mask of 911 24 bit region which is specified by a mask of 0x00fffffe.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.