Am Freitag, 20. Januar 2012, 01:50:02 schrieb Bjørn Mork: > This is preparing for supporting devices using other > protocols than AT commands. Such devices will typically not > echo back the received command. > > Signed-off-by: Bjørn Mork <bjorn@xxxxxxx> > --- > This won't affect existing users. I was wondering how to enable > echo in a sane way. I did not want to that the tty route using > an ioctl... Although that is probably the only possible way > if configuring this is required per client? > > For now it is a static device specific attribute. The assumption > is that QMI devices will have this on to enable monitoring complete > transactions from a read-only process, while AT based devices have > it turned off as they echo back commands themselves This makes me wonder why we want to work around user space's stupidity of not knowing what it sent. However, this seems to be a traditional capability of ttys. And the other major option to configure wireless devices is a pseudo serial interface. That on the gripping hand argues for doing this exactly the way a tty does it, namely by supporting the very ioctl ttys use. Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
