All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Mirza Krak <mirza.krak@hostmobility.com>, Marek Vasut <marex@denx.de>
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: Fri, 20 May 2016 08:28:45 +0200	[thread overview]
Message-ID: <573EAE9D.20006@hartkopp.net> (raw)
In-Reply-To: <CAJ=nTsu_bJgj1A5JNJNAd9HAao5493CnofbQpJ_qftYOiCgaYw@mail.gmail.com>

Hi,

I removed Dave Miller from the discussion not to be tagged as SPAM :-)
That's not Daves focus as networking maintainer ...

Here's an update about the LIN Status from Pavel Pisa:

http://marc.info/?l=linux-can&m=146163127517268&w=2

I remember a K-Line implementation for Linux where we had a MPC5200 UART 
which we programmed with bit-banging of some control line to do the 
5bit/s opening pattern.
After that we went to 10400 bit/s and did some K-Line communication.
All this was done by a user space application on /dev/ttyS0.

What would be the advantages to put this into kernel space (or into the 
CAN networking infrastructure)?

Regards,
Oliver


On 05/20/2016 08:04 AM, Mirza Krak wrote:
> 2016-05-20 1:15 GMT+02:00 Marek Vasut <marex@denx.de>:
>> I will also need to add support for the LIN protocol and SENT protocol
>> further down the line. I will also likely revisit the Arinc at some
>> point afterward. So I would like to know how to deal with this protocol
>> mess.
>
> FYI, there has been a similar LIN project for quite a while [1]. You
> might have seen it earlier?
>
> [1]. http://rtime.felk.cvut.cz/gitweb/linux-lin.git
>

  reply	other threads:[~2016-05-20  6:28 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 [this message]
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
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=573EAE9D.20006@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.