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