€•jŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ#/translations/zh_CN/networking/plip”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ#/translations/zh_TW/networking/plip”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ#/translations/it_IT/networking/plip”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ#/translations/ja_JP/networking/plip”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ#/translations/ko_KR/networking/plip”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ#/translations/sp_SP/networking/plip”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1h¡hhhžhhŸŒ=/var/lib/git/docbuild/linux/Documentation/networking/plip.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ0PLIP: The Parallel Line Internet Protocol Device”h]”hŒ0PLIP: The Parallel Line Internet Protocol Device”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒ paragraph”“”)”}”(hŒVDonald Becker (becker@super.org) I.D.A. Supercomputing Research Center, Bowie MD 20715”h]”(hŒDonald Becker (”…””}”(hhËhžhhŸNh NubhŒ reference”“”)”}”(hŒbecker@super.org”h]”hŒbecker@super.org”…””}”(hhÕhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:becker@super.org”uh1hÓhhËubhŒ7) I.D.A. Supercomputing Research Center, Bowie MD 20715”…””}”(hhËhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhÊ)”}”(hŒWAt some point T. Thorn will probably contribute text, Tommy Thorn (tthorn@daimi.aau.dk)”h]”(hŒCAt some point T. Thorn will probably contribute text, Tommy Thorn (”…””}”(hhïhžhhŸNh NubhÔ)”}”(hŒtthorn@daimi.aau.dk”h]”hŒtthorn@daimi.aau.dk”…””}”(hh÷hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:tthorn@daimi.aau.dk”uh1hÓhhïubhŒ)”…””}”(hhïhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K hh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒPLIP Introduction”h]”hŒPLIP Introduction”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjhžhhŸh³h KubhÊ)”}”(hŒ½This document describes the parallel port packet pusher for Net/LGX. This device interface allows a point-to-point connection between two parallel ports to appear as a IP network interface.”h]”hŒ½This document describes the parallel port packet pusher for Net/LGX. This device interface allows a point-to-point connection between two parallel ports to appear as a IP network interface.”…””}”(hj"hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khjhžhubhµ)”}”(hhh]”(hº)”}”(hŒ What is PLIP?”h]”hŒ What is PLIP?”…””}”(hj3hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj0hžhhŸh³h KubhÊ)”}”(hXkPLIP is Parallel Line IP, that is, the transportation of IP packages over a parallel port. In the case of a PC, the obvious choice is the printer port. PLIP is a non-standard, but [can use] uses the standard LapLink null-printer cable [can also work in turbo mode, with a PLIP cable]. [The protocol used to pack IP packages, is a simple one initiated by Crynwr.]”h]”hXkPLIP is Parallel Line IP, that is, the transportation of IP packages over a parallel port. In the case of a PC, the obvious choice is the printer port. PLIP is a non-standard, but [can use] uses the standard LapLink null-printer cable [can also work in turbo mode, with a PLIP cable]. [The protocol used to pack IP packages, is a simple one initiated by Crynwr.]”…””}”(hjAhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj0hžhubeh}”(h]”Œ what-is-plip”ah ]”h"]”Œ what is plip?”ah$]”h&]”uh1h´hjhžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒAdvantages of PLIP”h]”hŒAdvantages of PLIP”…””}”(hjZhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjWhžhhŸh³h KubhÊ)”}”(hŒ5It's cheap, it's available everywhere, and it's easy.”h]”hŒ;It’s cheap, it’s available everywhere, and it’s easy.”…””}”(hjhhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K!hjWhžhubhÊ)”}”(hŒgThe PLIP cable is all that's needed to connect two Linux boxes, and it can be built for very few bucks.”h]”hŒiThe PLIP cable is all that’s needed to connect two Linux boxes, and it can be built for very few bucks.”…””}”(hjvhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K#hjWhžhubhÊ)”}”(hŒêConnecting two Linux boxes takes only a second's decision and a few minutes' work, no need to search for a [supported] netcard. This might even be especially important in the case of notebooks, where netcards are not easily available.”h]”hŒîConnecting two Linux boxes takes only a second’s decision and a few minutes’ work, no need to search for a [supported] netcard. This might even be especially important in the case of notebooks, where netcards are not easily available.”…””}”(hj„hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K&hjWhžhubhÊ)”}”(hŒ¡Not requiring a netcard also means that apart from connecting the cables, everything else is software configuration [which in principle could be made very easy.]”h]”hŒ¡Not requiring a netcard also means that apart from connecting the cables, everything else is software configuration [which in principle could be made very easy.]”…””}”(hj’hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K+hjWhžhubeh}”(h]”Œadvantages-of-plip”ah ]”h"]”Œadvantages of plip”ah$]”h&]”uh1h´hjhžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒDisadvantages of PLIP”h]”hŒDisadvantages of PLIP”…””}”(hj«hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj¨hžhhŸh³h K0ubhÊ)”}”(hŒÖDoesn't work over a modem, like SLIP and PPP. Limited range, 15 m. Can only be used to connect three (?) Linux boxes. Doesn't connect to an existing Ethernet. Isn't standard (not even de facto standard, like SLIP).”h]”hŒÜDoesn’t work over a modem, like SLIP and PPP. Limited range, 15 m. Can only be used to connect three (?) Linux boxes. Doesn’t connect to an existing Ethernet. Isn’t standard (not even de facto standard, like SLIP).”…””}”(hj¹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K2hj¨hžhubeh}”(h]”Œdisadvantages-of-plip”ah ]”h"]”Œdisadvantages of plip”ah$]”h&]”uh1h´hjhžhhŸh³h K0ubhµ)”}”(hhh]”(hº)”}”(hŒ Performance”h]”hŒ Performance”…””}”(hjÒhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÏhžhhŸh³h K8ubhÊ)”}”(hŒ^PLIP easily outperforms Ethernet cards....(ups, I was dreaming, but it *is* getting late. EOB)”h]”(hŒGPLIP easily outperforms Ethernet cards....(ups, I was dreaming, but it ”…””}”(hjàhžhhŸNh NubhŒemphasis”“”)”}”(hŒ*is*”h]”hŒis”…””}”(hjêhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jèhjàubhŒ getting late. EOB)”…””}”(hjàhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K:hjÏhžhubeh}”(h]”Œ performance”ah ]”h"]”Œ performance”ah$]”h&]”uh1h´hjhžhhŸh³h K8ubeh}”(h]”Œplip-introduction”ah ]”h"]”Œplip introduction”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒPLIP driver details”h]”hŒPLIP driver details”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjhžhhŸh³h K>ubhÊ)”}”(hŒÊThe Linux PLIP driver is an implementation of the original Crynwr protocol, that uses the parallel port subsystem of the kernel in order to properly share parallel ports between PLIP and other services.”h]”hŒÊThe Linux PLIP driver is an implementation of the original Crynwr protocol, that uses the parallel port subsystem of the kernel in order to properly share parallel ports between PLIP and other services.”…””}”(hj#hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K@hjhžhubhµ)”}”(hhh]”(hº)”}”(hŒIRQs and trigger timeouts”h]”hŒIRQs and trigger timeouts”…””}”(hj4hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj1hžhhŸh³h KEubhÊ)”}”(hŒÑWhen a parallel port used for a PLIP driver has an IRQ configured to it, the PLIP driver is signaled whenever data is sent to it via the cable, such that when no data is available, the driver isn't being used.”h]”hŒÓWhen a parallel port used for a PLIP driver has an IRQ configured to it, the PLIP driver is signaled whenever data is sent to it via the cable, such that when no data is available, the driver isn’t being used.”…””}”(hjBhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KGhj1hžhubhÊ)”}”(hXÝHowever, on some machines it is hard, if not impossible, to configure an IRQ to a certain parallel port, mainly because it is used by some other device. On these machines, the PLIP driver can be used in IRQ-less mode, where the PLIP driver would constantly poll the parallel port for data waiting, and if such data is available, process it. This mode is less efficient than the IRQ mode, because the driver has to check the parallel port many times per second, even when no data at all is sent. Some rough measurements indicate that there isn't a noticeable performance drop when using IRQ-less mode as compared to IRQ mode as far as the data transfer speed is involved. There is a performance drop on the machine hosting the driver.”h]”hXßHowever, on some machines it is hard, if not impossible, to configure an IRQ to a certain parallel port, mainly because it is used by some other device. On these machines, the PLIP driver can be used in IRQ-less mode, where the PLIP driver would constantly poll the parallel port for data waiting, and if such data is available, process it. This mode is less efficient than the IRQ mode, because the driver has to check the parallel port many times per second, even when no data at all is sent. Some rough measurements indicate that there isn’t a noticeable performance drop when using IRQ-less mode as compared to IRQ mode as far as the data transfer speed is involved. There is a performance drop on the machine hosting the driver.”…””}”(hjPhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KKhj1hžhubhÊ)”}”(hXKWhen the PLIP driver is used in IRQ mode, the timeout used for triggering a data transfer (the maximal time the PLIP driver would allow the other side before announcing a timeout, when trying to handshake a transfer of some data) is, by default, 500usec. As IRQ delivery is more or less immediate, this timeout is quite sufficient.”h]”hXKWhen the PLIP driver is used in IRQ mode, the timeout used for triggering a data transfer (the maximal time the PLIP driver would allow the other side before announcing a timeout, when trying to handshake a transfer of some data) is, by default, 500usec. As IRQ delivery is more or less immediate, this timeout is quite sufficient.”…””}”(hj^hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KVhj1hžhubhÊ)”}”(hXxWhen in IRQ-less mode, the PLIP driver polls the parallel port HZ times per second (where HZ is typically 100 on most platforms, and 1024 on an Alpha, as of this writing). Between two such polls, there are 10^6/HZ usecs. On an i386, for example, 10^6/100 = 10000usec. It is easy to see that it is quite possible for the trigger timeout to expire between two such polls, as the timeout is only 500usec long. As a result, it is required to change the trigger timeout on the *other* side of a PLIP connection, to about 10^6/HZ usecs. If both sides of a PLIP connection are used in IRQ-less mode, this timeout is required on both sides.”h]”(hXØWhen in IRQ-less mode, the PLIP driver polls the parallel port HZ times per second (where HZ is typically 100 on most platforms, and 1024 on an Alpha, as of this writing). Between two such polls, there are 10^6/HZ usecs. On an i386, for example, 10^6/100 = 10000usec. It is easy to see that it is quite possible for the trigger timeout to expire between two such polls, as the timeout is only 500usec long. As a result, it is required to change the trigger timeout on the ”…””}”(hjlhžhhŸNh Nubjé)”}”(hŒ*other*”h]”hŒother”…””}”(hjthžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jèhjlubhŒ™ side of a PLIP connection, to about 10^6/HZ usecs. If both sides of a PLIP connection are used in IRQ-less mode, this timeout is required on both sides.”…””}”(hjlhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K\hj1hžhubhÊ)”}”(hŒøIt appears that in practice, the trigger timeout can be shorter than in the above calculation. It isn't an important issue, unless the wire is faulty, in which case a long timeout would stall the machine when, for whatever reason, bits are dropped.”h]”hŒúIt appears that in practice, the trigger timeout can be shorter than in the above calculation. It isn’t an important issue, unless the wire is faulty, in which case a long timeout would stall the machine when, for whatever reason, bits are dropped.”…””}”(hjŒhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kfhj1hžhubhÊ)”}”(hXA utility that can perform this change in Linux is plipconfig, which is part of the net-tools package (its location can be found in the Documentation/Changes file). An example command would be 'plipconfig plipX trigger 10000', where plipX is the appropriate PLIP device.”h]”hXA utility that can perform this change in Linux is plipconfig, which is part of the net-tools package (its location can be found in the Documentation/Changes file). An example command would be ‘plipconfig plipX trigger 10000’, where plipX is the appropriate PLIP device.”…””}”(hjšhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kkhj1hžhubeh}”(h]”Œirqs-and-trigger-timeouts”ah ]”h"]”Œirqs and trigger timeouts”ah$]”h&]”uh1h´hjhžhhŸh³h KEubeh}”(h]”Œplip-driver-details”ah ]”h"]”Œplip driver details”ah$]”h&]”uh1h´hh¶hžhhŸh³h K>ubhµ)”}”(hhh]”(hº)”}”(hŒPLIP hardware interconnection”h]”hŒPLIP hardware interconnection”…””}”(hj»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj¸hžhhŸh³h KrubhÊ)”}”(hŒþPLIP uses several different data transfer methods. The first (and the only one implemented in the early version of the code) uses a standard printer "null" cable to transfer data four bits at a time using data bit outputs connected to status bit inputs.”h]”hXPLIP uses several different data transfer methods. The first (and the only one implemented in the early version of the code) uses a standard printer “null†cable to transfer data four bits at a time using data bit outputs connected to status bit inputs.”…””}”(hjÉhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kthj¸hžhubhÊ)”}”(hŒùThe second data transfer method relies on both machines having bi-directional parallel ports, rather than output-only ``printer`` ports. This allows byte-wide transfers and avoids reconstructing nibbles into bytes, leading to much faster transfers.”h]”(hŒvThe second data transfer method relies on both machines having bi-directional parallel ports, rather than output-only ”…””}”(hj×hžhhŸNh NubhŒliteral”“”)”}”(hŒ ``printer``”h]”hŒprinter”…””}”(hjáhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jßhj×ubhŒx ports. This allows byte-wide transfers and avoids reconstructing nibbles into bytes, leading to much faster transfers.”…””}”(hj×hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kyhj¸hžhubhµ)”}”(hhh]”(hº)”}”(hŒParallel Transfer Mode 0 Cable”h]”hŒParallel Transfer Mode 0 Cable”…””}”(hjühžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjùhžhhŸh³h KubhÊ)”}”(hX¼The cable for the first transfer mode is a standard printer "null" cable which transfers data four bits at a time using data bit outputs of the first port (machine T) connected to the status bit inputs of the second port (machine R). There are five status inputs, and they are used as four data inputs and a clock (data strobe) input, arranged so that the data input bits appear as contiguous bits with standard status register implementation.”h]”hXÀThe cable for the first transfer mode is a standard printer “null†cable which transfers data four bits at a time using data bit outputs of the first port (machine T) connected to the status bit inputs of the second port (machine R). There are five status inputs, and they are used as four data inputs and a clock (data strobe) input, arranged so that the data input bits appear as contiguous bits with standard status register implementation.”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KhjùhžhubhÊ)”}”(hŒÈA cable that implements this protocol is available commercially as a "Null Printer" or "Turbo Laplink" cable. It can be constructed with two DB-25 male connectors symmetrically connected as follows::”h]”hŒÏA cable that implements this protocol is available commercially as a “Null Printer†or “Turbo Laplink†cable. It can be constructed with two DB-25 male connectors symmetrically connected as follows:”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K‰hjùhžhubhŒ literal_block”“”)”}”(hX„STROBE output 1* D0->ERROR 2 - 15 15 - 2 D1->SLCT 3 - 13 13 - 3 D2->PAPOUT 4 - 12 12 - 4 D3->ACK 5 - 10 10 - 5 D4->BUSY 6 - 11 11 - 6 D5,D6,D7 are 7*, 8*, 9* AUTOFD output 14* INIT output 16* SLCTIN 17 - 17 extra grounds are 18*,19*,20*,21*,22*,23*,24* GROUND 25 - 25 * Do not connect these pins on either end”h]”hX„STROBE output 1* D0->ERROR 2 - 15 15 - 2 D1->SLCT 3 - 13 13 - 3 D2->PAPOUT 4 - 12 12 - 4 D3->ACK 5 - 10 10 - 5 D4->BUSY 6 - 11 11 - 6 D5,D6,D7 are 7*, 8*, 9* AUTOFD output 14* INIT output 16* SLCTIN 17 - 17 extra grounds are 18*,19*,20*,21*,22*,23*,24* GROUND 25 - 25 * Do not connect these pins on either end”…””}”hj(sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j&hŸh³h KhjùhžhubhÊ)”}”(hŒtIf the cable you are using has a metallic shield it should be connected to the metallic DB-25 shell at one end only.”h]”hŒtIf the cable you are using has a metallic shield it should be connected to the metallic DB-25 shell at one end only.”…””}”(hj6hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kœhjùhžhubeh}”(h]”Œparallel-transfer-mode-0-cable”ah ]”h"]”Œparallel transfer mode 0 cable”ah$]”h&]”uh1h´hj¸hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒParallel Transfer Mode 1”h]”hŒParallel Transfer Mode 1”…””}”(hjOhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjLhžhhŸh³h K ubhÊ)”}”(hX¾The second data transfer method relies on both machines having bi-directional parallel ports, rather than output-only ``printer`` ports. This allows byte-wide transfers, and avoids reconstructing nibbles into bytes. This cable should not be used on unidirectional ``printer`` (as opposed to ``parallel``) ports or when the machine isn't configured for PLIP, as it will result in output driver conflicts and the (unlikely) possibility of damage.”h]”(hŒvThe second data transfer method relies on both machines having bi-directional parallel ports, rather than output-only ”…””}”(hj]hžhhŸNh Nubjà)”}”(hŒ ``printer``”h]”hŒprinter”…””}”(hjehžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jßhj]ubhŒ‰ ports. This allows byte-wide transfers, and avoids reconstructing nibbles into bytes. This cable should not be used on unidirectional ”…””}”(hj]hžhhŸNh Nubjà)”}”(hŒ ``printer``”h]”hŒprinter”…””}”(hjwhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jßhj]ubhŒ (as opposed to ”…””}”(hj]hžhhŸNh Nubjà)”}”(hŒ ``parallel``”h]”hŒparallel”…””}”(hj‰hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jßhj]ubhŒ) ports or when the machine isn’t configured for PLIP, as it will result in output driver conflicts and the (unlikely) possibility of damage.”…””}”(hj]hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K¢hjLhžhubhÊ)”}”(hŒCThe cable for this transfer mode should be constructed as follows::”h]”hŒBThe cable for this transfer mode should be constructed as follows:”…””}”(hj¡hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KªhjLhžhubj')”}”(hXaSTROBE->BUSY 1 - 11 D0->D0 2 - 2 D1->D1 3 - 3 D2->D2 4 - 4 D3->D3 5 - 5 D4->D4 6 - 6 D5->D5 7 - 7 D6->D6 8 - 8 D7->D7 9 - 9 INIT -> ACK 16 - 10 AUTOFD->PAPOUT 14 - 12 SLCT->SLCTIN 13 - 17 GND->ERROR 18 - 15 extra grounds are 19*,20*,21*,22*,23*,24* GROUND 25 - 25 * Do not connect these pins on either end”h]”hXaSTROBE->BUSY 1 - 11 D0->D0 2 - 2 D1->D1 3 - 3 D2->D2 4 - 4 D3->D3 5 - 5 D4->D4 6 - 6 D5->D5 7 - 7 D6->D6 8 - 8 D7->D7 9 - 9 INIT -> ACK 16 - 10 AUTOFD->PAPOUT 14 - 12 SLCT->SLCTIN 13 - 17 GND->ERROR 18 - 15 extra grounds are 19*,20*,21*,22*,23*,24* GROUND 25 - 25 * Do not connect these pins on either end”…””}”hj¯sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j&hŸh³h K¬hjLhžhubhÊ)”}”(hŒ€Once again, if the cable you are using has a metallic shield it should be connected to the metallic DB-25 shell at one end only.”h]”hŒ€Once again, if the cable you are using has a metallic shield it should be connected to the metallic DB-25 shell at one end only.”…””}”(hj½hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K¾hjLhžhubeh}”(h]”Œparallel-transfer-mode-1”ah ]”h"]”Œparallel transfer mode 1”ah$]”h&]”uh1h´hj¸hžhhŸh³h K ubhµ)”}”(hhh]”(hº)”}”(hŒPLIP Mode 0 transfer protocol”h]”hŒPLIP Mode 0 transfer protocol”…””}”(hjÖhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÓhžhhŸh³h KÂubhÊ)”}”(hŒŒThe PLIP driver is compatible with the "Crynwr" parallel port transfer standard in Mode 0. That standard specifies the following protocol::”h]”hŒThe PLIP driver is compatible with the “Crynwr†parallel port transfer standard in Mode 0. That standard specifies the following protocol:”…””}”(hjähžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KÄhjÓhžhubj')”}”(hŒXsend header nibble '0x8' count-low octet count-high octet ... data octets checksum octet”h]”hŒXsend header nibble '0x8' count-low octet count-high octet ... data octets checksum octet”…””}”hjòsbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j&hŸh³h KÇhjÓhžhubhÊ)”}”(hŒEach octet is sent as::”h]”hŒEach octet is sent as:”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KÍhjÓhžhubj')”}”(hŒf >4)&0x0F)>”h]”hŒf >4)&0x0F)>”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j&hŸh³h KÏhjÓhžhubhÊ)”}”(hŒ×To start a transfer the transmitting machine outputs a nibble 0x08. That raises the ACK line, triggering an interrupt in the receiving machine. The receiving machine disables interrupts and raises its own ACK line.”h]”hŒ×To start a transfer the transmitting machine outputs a nibble 0x08. That raises the ACK line, triggering an interrupt in the receiving machine. The receiving machine disables interrupts and raises its own ACK line.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KÒhjÓhžhubhÊ)”}”(hŒ Restated::”h]”hŒ Restated:”…””}”(hj*hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K×hjÓhžhubj')”}”(hŒ®(OUT is bit 0-4, OUT.j is bit j from OUT. IN likewise) Send_Byte: OUT := low nibble, OUT.4 := 1 WAIT FOR IN.4 = 1 OUT := high nibble, OUT.4 := 0 WAIT FOR IN.4 = 0”h]”hŒ®(OUT is bit 0-4, OUT.j is bit j from OUT. IN likewise) Send_Byte: OUT := low nibble, OUT.4 := 1 WAIT FOR IN.4 = 1 OUT := high nibble, OUT.4 := 0 WAIT FOR IN.4 = 0”…””}”hj8sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j&hŸh³h KÙhjÓhžhubeh}”(h]”Œplip-mode-0-transfer-protocol”ah ]”h"]”Œplip mode 0 transfer protocol”ah$]”h&]”uh1h´hj¸hžhhŸh³h KÂubeh}”(h]”Œplip-hardware-interconnection”ah ]”h"]”Œplip hardware interconnection”ah$]”h&]”uh1h´hh¶hžhhŸh³h Krubeh}”(h]”Œ/plip-the-parallel-line-internet-protocol-device”ah ]”h"]”Œ0plip: the parallel line internet protocol device”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¹NŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jŒerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j[jXjj jTjQj¥j¢jÌjÉjjjµj²j­jªjSjPjIjFjÐjÍjKjHuŒ nametypes”}”(j[‰j‰jT‰j¥‰j̉j‰jµ‰j­‰jS‰jI‰jЉjK‰uh}”(jXh¶j jjQj0j¢jWjÉj¨jjÏj²jjªj1jPj¸jFjùjÍjLjHjÓuŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nhžhub.