diff options
author | Ralf Baechle <ralf@linux-mips.org> | 2000-02-24 00:12:35 +0000 |
---|---|---|
committer | Ralf Baechle <ralf@linux-mips.org> | 2000-02-24 00:12:35 +0000 |
commit | 482368b1a8e45430672c58c9a42e7d2004367126 (patch) | |
tree | ce2a1a567d4d62dee7c2e71a46a99cf72cf1d606 /Documentation/isdn/README.x25 | |
parent | e4d0251c6f56ab2e191afb70f80f382793e23f74 (diff) |
Merge with 2.3.47. Guys, this is buggy as shit. You've been warned.
Diffstat (limited to 'Documentation/isdn/README.x25')
-rw-r--r-- | Documentation/isdn/README.x25 | 16 |
1 files changed, 15 insertions, 1 deletions
diff --git a/Documentation/isdn/README.x25 b/Documentation/isdn/README.x25 index 9794f4118..e561a77c4 100644 --- a/Documentation/isdn/README.x25 +++ b/Documentation/isdn/README.x25 @@ -61,7 +61,21 @@ X.25 on top of isdn might be useful with two different scenarios: - You might want to access a public X.25 data network from your Linux box. You can use i4l if you were physically connected to the X.25 switch - by an ISDN line (leased line as well as dial up connection should work) + by an ISDN B-channel (leased line as well as dial up connection should + work). + + This corresponds to ITU-T recommendation X.31 Case A (circuit-mode + access to PSPDN [packet switched public data network]). + + NOTE: X.31 also covers a Case B (access to PSPDN via virtual + circuit / packet mode service). The latter mode (which in theory + also allows using the D-channel) is not supported by isdn4linux. + It should however be possible to establish such packet mode connections + with certain active isdn cards provided that the firmware supports X.31 + and the driver exports this functionality to the user. Currently, + the AVM B1 driver is the only driver which does so. (It should be + possible to access D-channel X.31 with active AVM cards using the + CAPI interface of the AVM-B1 driver). - Or you might want to operate certain ISDN teleservices on your linux box. A lot of those teleservices run on top of the ISO-8208 |