^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) ===================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) Linux and parallel port IDE devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) ===================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) PARIDE v1.03 (c) 1997-8 Grant Guenther <grant@torque.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) 1. Introduction
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8) ===============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) Owing to the simplicity and near universality of the parallel port interface
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) to personal computers, many external devices such as portable hard-disk,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) CD-ROM, LS-120 and tape drives use the parallel port to connect to their
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) host computer. While some devices (notably scanners) use ad-hoc methods
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) to pass commands and data through the parallel port interface, most
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) external devices are actually identical to an internal model, but with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) a parallel-port adapter chip added in. Some of the original parallel port
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) adapters were little more than mechanisms for multiplexing a SCSI bus.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) (The Iomega PPA-3 adapter used in the ZIP drives is an example of this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) approach). Most current designs, however, take a different approach.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) The adapter chip reproduces a small ISA or IDE bus in the external device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) and the communication protocol provides operations for reading and writing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) device registers, as well as data block transfer functions. Sometimes,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) the device being addressed via the parallel cable is a standard SCSI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) controller like an NCR 5380. The "ditto" family of external tape
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) drives use the ISA replicator to interface a floppy disk controller,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) which is then connected to a floppy-tape mechanism. The vast majority
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) of external parallel port devices, however, are now based on standard
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) IDE type devices, which require no intermediate controller. If one
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) were to open up a parallel port CD-ROM drive, for instance, one would
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) find a standard ATAPI CD-ROM drive, a power supply, and a single adapter
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) that interconnected a standard PC parallel port cable and a standard
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) IDE cable. It is usually possible to exchange the CD-ROM device with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) any other device using the IDE interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) The document describes the support in Linux for parallel port IDE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) devices. It does not cover parallel port SCSI devices, "ditto" tape
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) drives or scanners. Many different devices are supported by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) parallel port IDE subsystem, including:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) - MicroSolutions backpack CD-ROM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) - MicroSolutions backpack PD/CD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) - MicroSolutions backpack hard-drives
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) - MicroSolutions backpack 8000t tape drive
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) - SyQuest EZ-135, EZ-230 & SparQ drives
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) - Avatar Shark
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) - Imation Superdisk LS-120
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) - Maxell Superdisk LS-120
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) - FreeCom Power CD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) - Hewlett-Packard 5GB and 8GB tape drives
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) - Hewlett-Packard 7100 and 7200 CD-RW drives
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) as well as most of the clone and no-name products on the market.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) To support such a wide range of devices, PARIDE, the parallel port IDE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) subsystem, is actually structured in three parts. There is a base
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) paride module which provides a registry and some common methods for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) accessing the parallel ports. The second component is a set of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) high-level drivers for each of the different types of supported devices:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) === =============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) pd IDE disk
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) pcd ATAPI CD-ROM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) pf ATAPI disk
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) pt ATAPI tape
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) pg ATAPI generic
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66) === =============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) (Currently, the pg driver is only used with CD-R drives).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) The high-level drivers function according to the relevant standards.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) The third component of PARIDE is a set of low-level protocol drivers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) for each of the parallel port IDE adapter chips. Thanks to the interest
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) and encouragement of Linux users from many parts of the world,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) support is available for almost all known adapter protocols:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) ==== ====================================== ====
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) aten ATEN EH-100 (HK)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) bpck Microsolutions backpack (US)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) comm DataStor (old-type) "commuter" adapter (TW)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) dstr DataStor EP-2000 (TW)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) epat Shuttle EPAT (UK)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) epia Shuttle EPIA (UK)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) fit2 FIT TD-2000 (US)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) fit3 FIT TD-3000 (US)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) friq Freecom IQ cable (DE)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) frpw Freecom Power (DE)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) kbic KingByte KBIC-951A and KBIC-971A (TW)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) ktti KT Technology PHd adapter (SG)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) on20 OnSpec 90c20 (US)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) on26 OnSpec 90c26 (US)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) ==== ====================================== ====
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) 2. Using the PARIDE subsystem
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) =============================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) While configuring the Linux kernel, you may choose either to build
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) the PARIDE drivers into your kernel, or to build them as modules.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) In either case, you will need to select "Parallel port IDE device support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) as well as at least one of the high-level drivers and at least one
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) of the parallel port communication protocols. If you do not know
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) what kind of parallel port adapter is used in your drive, you could
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) begin by checking the file names and any text files on your DOS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) installation floppy. Alternatively, you can look at the markings on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) the adapter chip itself. That's usually sufficient to identify the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) correct device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) You can actually select all the protocol modules, and allow the PARIDE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) subsystem to try them all for you.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) For the "brand-name" products listed above, here are the protocol
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) and high-level drivers that you would use:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) ================ ============ ====== ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) Manufacturer Model Driver Protocol
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) ================ ============ ====== ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) MicroSolutions CD-ROM pcd bpck
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) MicroSolutions PD drive pf bpck
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) MicroSolutions hard-drive pd bpck
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) MicroSolutions 8000t tape pt bpck
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) SyQuest EZ, SparQ pd epat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) Imation Superdisk pf epat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) Maxell Superdisk pf friq
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) Avatar Shark pd epat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) FreeCom CD-ROM pcd frpw
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) Hewlett-Packard 5GB Tape pt epat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) Hewlett-Packard 7200e (CD) pcd epat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) Hewlett-Packard 7200e (CD-R) pg epat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) ================ ============ ====== ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) 2.1 Configuring built-in drivers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) ---------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) We recommend that you get to know how the drivers work and how to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) configure them as loadable modules, before attempting to compile a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) kernel with the drivers built-in.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) If you built all of your PARIDE support directly into your kernel,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) and you have just a single parallel port IDE device, your kernel should
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) locate it automatically for you. If you have more than one device,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) you may need to give some command line options to your bootloader
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) (eg: LILO), how to do that is beyond the scope of this document.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) The high-level drivers accept a number of command line parameters, all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) of which are documented in the source files in linux/drivers/block/paride.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) By default, each driver will automatically try all parallel ports it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) can find, and all protocol types that have been installed, until it finds
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) a parallel port IDE adapter. Once it finds one, the probe stops. So,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) if you have more than one device, you will need to tell the drivers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) how to identify them. This requires specifying the port address, the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) protocol identification number and, for some devices, the drive's
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) chain ID. While your system is booting, a number of messages are
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) displayed on the console. Like all such messages, they can be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) reviewed with the 'dmesg' command. Among those messages will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) some lines like::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) paride: bpck registered as protocol 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) paride: epat registered as protocol 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) The numbers will always be the same until you build a new kernel with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) different protocol selections. You should note these numbers as you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) will need them to identify the devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) If you happen to be using a MicroSolutions backpack device, you will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) also need to know the unit ID number for each drive. This is usually
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) the last two digits of the drive's serial number (but read MicroSolutions'
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) documentation about this).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) As an example, let's assume that you have a MicroSolutions PD/CD drive
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) with unit ID number 36 connected to the parallel port at 0x378, a SyQuest
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) EZ-135 connected to the chained port on the PD/CD drive and also an
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) Imation Superdisk connected to port 0x278. You could give the following
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) options on your boot command::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) pd.drive0=0x378,1 pf.drive0=0x278,1 pf.drive1=0x378,0,36
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) In the last option, pf.drive1 configures device /dev/pf1, the 0x378
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) is the parallel port base address, the 0 is the protocol registration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) number and 36 is the chain ID.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) Please note: while PARIDE will work both with and without the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) PARPORT parallel port sharing system that is included by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) "Parallel port support" option, PARPORT must be included and enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) if you want to use chains of devices on the same parallel port.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) 2.2 Loading and configuring PARIDE as modules
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) ----------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) It is much faster and simpler to get to understand the PARIDE drivers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) if you use them as loadable kernel modules.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) Note 1:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) using these drivers with the "kerneld" automatic module loading
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) system is not recommended for beginners, and is not documented here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) Note 2:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) if you build PARPORT support as a loadable module, PARIDE must
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) also be built as loadable modules, and PARPORT must be loaded before
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) the PARIDE modules.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202) To use PARIDE, you must begin by::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) insmod paride
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) this loads a base module which provides a registry for the protocols,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) among other tasks.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) Then, load as many of the protocol modules as you think you might need.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) As you load each module, it will register the protocols that it supports,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) and print a log message to your kernel log file and your console. For
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) # insmod epat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) paride: epat registered as protocol 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) # insmod kbic
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) paride: k951 registered as protocol 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) paride: k971 registered as protocol 2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) Finally, you can load high-level drivers for each kind of device that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) you have connected. By default, each driver will autoprobe for a single
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) device, but you can support up to four similar devices by giving their
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) individual co-ordinates when you load the driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) For example, if you had two no-name CD-ROM drives both using the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) KingByte KBIC-951A adapter, one on port 0x378 and the other on 0x3bc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) you could give the following command::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) # insmod pcd drive0=0x378,1 drive1=0x3bc,1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) For most adapters, giving a port address and protocol number is sufficient,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232) but check the source files in linux/drivers/block/paride for more
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) information. (Hopefully someone will write some man pages one day !).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) As another example, here's what happens when PARPORT is installed, and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) a SyQuest EZ-135 is attached to port 0x378::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) # insmod paride
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) paride: version 1.0 installed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) # insmod epat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) paride: epat registered as protocol 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) # insmod pd
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) pd: pd version 1.0, major 45, cluster 64, nice 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244) pda: Sharing parport1 at 0x378
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) pda: epat 1.0, Shuttle EPAT chip c3 at 0x378, mode 5 (EPP-32), delay 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) pda: SyQuest EZ135A, 262144 blocks [128M], (512/16/32), removable media
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) pda: pda1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) Note that the last line is the output from the generic partition table
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) scanner - in this case it reports that it has found a disk with one partition.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) 2.3 Using a PARIDE device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253) --------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255) Once the drivers have been loaded, you can access PARIDE devices in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256) same way as their traditional counterparts. You will probably need to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257) create the device "special files". Here is a simple script that you can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258) cut to a file and execute::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260) #!/bin/bash
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) # mkd -- a script to create the device special files for the PARIDE subsystem
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) function mkdev {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265) mknod $1 $2 $3 $4 ; chmod 0660 $1 ; chown root:disk $1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) }
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) function pd {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269) D=$( printf \\$( printf "x%03x" $[ $1 + 97 ] ) )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270) mkdev pd$D b 45 $[ $1 * 16 ]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) for P in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272) do mkdev pd$D$P b 45 $[ $1 * 16 + $P ]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273) done
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274) }
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276) cd /dev
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278) for u in 0 1 2 3 ; do pd $u ; done
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279) for u in 0 1 2 3 ; do mkdev pcd$u b 46 $u ; done
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) for u in 0 1 2 3 ; do mkdev pf$u b 47 $u ; done
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281) for u in 0 1 2 3 ; do mkdev pt$u c 96 $u ; done
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282) for u in 0 1 2 3 ; do mkdev npt$u c 96 $[ $u + 128 ] ; done
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283) for u in 0 1 2 3 ; do mkdev pg$u c 97 $u ; done
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285) # end of mkd
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287) With the device files and drivers in place, you can access PARIDE devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 288) like any other Linux device. For example, to mount a CD-ROM in pcd0, use::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 289)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 290) mount /dev/pcd0 /cdrom
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 291)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 292) If you have a fresh Avatar Shark cartridge, and the drive is pda, you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 293) might do something like::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 294)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 295) fdisk /dev/pda -- make a new partition table with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 296) partition 1 of type 83
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 297)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 298) mke2fs /dev/pda1 -- to build the file system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 299)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 300) mkdir /shark -- make a place to mount the disk
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 301)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 302) mount /dev/pda1 /shark
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 303)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 304) Devices like the Imation superdisk work in the same way, except that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 305) they do not have a partition table. For example to make a 120MB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 306) floppy that you could share with a DOS system::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 307)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 308) mkdosfs /dev/pf0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 309) mount /dev/pf0 /mnt
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 310)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 311)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 312) 2.4 The pf driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 313) ------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 314)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 315) The pf driver is intended for use with parallel port ATAPI disk
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 316) devices. The most common devices in this category are PD drives
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 317) and LS-120 drives. Traditionally, media for these devices are not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 318) partitioned. Consequently, the pf driver does not support partitioned
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 319) media. This may be changed in a future version of the driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 320)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 321) 2.5 Using the pt driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 322) ------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 323)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 324) The pt driver for parallel port ATAPI tape drives is a minimal driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 325) It does not yet support many of the standard tape ioctl operations.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 326) For best performance, a block size of 32KB should be used. You will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 327) probably want to set the parallel port delay to 0, if you can.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 328)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 329) 2.6 Using the pg driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 330) ------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 331)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 332) The pg driver can be used in conjunction with the cdrecord program
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 333) to create CD-ROMs. Please get cdrecord version 1.6.1 or later
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 334) from ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . To record CD-R media
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 335) your parallel port should ideally be set to EPP mode, and the "port delay"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 336) should be set to 0. With those settings it is possible to record at 2x
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 337) speed without any buffer underruns. If you cannot get the driver to work
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 338) in EPP mode, try to use "bidirectional" or "PS/2" mode and 1x speeds only.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 339)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 340)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 341) 3. Troubleshooting
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 342) ==================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 343)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 344) 3.1 Use EPP mode if you can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 345) ----------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 346)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 347) The most common problems that people report with the PARIDE drivers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 348) concern the parallel port CMOS settings. At this time, none of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 349) PARIDE protocol modules support ECP mode, or any ECP combination modes.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 350) If you are able to do so, please set your parallel port into EPP mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 351) using your CMOS setup procedure.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 352)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 353) 3.2 Check the port delay
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 354) -------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 355)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 356) Some parallel ports cannot reliably transfer data at full speed. To
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 357) offset the errors, the PARIDE protocol modules introduce a "port
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 358) delay" between each access to the i/o ports. Each protocol sets
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 359) a default value for this delay. In most cases, the user can override
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 360) the default and set it to 0 - resulting in somewhat higher transfer
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 361) rates. In some rare cases (especially with older 486 systems) the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 362) default delays are not long enough. if you experience corrupt data
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 363) transfers, or unexpected failures, you may wish to increase the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 364) port delay. The delay can be programmed using the "driveN" parameters
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 365) to each of the high-level drivers. Please see the notes above, or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 366) read the comments at the beginning of the driver source files in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 367) linux/drivers/block/paride.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 368)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 369) 3.3 Some drives need a printer reset
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 370) -------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 371)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 372) There appear to be a number of "noname" external drives on the market
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 373) that do not always power up correctly. We have noticed this with some
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 374) drives based on OnSpec and older Freecom adapters. In these rare cases,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 375) the adapter can often be reinitialised by issuing a "printer reset" on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 376) the parallel port. As the reset operation is potentially disruptive in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 377) multiple device environments, the PARIDE drivers will not do it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 378) automatically. You can however, force a printer reset by doing::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 379)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 380) insmod lp reset=1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 381) rmmod lp
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 382)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 383) If you have one of these marginal cases, you should probably build
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 384) your paride drivers as modules, and arrange to do the printer reset
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 385) before loading the PARIDE drivers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 386)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 387) 3.4 Use the verbose option and dmesg if you need help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 388) ------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 389)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 390) While a lot of testing has gone into these drivers to make them work
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 391) as smoothly as possible, problems will arise. If you do have problems,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 392) please check all the obvious things first: does the drive work in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 393) DOS with the manufacturer's drivers ? If that doesn't yield any useful
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 394) clues, then please make sure that only one drive is hooked to your system,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 395) and that either (a) PARPORT is enabled or (b) no other device driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 396) is using your parallel port (check in /proc/ioports). Then, load the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 397) appropriate drivers (you can load several protocol modules if you want)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 398) as in::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 399)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 400) # insmod paride
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 401) # insmod epat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 402) # insmod bpck
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 403) # insmod kbic
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 404) ...
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 405) # insmod pd verbose=1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 406)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 407) (using the correct driver for the type of device you have, of course).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 408) The verbose=1 parameter will cause the drivers to log a trace of their
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 409) activity as they attempt to locate your drive.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 410)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 411) Use 'dmesg' to capture a log of all the PARIDE messages (any messages
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 412) beginning with paride:, a protocol module's name or a driver's name) and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 413) include that with your bug report. You can submit a bug report in one
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 414) of two ways. Either send it directly to the author of the PARIDE suite,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 415) by e-mail to grant@torque.net, or join the linux-parport mailing list
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 416) and post your report there.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 417)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 418) 3.5 For more information or help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 419) ---------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 420)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 421) You can join the linux-parport mailing list by sending a mail message
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 422) to:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 423)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 424) linux-parport-request@torque.net
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 425)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 426) with the single word::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 427)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 428) subscribe
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 429)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 430) in the body of the mail message (not in the subject line). Please be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 431) sure that your mail program is correctly set up when you do this, as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 432) the list manager is a robot that will subscribe you using the reply
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 433) address in your mail headers. REMOVE any anti-spam gimmicks you may
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 434) have in your mail headers, when sending mail to the list server.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 435)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 436) You might also find some useful information on the linux-parport
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 437) web pages (although they are not always up to date) at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 438)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 439) http://web.archive.org/web/%2E/http://www.torque.net/parport/
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags