1 X.25 Device Driver Interface 1.1
3 Jonathan Naylor 26.12.96
5 This is a description of the messages to be passed between the X.25 Packet
6 Layer and the X.25 device driver. They are designed to allow for the easy
7 setting of the LAPB mode from within the Packet Layer.
9 The X.25 device driver will be coded normally as per the Linux device driver
10 standards. Most X.25 device drivers will be moderately similar to the
11 already existing Ethernet device drivers. However unlike those drivers, the
12 X.25 device driver has a state associated with it, and this information
13 needs to be passed to and from the Packet Layer for proper operation.
15 All messages are held in sk_buff's just like real data to be transmitted
16 over the LAPB link. The first byte of the skbuff indicates the meaning of
17 the rest of the skbuff, if any more information does exist.
20 Packet Layer to Device Driver
21 -----------------------------
25 This indicates that the rest of the skbuff contains data to be transmitted
26 over the LAPB link. The LAPB link should already exist before any data is
31 Establish the LAPB link. If the link is already established then the connect
32 confirmation message should be returned as soon as possible.
36 Terminate the LAPB link. If it is already disconnected then the disconnect
37 confirmation message should be returned as soon as possible.
41 LAPB parameters. To be defined.
44 Device Driver to Packet Layer
45 -----------------------------
49 This indicates that the rest of the skbuff contains data that has been
50 received over the LAPB link.
54 LAPB link has been established. The same message is used for both a LAPB
55 link connect_confirmation and a connect_indication.
59 LAPB link has been terminated. This same message is used for both a LAPB
60 link disconnect_confirmation and a disconnect_indication.
64 LAPB parameters. To be defined.