[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1300964201.3295.16.camel@localhost>
Date: Thu, 24 Mar 2011 11:56:41 +0100
From: Jan Altenberg <jan@...utronix.de>
To: Bhupesh SHARMA <bhupesh.sharma@...com>
Cc: "wg@...ndegger.com" <wg@...ndegger.com>,
"kurt.van.dijck@....be" <kurt.van.dijck@....be>,
"b.spranger@...utronix.de" <b.spranger@...utronix.de>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
jan@...utronix.de
Subject: RE: c_can: TX handling
Hi,
> Thanks for your work on c_can.
> This week has been very busy for me, so please excuse me for the late reply.
No problem.
> Just to better understand this can you send me your *candump* output
> when you see that the message object put earlier in the message RAM
> being pending on the line.
>
> Your point seems valid but I want to make sure that this is not done by the
> C_CAN core implicitly..
I'll try to prepare a (stripped down) test-case, but since I'm quite
busy at the moment, that might take a couple of days.
I'm quite sure, I've seen such a situation, but first of all, I'd like
to sort out, if that was related to the "DA mode".
Cheers,
Jan
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists