From: "Max S." <max@schneidersoft.net>
To: "Michael Thénault" <michael.thenault@gmail.com>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>, linux-can@vger.kernel.org
Subject: Re: write: No buffer space available
Date: Fri, 08 Mar 2013 10:39:34 +0000 [thread overview]
Message-ID: <1362739174.3296.2.camel@blackbox> (raw)
In-Reply-To: <CACekSAML-BgcW5CWNfns_V0HgqsEFEHXQ06AdLAMupDKefmnFQ@mail.gmail.com>
Hello,
On Fri, 2013-03-08 at 11:24 +0100, Michael Thénault wrote:
> Hello,
>
> Indeed after connecting the arm board to a termination, I'm able to
> see traffic with the oscilloscope.
> I noticed that after sending only one frame with cansend, I see
> traffic all the time with the oscilloscope. I guess that the reason is
> the lack of ACK frames coming from other nodes, which causes re-sends.
Yes. If there is no other node to ack the frame, the can controller will
resend the frame continuously. unless, i think, if you set it up to use
oneshot mode.
M.S.
prev parent reply other threads:[~2013-03-08 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 9:55 write: No buffer space available Michael Thénault
2013-03-07 16:36 ` Oliver Hartkopp
2013-03-08 10:24 ` Michael Thénault
2013-03-08 10:39 ` Max S. [this message]
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=1362739174.3296.2.camel@blackbox \
--to=max@schneidersoft.net \
--cc=linux-can@vger.kernel.org \
--cc=michael.thenault@gmail.com \
--cc=socketcan@hartkopp.net \
/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).