]> rtime.felk.cvut.cz Git - socketcan-devel.git/commit
As Stephen Hellriegel pointed out in
authorhartkopp <hartkopp@030b6a49-0b11-0410-94ab-b0dab22257f2>
Fri, 16 Apr 2010 19:03:14 +0000 (19:03 +0000)
committerhartkopp <hartkopp@030b6a49-0b11-0410-94ab-b0dab22257f2>
Fri, 16 Apr 2010 19:03:14 +0000 (19:03 +0000)
commit2d59ba8eb3d5c7e2059de336a88caa9233f10be2
treeebb83ddb8302277bada5fb8074f1bfb323deb129
parent4790ed43f144c747f2c218f87b0bfbd84dac8c30
As Stephen Hellriegel pointed out in
https://lists.berlios.de/pipermail/socketcan-users/2010-April/001378.html
it does not make sense to monitor the tx data flow in the slcan driver as
we do not know anything about the CAN specific problems that may occur in the
slcan device.

Therefore we just wait until the ASCII data is sent on the serial line without
having a separate timeout handler in the slcan driver.

git-svn-id: svn://svn.berlios.de//socketcan/trunk@1168 030b6a49-0b11-0410-94ab-b0dab22257f2
kernel/2.6/drivers/net/can/slcan.c