diff options
author | Tilman Schmidt <tilman@imap.cc> | 2009-05-13 08:44:18 -0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2009-05-17 23:51:27 -0400 |
commit | b88bd95655c7bc059606529e01467594978d7b72 (patch) | |
tree | f5669760db7d97186d1c59b5bcf2b57f1bca5b56 /Documentation/isdn/README.gigaset | |
parent | 5a1888ea994bf6b28179255a376e83dfa53c81c5 (diff) |
gigaset: remove UNDOCREQ config option
Drop the kernel config option GIGASET_UNDOCREQ, permanently
activating the code it controlled, as there have been no reports
of problems caused by its activation but many problems caused by
it being disabled.
Also fix a few bad comments while we're at it.
Impact: cleanup
Signed-off-by: Tilman Schmidt <tilman@imap.cc>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/isdn/README.gigaset')
-rw-r--r-- | Documentation/isdn/README.gigaset | 33 |
1 files changed, 5 insertions, 28 deletions
diff --git a/Documentation/isdn/README.gigaset b/Documentation/isdn/README.gigaset index f6e9eaa75967..f9963103ae3d 100644 --- a/Documentation/isdn/README.gigaset +++ b/Documentation/isdn/README.gigaset | |||
@@ -149,10 +149,8 @@ GigaSet 307x Device Driver | |||
149 | configuration files and chat scripts in the gigaset-VERSION/ppp directory | 149 | configuration files and chat scripts in the gigaset-VERSION/ppp directory |
150 | in the driver packages from http://sourceforge.net/projects/gigaset307x/. | 150 | in the driver packages from http://sourceforge.net/projects/gigaset307x/. |
151 | Please note that the USB drivers are not able to change the state of the | 151 | Please note that the USB drivers are not able to change the state of the |
152 | control lines (the M105 driver can be configured to use some undocumented | 152 | control lines. This means you must use "Stupid Mode" if you are using |
153 | control requests, if you really need the control lines, though). This means | 153 | wvdial or you should use the nocrtscts option of pppd. |
154 | you must use "Stupid Mode" if you are using wvdial or you should use the | ||
155 | nocrtscts option of pppd. | ||
156 | You must also assure that the ppp_async module is loaded with the parameter | 154 | You must also assure that the ppp_async module is loaded with the parameter |
157 | flag_time=0. You can do this e.g. by adding a line like | 155 | flag_time=0. You can do this e.g. by adding a line like |
158 | 156 | ||
@@ -190,20 +188,7 @@ GigaSet 307x Device Driver | |||
190 | You can also use /sys/class/tty/ttyGxy/cidmode for changing the CID mode | 188 | You can also use /sys/class/tty/ttyGxy/cidmode for changing the CID mode |
191 | setting (ttyGxy is ttyGU0 or ttyGB0). | 189 | setting (ttyGxy is ttyGU0 or ttyGB0). |
192 | 190 | ||
193 | 2.6. M105 Undocumented USB Requests | 191 | 2.6. Unregistered Wireless Devices (M101/M105) |
194 | ------------------------------ | ||
195 | The Gigaset M105 USB data box understands a couple of useful, but | ||
196 | undocumented USB commands. These requests are not used in normal | ||
197 | operation (for wireless access to the base), but are needed for access | ||
198 | to the M105's own configuration mode (registration to the base, baudrate | ||
199 | and line format settings, device status queries) via the gigacontr | ||
200 | utility. Their use is controlled by the kernel configuration option | ||
201 | "Support for undocumented USB requests" (CONFIG_GIGASET_UNDOCREQ). If you | ||
202 | encounter error code -ENOTTY when trying to use some features of the | ||
203 | M105, try setting that option to "y" via 'make {x,menu}config' and | ||
204 | recompiling the driver. | ||
205 | |||
206 | 2.7. Unregistered Wireless Devices (M101/M105) | ||
207 | ----------------------------------------- | 192 | ----------------------------------------- |
208 | The main purpose of the ser_gigaset and usb_gigaset drivers is to allow | 193 | The main purpose of the ser_gigaset and usb_gigaset drivers is to allow |
209 | the M101 and M105 wireless devices to be used as ISDN devices for ISDN | 194 | the M101 and M105 wireless devices to be used as ISDN devices for ISDN |
@@ -215,8 +200,7 @@ GigaSet 307x Device Driver | |||
215 | driver. In that situation, a restricted set of functions is available | 200 | driver. In that situation, a restricted set of functions is available |
216 | which includes, in particular, those necessary for registering the device | 201 | which includes, in particular, those necessary for registering the device |
217 | to a base or for switching it between Fixed Part and Portable Part | 202 | to a base or for switching it between Fixed Part and Portable Part |
218 | modes. For the M105, these commands require the "Support for undocumented | 203 | modes. |
219 | USB requests" configuration option (see section 2.6.) to be enabled. | ||
220 | 204 | ||
221 | 3. Troubleshooting | 205 | 3. Troubleshooting |
222 | --------------- | 206 | --------------- |
@@ -247,19 +231,12 @@ GigaSet 307x Device Driver | |||
247 | Select Unimodem mode for all DECT data adapters. (see section 2.4.) | 231 | Select Unimodem mode for all DECT data adapters. (see section 2.4.) |
248 | 232 | ||
249 | Problem: | 233 | Problem: |
250 | You want to configure your USB DECT data adapter (M105) but gigacontr | ||
251 | reports an error: "/dev/ttyGU0: Inappropriate ioctl for device". | ||
252 | Solution: | ||
253 | Recompile the usb_gigaset driver with the kernel configuration option | ||
254 | CONFIG_GIGASET_UNDOCREQ set to 'y'. (see section 2.6.) | ||
255 | |||
256 | Problem: | ||
257 | Messages like this: | 234 | Messages like this: |
258 | usb_gigaset 3-2:1.0: Could not initialize the device. | 235 | usb_gigaset 3-2:1.0: Could not initialize the device. |
259 | appear in your syslog. | 236 | appear in your syslog. |
260 | Solution: | 237 | Solution: |
261 | Check whether your M10x wireless device is correctly registered to the | 238 | Check whether your M10x wireless device is correctly registered to the |
262 | Gigaset base. (see section 2.7.) | 239 | Gigaset base. (see section 2.6.) |
263 | 240 | ||
264 | 3.2. Telling the driver to provide more information | 241 | 3.2. Telling the driver to provide more information |
265 | ---------------------------------------------- | 242 | ---------------------------------------------- |