netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Altenberg <jan@linutronix.de>
To: Bhupesh SHARMA <bhupesh.sharma@st.com>
Cc: "wg@grandegger.com" <wg@grandegger.com>,
	"kurt.van.dijck@eia.be" <kurt.van.dijck@eia.be>,
	"b.spranger@linutronix.de" <b.spranger@linutronix.de>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	jan@linutronix.de
Subject: RE: c_can: TX handling
Date: Thu, 24 Mar 2011 11:56:41 +0100	[thread overview]
Message-ID: <1300964201.3295.16.camel@localhost> (raw)
In-Reply-To: <D5ECB3C7A6F99444980976A8C6D896384DF0D6F684@EAPEX1MAIL1.st.com>

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


  reply	other threads:[~2011-03-24 10:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 15:59 can: c_can: TX handling Jan Altenberg
2011-03-23  8:51 ` can: c_can: TX echo Kurt Van Dijck
2011-03-23 13:54   ` Jan Altenberg
2011-03-23 14:25     ` Wolfgang Grandegger
2011-03-23 14:52       ` Jan Altenberg
2011-03-23  8:53 ` can: c_can: TX delivery Kurt Van Dijck
2011-03-23 15:32   ` Jan Altenberg
2011-03-23 15:49     ` Kurt Van Dijck
2011-03-24 10:02     ` Marc Kleine-Budde
2011-03-24  4:18 ` c_can: TX handling Bhupesh SHARMA
2011-03-24 10:56   ` Jan Altenberg [this message]
2011-03-24  5:43 ` Bhupesh SHARMA
2011-03-24 10:38   ` [PATCH] can: c_can: Fix tx_bytes accounting Jan Altenberg
2011-03-24 10:00     ` Wolfgang Grandegger
2011-03-24 11:26       ` [PATCH resend] " Jan Altenberg
2011-03-24 10:49         ` Kurt Van Dijck
     [not found]           ` <20110324104925.GB339-MxZ6Iy/zr/UdbCeoMzGj59i2O/JbrIOy@public.gmane.org>
2011-03-24 11:49             ` Wolfgang Grandegger
     [not found]               ` <4D8B2FAF.5040000-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-03-28  1:24                 ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1300964201.3295.16.camel@localhost \
    --to=jan@linutronix.de \
    --cc=b.spranger@linutronix.de \
    --cc=bhupesh.sharma@st.com \
    --cc=kurt.van.dijck@eia.be \
    --cc=netdev@vger.kernel.org \
    --cc=wg@grandegger.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).