From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Alex Layton <alex@layton.in>, linux-can <linux-can@vger.kernel.org>
Subject: Re: can-j1939 API
Date: Mon, 02 Nov 2015 14:18:25 +0100 [thread overview]
Message-ID: <563762A1.7020601@hartkopp.net> (raw)
In-Reply-To: <20151102122913.GA25072@airbook.eia.lan>
On 02.11.2015 13:29, Kurt Van Dijck wrote:
>> From: Oliver Hartkopp <socketcan@hartkopp.net>
>> To: Alex Layton <alex@layton.in>, linux-can <linux-can@vger.kernel.org>,
>>> 'per socket' is a bit dubious. In contrast to Alex, I would not restrict
>>> a specific SA or Name to a single socket for reasons I gave earlier.
>>
>> If I understand you correctly the first socket which is giving his address
>> information enables the j1939 address (claiming) handling inside the Kernel,
>> right?
>
> That's the plan.
> I would keep the address claiming itself as today in userspace.
Oh - but what is net/can/j1939/address-claim.c then?
Did it become obsolete?
>> Btw. is it possible to create two processes on the same Linux box which
>> implement two different j1939 nodes (e.g. engine and trailer) that can
>> communicate with each other both using the *same* CAN interface (can0 or
>> vcan0)??
>
> Yes.
> This kind of transparency was one of my goals.
Great.
Regards,
Oliver
next prev parent reply other threads:[~2015-11-02 13:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <linux-can/can-utils/pull/7@github.com>
2015-09-28 6:53 ` [can-utils] J1939 v6 (#7) Marc Kleine-Budde
2015-09-29 12:15 ` Kurt Van Dijck
2015-09-30 15:26 ` Aaron Clarke
2015-09-30 23:38 ` Kurt Van Dijck
[not found] ` <linux-can/can-utils/pull/7/c144149208@github.com>
2015-09-29 18:46 ` Marc Kleine-Budde
2015-09-29 19:49 ` can-j1939 API Kurt Van Dijck
2015-09-29 20:10 ` Austin Schuh
2015-10-15 22:04 ` Alex Layton
2015-10-16 19:36 ` Patrick Menschel
2015-10-18 2:42 ` Kurt Van Dijck
2015-10-19 3:41 ` Patrick Menschel
2015-10-19 6:07 ` Oliver Hartkopp
2015-10-19 9:52 ` Kurt Van Dijck
2015-10-19 16:53 ` Alex Layton
2015-10-19 20:57 ` Kurt Van Dijck
2015-10-19 21:31 ` Kurt Van Dijck
2015-10-22 16:39 ` Alex Layton
2015-10-18 2:32 ` Kurt Van Dijck
2015-10-19 16:53 ` Alex Layton
2015-10-19 20:44 ` Kurt Van Dijck
2015-10-22 16:39 ` Alex Layton
2015-10-23 11:14 ` Kurt Van Dijck
2015-10-29 19:33 ` Oliver Hartkopp
2015-10-29 23:38 ` Kurt Van Dijck
2015-11-02 12:14 ` Oliver Hartkopp
2015-11-02 12:29 ` Kurt Van Dijck
2015-11-02 13:18 ` Oliver Hartkopp [this message]
2015-11-11 19:48 ` Kurt Van Dijck
2015-11-10 21:58 ` Yang
2015-11-11 18:49 ` Kurt Van Dijck
2015-11-17 6:01 ` Yang Wang
2015-11-17 8:43 ` Kurt Van Dijck
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=563762A1.7020601@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=alex@layton.in \
--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).