From: Oliver Hartkopp <socketcan@hartkopp.net>
To: pfifre.ext@orange.com,
Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>,
laurent vaudoit <laurent.vaudoit@gmail.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: J1939 message length
Date: Thu, 21 May 2015 22:22:04 +0200 [thread overview]
Message-ID: <555E3E6C.2020407@hartkopp.net> (raw)
In-Reply-To: <15657_1432221395_555DF6D3_15657_7688_1_F1366246CF364C42B98553900CE0C5CB08028C85@PEXCVZYM11.corporate.adroot.infra.ftgroup>
On 05/21/2015 05:16 PM, pfifre.ext@orange.com wrote:
> Hi All,
>
> My j1939 works fine! Thanks a lot.
>
> Now, I need to implement diagnostic ISOTP protocol on the same link.
> I tried isotpsend tool to make a simple test first but this tool told me that the protocol is not supported.
> Does it mean that I need to select in the kernel?
>
> I looked for isotp.c in the kernel (net/can/isotp.c) but nothing like here.
>
> Do you know if I need to upgrade the kernel or add user mode modules?
Hi Pascal,
the ISOTP stuff is currently outside the mainline tree too.
There are some minor things to clarify for the blocking of big PDU chunks in
the socket interface.
Btw. you can clone the isotp development repository from here:
https://github.com/hartkopp/can-isotp-modules
git clone https://github.com/hartkopp/can-isotp-modules.git
Then do
cd can-isotp-modules/net/can
./make_isotp.sh
which should create a can-isotp.ko module file you can load into your kernel:
insmod ./can-isotp.ko
That should make it :-)
Please read the README.isotp file from
https://github.com/hartkopp/can-isotp-modules
especially for the tx-queue-len configuration for you CAN netdevice.
Regards,
Oliver
next prev parent reply other threads:[~2015-05-21 20:22 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 10:44 J1939 message length pascal
2014-12-12 11:07 ` Kurt Van Dijck
2014-12-15 8:58 ` pfifre.ext
2014-12-15 9:31 ` Kurt Van Dijck
2014-12-15 9:37 ` pfifre.ext
2015-01-16 13:31 ` Laurent Vaudoit
2015-01-19 9:13 ` Kurt Van Dijck
2015-04-27 9:22 ` pfifre.ext
2015-05-19 8:46 ` Kurt Van Dijck
2015-05-19 13:27 ` pfifre.ext
[not found] ` <CAA7hF3y7+j_TZ4nTak8t5Y4ejmE2fOFWxRBKJbrHLiFts_+8eg@mail.gmail.com>
2015-05-19 21:01 ` Kurt Van Dijck
2015-05-20 6:27 ` pfifre.ext
2015-05-21 15:16 ` pfifre.ext
2015-05-21 20:22 ` Oliver Hartkopp [this message]
2015-05-22 6:08 ` pfifre.ext
2015-05-19 13:55 ` pfifre.ext
2015-09-04 12:24 ` pfifre.ext
2015-09-07 0:40 ` J1939 + iMX6 + yocto Kurt Van Dijck
2015-09-07 6:31 ` pfifre.ext
2015-09-08 7:58 ` Kurt Van Dijck
2015-09-08 9:33 ` pfifre.ext
2015-09-08 12:32 ` Kurt Van Dijck
2015-09-08 12:45 ` pfifre.ext
2015-09-18 9:04 ` pfifre.ext
2015-09-18 12:10 ` Kurt Van Dijck
2015-09-18 12:29 ` pfifre.ext
2015-09-19 6:34 ` Kurt Van Dijck
2015-09-21 7:27 ` pfifre.ext
2015-09-10 9:56 ` pfifre.ext
2015-09-10 11:34 ` Kurt Van Dijck
2015-09-10 13:18 ` pfifre.ext
2015-09-10 13:30 ` Marc Kleine-Budde
2015-09-10 15:32 ` pfifre.ext
2015-09-11 3:49 ` Kurt Van Dijck
2015-09-11 6:46 ` pfifre.ext
2015-09-11 9:48 ` Kurt Van Dijck
2015-09-11 9:53 ` pfifre.ext
2015-09-15 6:54 ` pfifre.ext
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=555E3E6C.2020407@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=laurent.vaudoit@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=pfifre.ext@orange.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