Tilman Schmidt

Hi guys, so finally I couldn't resist looking into this a bit more. Am 19.08.2019 um 10:30 schrieb Paul Bolle: Jul 26 09:00:02 servi kernel: [41511.530376] bas_gigaset 1-1.5:1.0: timeout waiting for HD_READY_SEND_ATDATA This seems to be the root problem. You see, the Gigaset base is supposed to send an HD_READY_SEND_ATDATA message whenever it is ready to receive a command, and the driver is not supposed to send a command as long as it hasn't received that message. However the Gigaset documentation...

Hi Paul, Am 17.09.2019 um 20:28 schrieb Paul Bolle: As far as I know the gigaset driver was written by people unfamiliar with i4l, CAPI, the linux network stack, the linux USB stack, etc. That is correct as far as I am concerned. "Etc." would notably include the serial line discipline interface which is used for connecting the ser_gigaset driver to the serial port framework of the kernel. (I was in fact familiar with the concept of line disciplines from Unix SVR4 but they Linux implementation is...

In my experiments, unplugging and replugging the USB cable to the base helped best. At one point I even tried to find out whether I could simulate that from the driver, but found no way to do so.

I'm afraid I cannot help you. I don't have a Gigaset base anymore, and those "endpoint stalled" errors were always difficult to make sense of even when I encountered them on my own installation, let alone remotely.

frontend/README: added credit

web: update gigacontr manpage to release 0.7.2

release 0.7.2

qgigaset: add a translation