Thread (36 messages) 36 messages, 8 authors, 2012-11-16

Re: What are you doing if the TX buffer overflows?

From: Kurt Van Dijck <hidden>
Date: 2012-11-16 15:13:22

On Thu, Nov 15, 2012 at 06:12:06PM +0100, Oliver Hartkopp wrote:
On 15.11.2012 13:54, Marc Kleine-Budde wrote:
quoted
On 11/14/2012 09:48 PM, Jason White wrote:

Officially the TX-timeout has been removed as the controller just sends out
the CAN frames, when it comes back to life ...

The question is, if the controller gets into the BUS_OFF state and if the
restart-ms option (see ip tool) would help here.
FYI:
A CAN chip that sits alone on a proper bus, trying to transmit a frame,
will never go into BUS_OFF. It can only go in BUS_OFF when a bad network
is encountered, i.e. the chip does not see it's TX activity on its RX.

I think this scenario (chip alone, going in BUS_OFF) is no different
than regular BUS_OFF, and should be treated likewise.
Regards,
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-can" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help