From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Stefan <os252@gmx.de>
Cc: linux-can@vger.kernel.org
Subject: Re: Transmitted Data is not to be received by other Application
Date: Thu, 28 Mar 2013 13:21:00 +0100 [thread overview]
Message-ID: <515435AC.2040707@pengutronix.de> (raw)
In-Reply-To: <515433AF.7000203@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On 03/28/2013 01:12 PM, Oliver Stefan wrote:
> I'm developing Software for the Raspberry Pi with MCP2515 extension.
>
> I have two applications running the same time.
> One is in the receiving mode, and the other can transmit and receive.
> Unfortunately the application that is permanently receiving, receives
> the data of the second application too.
>
> How can I turn off this function?
Have you tried this:
4.1.3 RAW socket option CAN_RAW_LOOPBACK
To meet multi user needs the local loopback is enabled by default
(see chapter 3.2 for details). But in some embedded use-cases
(e.g. when only one application uses the CAN bus) this loopback
functionality can be disabled (separately for each socket):
int loopback = 0; /* 0 = disabled, 1 = enabled (default) */
setsockopt(s, SOL_CAN_RAW, CAN_RAW_LOOPBACK, &loopback, sizeof(loopback));
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2013-03-28 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 12:12 Transmitted Data is not to be received by other Application Oliver Stefan
2013-03-28 12:21 ` Marc Kleine-Budde [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=515435AC.2040707@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=os252@gmx.de \
/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).