where IC is of the form [::] , [..], or [==], would incorrectly
report an error.
Fixed input mode bug: a literal ^J(i.e., ^V^J) would discard text
following it. Now, a literal ^J is treated as an ordinary ^J - i.e, it
splits a line in two.
not ported to the '386 (xdr_float.c was excluded in the makefile).
Since the '386, like the 68k and sparc, uses IEEE floating point, all
that was needed was to take word ordering into account for
xdr_double().
patch from J.T. Conklin <conklin@talisman.kaleida.com>
hacked to use BYTE_ORDER macros from machine/endian.h
may be. basically to find out whether nfsserver support is in the kernel
earlier and thus avoid the loop problem, call nfssvc() with a bogus fd and
see whether you get a -1 return value or a SIGSYS...
2. "irq ?" sets it to (u_short)-1
3. "irq #" sets it to (1<<#)
4. not specifying an interrupt sets it to 0.
Until someone else comes up with a better scheme, that's the way it is.
If you have a driver that turns the interrupt off, set it to ZERO.
If, after calling XXprobe(), id_irq is still (u_short)-1, that is the same
as if probe() failed.
2. "irq ?" sets it to (u_short)-1
3. "irq #" sets it to (1<<#)
4. not specifying an interrupt sets it to 0.
Until someone else comes up with a better scheme, that's the way it is.
If you have a driver that turns the interrupt off, set it to ZERO.
If, after calling XXprobe(), id_irq is still (u_short)-1, that is the same
as if XXprobe() failed.
and scsi disks. See?
fd0 at fdc0 slave 0: 1.44MB 80 cyl, 2 head, 18 sec
Also, added a define for 720K disks, probably incorrect..
Note: the CMOS is used to find out what type the drive is.
WD1007-derived controllers. In this example, wdc0 is a WD1007-clone,
and wdc1 is a WD1003-clone. WD1007 controllers are generally ESDI
and IDE controllers.
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wd0 at wdc0 targ 0: 322MB 1224 cyl, 15 head, 36 sec <disktype>
wdc1 at 0x170-0x17f irq 7 on isa
wd2 at wdc1 targ 0: (unknown size) <disktype>
