patch-2.1.129 linux/Documentation/networking/ltpc.txt

• Lines: 122
• Date: Fri Nov 13 10:29:43 1998
• Orig file: v2.1.128/linux/Documentation/networking/ltpc.txt
• Orig date: Sat May 2 14:19:51 1998

diff -u --recursive --new-file v2.1.128/linux/Documentation/networking/ltpc.txt linux/Documentation/networking/ltpc.txt
@@ -6,18 +6,37 @@
 driver applies only to the one with the 65c02 processor chip on it.
 
 To include it in the kernel, select the CONFIG_LTPC switch in the
-configuration dialog; at this time (kernel 2.1.23) compiling it as
-a module will not work.
+configuration dialog.  You can also compile it as a module.
+
+While the driver will attempt to autoprobe the I/O port address, IRQ
+line, and DMA channel of the card, this does not always work.  For
+this reason, you should be prepared to supply these parameters
+yourself.  (see "Card Configuration" below for how to determine or
+change the settings on your card)
+
+When the driver is compiled into the kernel, you can add a line such
+as the following to your /etc/lilo.conf:
+
+ append="ltpc=0x240,9,1"
+
+where the parameters (in order) are the port address, IRQ, and DMA
+channel.  The second and third values can be omitted, in which case
+the driver will try to determine them itself.
+
+If you load the driver as a module, you can pass the parameters "io=",
+"irq=", and "dma=" on the command line with insmod or modprobe, or add
+them as options in /etc/conf.modules:
+
+ alias lt0 ltpc # autoload the module when the interface is configured
+ options ltpc io=0x240 irq=9 dma=1
 
 Before starting up the netatalk demons (perhaps in rc.local), you
 need to add a line such as:
 
-/sbin/ifconfig ltalk0 127.0.0.42
-
+ /sbin/ifconfig lt0 127.0.0.42
 
-The driver will autoprobe, and you should see a message like:
-"LocalTalk card found at 240, IR9, DMA1."
-at bootup.
+The address is unimportant - however, the card needs to be configured
+with ifconfig so that Netatalk can find it.
 
 The appropriate netatalk configuration depends on whether you are
 attached to a network that includes AppleTalk routers or not.  If,
@@ -25,22 +44,22 @@
 printers, you need to set up netatalk to "seed".  The way I do this
 is to have the lines
 
-dummy -seed -phase 2 -net 2000 -addr 2000.26 -zone "1033"
-ltalk0 -seed -phase 1 -net 1033 -addr 1033.27 -zone "1033"
+ dummy -seed -phase 2 -net 2000 -addr 2000.26 -zone "1033"
+ lt0 -seed -phase 1 -net 1033 -addr 1033.27 -zone "1033"
 
 in my atalkd.conf.  What is going on here is that I need to fool
 netatalk into thinking that there are two AppleTalk interfaces
-present -- otherwise it refuses to seed.  This is a hack, and a
-more permanent solution would be to alter the netatalk code.
-Note that the dummy driver needs to accept multicasts also -- earlier
-versions of dummy.c may need to be patched.  
-
+present; otherwise, it refuses to seed.  This is a hack, and a more
+permanent solution would be to alter the netatalk code.  Also, make
+sure you have the correct name for the dummy interface - If it's
+compiled as a module, you will need to refer to it as "dummy0" or some
+such.
 
 If you are attached to an extended AppleTalk network, with routers on
 it, then you don't need to fool around with this -- the appropriate
 line in atalkd.conf is
 
-ltalk0 -phase 1
+ lt0 -phase 1
 
 --------------------------------------
 
@@ -74,19 +93,32 @@
 --------------------------------------
 
 IP:
-	Many people are interested in this driver in order to use IP
-when LocalTalk, but no Ethernet, is available.  While the code to do
-this is not strictly speaking part of this driver, an experimental 
-version is available which seems to work under kernel 2.0.xx.  It is
-not yet functional in the 2.1.xx kernels.
+
+Yes, it is possible to do IP over LocalTalk.  However, you can't just
+treat the LocalTalk device like an ordinary Ethernet device, even if
+that's what it looks like to Netatalk.
+
+Instead, you follow the same procedure as for doing IP in EtherTalk.
+See Documentation/networking/ipddp.txt for more information about the
+kernel driver and userspace tools needed.
 
 --------------------------------------
 
 BUGS:
 
-2.0.xx:
-
-2.1.xx:	The module support doesn't work yet.
+IRQ autoprobing often doesn't work on a cold boot.  To get around
+this, either compile the driver as a module, or pass the parameters
+for the card to the kernel as described above.
+
+Also, as usual, autoprobing is not recommended when you use the driver
+as a module. (though it usually works at boot time, at least)
+
+Polled mode is *really* slow sometimes, but this seems to depend on
+the configuration of the network.
+
+It may theoretically be possible to use two LTPC cards in the same
+machine, but this is unsupported, so if you really want to do this,
+you'll probably have to hack the initialization code a bit.
 
 ______________________________________
 
@@ -96,3 +128,4 @@
 
 -- Bradford Johnson <bradford@math.umn.edu>
 
+-- Updated 11/09/1998 by David Huggins-Daines <dhd@debian.org>