From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "Ira W. Snyder" <iws@ovro.caltech.edu>,
Kurt Van Dijck <kurt.van.dijck@eia.be>,
Wolfgang Grandegger <wg@grandegger.com>,
linux-can@vger.kernel.org
Subject: Re: Questions about janz-ican3 and CAN_RAW_RECV_OWN_MSGS
Date: Tue, 10 Jul 2012 21:01:11 +0200 [thread overview]
Message-ID: <4FFC7BF7.9070709@hartkopp.net> (raw)
In-Reply-To: <4FFC01FF.3030801@pengutronix.de>
On 10.07.2012 12:20, Marc Kleine-Budde wrote:
> On 07/04/2012 06:23 PM, Oliver Hartkopp wrote:
>> Anyway we currently have the flexcan and the ican3 hardware that generally
>> supports a loopback on hardware level but looses the reference to the tx-skb
>> and therefore to the sk pointer which is used to identify the originating
>> socket for recv-own-msgs support.
>
> For the record:
> Since v3.4-rc1 flexcan implements proper loopback. (The flexcan driver
> has been added before recv-own-msgs support has been implemented, so it
> didn't make any difference back then.)
>
Yes. I did not want to state that the driver does not have a proper solution.
The point is that the flexcan driver has a hardware loopback (like the ican3)
but due to the lack of references in the CAN frame registers the (generally
nice) functionality cannot be used for us. sigh.
Regards,
Oliver
next prev parent reply other threads:[~2012-07-10 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 23:23 Questions about janz-ican3 and CAN_RAW_RECV_OWN_MSGS Ira W. Snyder
2012-07-04 9:18 ` Wolfgang Grandegger
2012-07-04 12:07 ` Kurt Van Dijck
2012-07-04 16:23 ` Oliver Hartkopp
2012-07-04 19:07 ` Ira W. Snyder
2012-07-05 9:48 ` Oliver Hartkopp
2012-07-10 10:20 ` Marc Kleine-Budde
2012-07-10 19:01 ` Oliver Hartkopp [this message]
2012-07-04 16:34 ` Ira W. Snyder
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=4FFC7BF7.9070709@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=iws@ovro.caltech.edu \
--cc=kurt.van.dijck@eia.be \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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).