From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marek Vasut <marex@denx.de>, Mirza Krak <mirza.krak@hostmobility.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Wolfgang Grandegger <wg@grandegger.com>
Subject: Re: [RFC] K-Line protocol via SocketCAN
Date: Wed, 15 Jun 2016 08:57:49 +0200 [thread overview]
Message-ID: <5760FC6D.9030300@hartkopp.net> (raw)
In-Reply-To: <5760CEC2.2050701@denx.de>
On 06/15/2016 05:42 AM, Marek Vasut wrote:
> On 06/14/2016 08:10 AM, Oliver Hartkopp wrote:
>>
>>>> On 06/11/2016 09:42 PM, Marek Vasut wrote:
>>>>> Well, I was talking about arinc 429 .
>>>>>
>>>>
>>>> Ah - I remember that discussion:
>>>> https://lwn.net/Articles/663130/
>>>> http://thread.gmane.org/gmane.linux.network/385449
>>>>
>>>> What happed to it?
>>>
>>> Priorities shifted. I still hope to return to it and get it into
>>> mainline proper. Since I did some digging in the socketcan recently,
>>> I have a better understanding of it now too. I believe the agreement
>>> there was to put it into the socketcan stack as an extension, does it
>>> still make sense ?
>>>
>>
>> There were intensive discussions about the original patchset and I think
>> the copy&paste hell from the PF_CAN won't make it.
>
> Yeah, that's pretty clear to me. But does it make sense to extend
> socketcan with that arinc429 stuff instead then ?
You might think into the direction of the SLLIN implementation:
Create a ldisc which smells like a CAN interface.
SLLIN doesn't change SocketCAN either.
Regards,
Oliver
next prev parent reply other threads:[~2016-06-15 6:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 23:15 [RFC] K-Line protocol via SocketCAN Marek Vasut
2016-05-20 6:04 ` Mirza Krak
2016-05-20 6:28 ` Oliver Hartkopp
2016-05-20 11:59 ` Marek Vasut
2016-05-22 20:27 ` Patrick Menschel
2016-05-22 21:11 ` Marek Vasut
2016-06-01 2:26 ` Marek Vasut
2016-06-05 12:07 ` Oliver Hartkopp
2016-06-09 15:00 ` Marek Vasut
2016-06-09 18:29 ` Oliver Hartkopp
2016-06-09 19:21 ` Marek Vasut
2016-06-09 20:12 ` Oliver Hartkopp
2016-06-11 19:42 ` Marek Vasut
2016-06-12 19:28 ` Oliver Hartkopp
2016-06-13 22:07 ` Marek Vasut
2016-06-14 6:10 ` Oliver Hartkopp
2016-06-15 3:42 ` Marek Vasut
2016-06-15 6:57 ` Oliver Hartkopp [this message]
2016-06-15 11:05 ` Marek Vasut
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=5760FC6D.9030300@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=marex@denx.de \
--cc=mirza.krak@hostmobility.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.