diff options
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/isdn/README.gigaset | 65 |
1 files changed, 48 insertions, 17 deletions
diff --git a/Documentation/isdn/README.gigaset b/Documentation/isdn/README.gigaset index fa0d4cca964a..55b2852904a4 100644 --- a/Documentation/isdn/README.gigaset +++ b/Documentation/isdn/README.gigaset | |||
@@ -8,29 +8,33 @@ GigaSet 307x Device Driver | |||
8 | This release supports the connection of the Gigaset 307x/417x family of | 8 | This release supports the connection of the Gigaset 307x/417x family of |
9 | ISDN DECT bases via Gigaset M101 Data, Gigaset M105 Data or direct USB | 9 | ISDN DECT bases via Gigaset M101 Data, Gigaset M105 Data or direct USB |
10 | connection. The following devices are reported to be compatible: | 10 | connection. The following devices are reported to be compatible: |
11 | 307x/417x: | 11 | |
12 | Gigaset SX255isdn | 12 | Bases: |
13 | Gigaset SX353isdn | 13 | Siemens Gigaset 3070/3075 isdn |
14 | Sinus 45 [AB] isdn (Deutsche Telekom) | 14 | Siemens Gigaset 4170/4175 isdn |
15 | Sinus 721X/XA | 15 | Siemens Gigaset SX205/255 |
16 | Siemens Gigaset SX353 | ||
17 | T-Com Sinus 45 [AB] isdn | ||
18 | T-Com Sinus 721X[A] [SE] | ||
16 | Vox Chicago 390 ISDN (KPN Telecom) | 19 | Vox Chicago 390 ISDN (KPN Telecom) |
17 | M101: | 20 | |
18 | Sinus 45 Data 1 (Telekom) | 21 | RS232 data boxes: |
19 | M105: | 22 | Siemens Gigaset M101 Data |
20 | Gigaset USB Adapter DECT | 23 | T-Com Sinus 45 Data 1 |
21 | Sinus 45 Data 2 (Telekom) | 24 | |
22 | Sinus 721 data | 25 | USB data boxes: |
26 | Siemens Gigaset M105 Data | ||
27 | Siemens Gigaset USB Adapter DECT | ||
28 | T-Com Sinus 45 Data 2 | ||
29 | T-Com Sinus 721 data | ||
23 | Chicago 390 USB (KPN) | 30 | Chicago 390 USB (KPN) |
31 | |||
24 | See also http://www.erbze.info/sinus_gigaset.htm and | 32 | See also http://www.erbze.info/sinus_gigaset.htm and |
25 | http://gigaset307x.sourceforge.net/ | 33 | http://gigaset307x.sourceforge.net/ |
26 | 34 | ||
27 | We had also reports from users of Gigaset M105 who could use the drivers | 35 | We had also reports from users of Gigaset M105 who could use the drivers |
28 | with SX 100 and CX 100 ISDN bases (only in unimodem mode, see section 2.4.) | 36 | with SX 100 and CX 100 ISDN bases (only in unimodem mode, see section 2.4.) |
29 | If you have another device that works with our driver, please let us know. | 37 | If you have another device that works with our driver, please let us know. |
30 | For example, Gigaset SX205isdn/Sinus 721 X SE and Gigaset SX303isdn bases | ||
31 | are just versions without answering machine of models known to work, so | ||
32 | they should work just as well; but so far we are lacking positive reports | ||
33 | on these. | ||
34 | 38 | ||
35 | Chances of getting an USB device to work are good if the output of | 39 | Chances of getting an USB device to work are good if the output of |
36 | lsusb | 40 | lsusb |
@@ -60,14 +64,28 @@ GigaSet 307x Device Driver | |||
60 | To get the device working, you have to load the proper kernel module. You | 64 | To get the device working, you have to load the proper kernel module. You |
61 | can do this using | 65 | can do this using |
62 | modprobe modulename | 66 | modprobe modulename |
63 | where modulename is usb_gigaset (M105) or bas_gigaset (direct USB | 67 | where modulename is ser_gigaset (M101), usb_gigaset (M105), or |
64 | connection to the base). | 68 | bas_gigaset (direct USB connection to the base). |
69 | |||
70 | The module ser_gigaset provides a serial line discipline N_GIGASET_M101 | ||
71 | which drives the device through the regular serial line driver. To use it, | ||
72 | run the Gigaset M101 daemon "gigasetm101d" (also available from | ||
73 | http://sourceforge.net/projects/gigaset307x/) with the device file of the | ||
74 | RS232 port to the M101 as an argument, for example: | ||
75 | gigasetm101d /dev/ttyS1 | ||
76 | This will open the device file, set its line discipline to N_GIGASET_M101, | ||
77 | and then sleep in the background, keeping the device open so that the | ||
78 | line discipline remains active. To deactivate it, kill the daemon, for | ||
79 | example with | ||
80 | killall gigasetm101d | ||
81 | before disconnecting the device. | ||
65 | 82 | ||
66 | 2.2. Device nodes for user space programs | 83 | 2.2. Device nodes for user space programs |
67 | ------------------------------------ | 84 | ------------------------------------ |
68 | The device can be accessed from user space (eg. by the user space tools | 85 | The device can be accessed from user space (eg. by the user space tools |
69 | mentioned in 1.2.) through the device nodes: | 86 | mentioned in 1.2.) through the device nodes: |
70 | 87 | ||
88 | - /dev/ttyGS0 for M101 (RS232 data boxes) | ||
71 | - /dev/ttyGU0 for M105 (USB data boxes) | 89 | - /dev/ttyGU0 for M105 (USB data boxes) |
72 | - /dev/ttyGB0 for the base driver (direct USB connection) | 90 | - /dev/ttyGB0 for the base driver (direct USB connection) |
73 | 91 | ||
@@ -168,6 +186,19 @@ GigaSet 307x Device Driver | |||
168 | You can also use /sys/class/tty/ttyGxy/cidmode for changing the CID mode | 186 | You can also use /sys/class/tty/ttyGxy/cidmode for changing the CID mode |
169 | setting (ttyGxy is ttyGU0 or ttyGB0). | 187 | setting (ttyGxy is ttyGU0 or ttyGB0). |
170 | 188 | ||
189 | 2.6. M105 Undocumented USB Requests | ||
190 | ------------------------------ | ||
191 | |||
192 | The Gigaset M105 USB data box understands a couple of useful, but | ||
193 | undocumented USB commands. These requests are not used in normal | ||
194 | operation (for wireless access to the base), but are needed for access | ||
195 | to the M105's own configuration mode (registration to the base, baudrate | ||
196 | and line format settings, device status queries) via the gigacontr | ||
197 | utility. Their use is disabled in the driver by default for safety | ||
198 | reasons but can be enabled by setting the kernel configuration option | ||
199 | "Support for undocumented USB requests" (GIGASET_UNDOCREQ) to "Y" and | ||
200 | recompiling. | ||
201 | |||
171 | 202 | ||
172 | 3. Troubleshooting | 203 | 3. Troubleshooting |
173 | --------------- | 204 | --------------- |