From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Felix Obenhuber <felix@obenhuber.de>
Cc: linux-can@vger.kernel.org
Subject: Re: loopback/recv own messages option not working as expected with plx_pci (Adlink Technology PCI-7841)
Date: Thu, 12 Jan 2012 17:57:45 +0100 [thread overview]
Message-ID: <4F0F1109.6090300@hartkopp.net> (raw)
In-Reply-To: <CAJsOQGNE959CjAJUCQzxqh_zyrLj-Ed=-RDYBvJq9OrtScMkKw@mail.gmail.com>
Hi Felix,
On 12.01.2012 14:53, Felix Obenhuber wrote:
> I just encountered a problem with the loopback and receive own
> messages option in combination with the plx_pci driver serving a
> Adlink PCI-7841. It driver behaves a the CAN_RAW_RECV_OWN_MSGS and
> LOOPBACK option would have been set (and they aren't).
>
> One box with the Adlink card connected to another host with a approved
> and well initialized CAN card. Sending single frames from each hosts
> works fine. When I start the canecho test from trunk/test and send a
> frame on the bus (from the other node) its duplicated each time
> canecho reads/writes the frame. You would get the same result if you
> set the CAN_RAW_RECV_OWN_MSGS and LOOPBACK option on the socket in the
> canecho test.
> I have the same behavior with a tool written by me and tested with the
> latest trunk revision - same result.
> Running canecho on a vcan or peak usb device works as expected.
Both vcan & the PEAK driver use a fallback solution for that - so it is not a
real statement when they work.
>
> Has someone seen something similar with that driver? I'd just like to
> ask before digging into it.
No - i assume you are using a 2.6.30.x (0 <= x < 5) kernel, right?
See
http://old.nabble.com/Local-loopback-broken--td24108048.html
Regards,
Oliver
next prev parent reply other threads:[~2012-01-12 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 13:53 loopback/recv own messages option not working as expected with plx_pci (Adlink Technology PCI-7841) Felix Obenhuber
2012-01-12 16:57 ` Oliver Hartkopp [this message]
2012-01-13 8:06 ` Felix Obenhuber
2012-01-13 10:30 ` Felix Obenhuber
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=4F0F1109.6090300@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=felix@obenhuber.de \
--cc=linux-can@vger.kernel.org \
/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).