From: Oliver Hartkopp <socketcan@hartkopp.net>
To: laurent vaudoit <laurent.vaudoit@gmail.com>
Cc: maxime@artisandeveloppeur.fr, linux-can@vger.kernel.org
Subject: Re: linux-can ISOTP module
Date: Thu, 13 Nov 2014 18:47:48 +0100 [thread overview]
Message-ID: <5464EEC4.1080009@hartkopp.net> (raw)
In-Reply-To: <CAA7hF3yzM8KZjj+4d8m2rUZaDWPuC2hygYZ6PzFz4jWu1Y8e_A@mail.gmail.com>
Hello Laurent,
On 23.06.2014 20:01, laurent vaudoit wrote:
> On Fri, Jun 20, 2014 at 9:08 PM, Oliver Hartkopp <socketcan@hartkopp.net> wrote:
>> On 06.06.2014 08:42, laurent vaudoit wrote:
>>
>>>>>> With this method, how can i have a segmented transfer like this:
>>>>>> 0x6a7 0x55 0x10 0x08 ........
>>>>>> 0x687 0xAA 0x30 0x00 0x00
>>>>>> 0x6a7 0x55 0x21 .....
>>>>>>
>>>>>> The connection i need is between two ECU, using IDs 0x6a7/687 and one has
>>>>>> adress extension 0x55, the other 0xAA (this adressing method is used on some
>>>>>> FIAT ECUs for example), but i don't see how it can work using two socket.
>>>>> I confirm.
>>>>> This is a problem that we also encountered on a BMW ECU with the current
>>>>> implementation of ISOTP.
>>>>> The use-case is real and not currently supported.
>>
>> I added the funtionality of a different rx_ext_addr to a specific branch of
>> can-utils and can-modules:
>>
>> https://gitorious.org/linux-can/can-utils/commits/rx_ext_addr
>> https://gitorious.org/linux-can/can-modules/commits/rx_ext_addr
>>
>> Please check them out for a test. As all the isotp tools (in the branch)
>> support the new feature too, it should be easy to do.
>
> i did not have time for test but regarding the source code, it should be ok.
Did you find some time to check this change?
I would like to move this patch into the master branch before continuing the
development.
Regards,
Oliver
next prev parent reply other threads:[~2014-11-13 17:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 12:55 linux-can ISOTP module laurent vaudoit
2014-06-04 18:40 ` Oliver Hartkopp
2014-06-05 7:16 ` laurent vaudoit
2014-06-05 10:18 ` Maxime Jayat
2014-06-05 18:22 ` Oliver Hartkopp
2014-06-06 6:42 ` laurent vaudoit
2014-06-20 19:08 ` Oliver Hartkopp
2014-06-23 18:01 ` laurent vaudoit
2014-11-13 17:47 ` Oliver Hartkopp [this message]
[not found] ` <CAA7hF3ypuVbfxbskM+2bn_58a-k0EtCePxQ_1i6j24G5H=zFSQ@mail.gmail.com>
2015-01-16 17:31 ` Oliver Hartkopp
2014-06-21 11:18 ` N_Cs timing - was " Oliver Hartkopp
2014-06-23 18:13 ` laurent vaudoit
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=5464EEC4.1080009@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=laurent.vaudoit@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=maxime@artisandeveloppeur.fr \
/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).