summaryrefslogtreecommitdiffstats
path: root/drivers/net
diff options
context:
space:
mode:
authorAhmad Fatoum <ahmad@a3f.at>2019-09-20 09:58:13 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2019-10-14 12:52:11 +0200
commita805a3cab4e3ef5b8673dd4e4a2fe2f7480a960d (patch)
tree36f41478c3cec0f7bf90d58ee13a377c46223a3f /drivers/net
parent55397b9ebe3a21a3aeb6a98131c0991bff0f7123 (diff)
downloadbarebox-a805a3cab4e3ef5b8673dd4e4a2fe2f7480a960d.tar.gz
barebox-a805a3cab4e3ef5b8673dd4e4a2fe2f7480a960d.tar.xz
USB: gadget: ACM: don't announce V.25ter support
barebox currently announces support for ITU V.25ter AT commands, but doesn't handle them specially when they arrive. Instead they are passed as is to the sole barebox input console, where it may interfere with valid user input. This is especially annoying as ModemManager probes ttyACM devices that announce their AT command support. So even when not using the ttyACM device at all, the other UART ports are affected. Fix this by ceasing to announce USB_CDC_ACM_PROTO_AT_V25TER as function protocol. After applying this patch, I can't see any spurious AT or ~x~ symbols on the console anymore. Cc: <bst@pengutronix.de> Cc: <jlu@pengutronix.de> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions