From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Informations About CAN API of the Linux Kernel
Date: Mon, 11 Mar 2013 11:03:46 +0100 [thread overview]
Message-ID: <513DAC02.6080905@hartkopp.net> (raw)
In-Reply-To: <20130311093123.GB5114@vandijck-laurijssen.be>
On 11.03.2013 10:31, Kurt Van Dijck wrote:
> On Fri, Mar 08, 2013 at 02:27:18PM +0100, Yegor Yefremov wrote:
>> On Fri, Mar 8, 2013 at 1:04 PM, Oliver Hartkopp
>> <oliver.hartkopp@volkswagen.de> wrote:
>>> Am 08.03.2013 11:05, schrieb Kurt Van Dijck:
>>>
>>>
>>
>> What about creating a small k1939 howto here http://elinux.org/CAN_Bus
>> Then we could at least try G+ channel to get attention. There are many
>> automation engineers.
>
> Your suggestion makes sense regardless of the outcome of the Kconfig discussion.
>
Yes. Great idea.
Especially as all the announcements about the support of
- Android
- CAN utils
- Python
- CAN FD
- J1939
- ISO15765-2 (w CAN FD too)
- CAN Gateways
- etc
get lost on the mailing list ...
It's hard to check the ML archives so i really would appreciate to have a
general overview about SocketCAN and it's dedicated projects.
http://elinux.org/CAN_Bus looks to be a good place for that.
If it's ok for the other guys here on the ML how can i contribute to the wiki?
Just create an account and go for it?
Best regards,
Oliver
next prev parent reply other threads:[~2013-03-11 10:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2B7D120CFC15DC438D721B998AD9D9E9097105AB@SEGOTNC5180-N2.vcn.ds.volvo.net>
2013-03-06 15:42 ` Informations About CAN API of the Linux Kernel Marc Kleine-Budde
2013-03-06 16:03 ` Sako Youssouf
2013-03-06 16:18 ` Marc Kleine-Budde
2013-03-06 16:25 ` Sako Youssouf
2013-03-06 16:36 ` Marc Kleine-Budde
2013-03-06 16:41 ` Sako Youssouf
2013-03-07 12:40 ` Kurt Van Dijck
2013-03-08 8:55 ` Marc Kleine-Budde
2013-03-08 10:05 ` Kurt Van Dijck
2013-03-08 12:04 ` Oliver Hartkopp
2013-03-08 13:07 ` Kurt Van Dijck
2013-03-08 13:31 ` Kurt Van Dijck
2013-03-08 13:27 ` Yegor Yefremov
2013-03-11 9:31 ` Kurt Van Dijck
2013-03-11 10:03 ` Oliver Hartkopp [this message]
2013-03-11 10:21 ` Yegor Yefremov
2013-03-13 14:57 ` Kurt Van Dijck
2013-03-14 8:04 ` Heinz-Jürgen Oertel
2013-03-14 8:28 ` Wolfgang Grandegger
2013-03-14 8:41 ` Heinz-Jürgen Oertel
2013-03-14 10:34 ` Heinz-Jürgen Oertel
2013-03-14 11:00 ` Kurt Van Dijck
2013-03-14 12:25 ` Yegor Yefremov
2013-03-14 12:31 ` Heinz-Jürgen Oertel
2013-03-16 9:48 ` Heinz-Jürgen Oertel
2013-03-08 12:51 ` Robert Schwebel
2013-03-11 9:29 ` Kurt Van Dijck
2013-03-11 15:10 ` Marc Kleine-Budde
2013-03-11 15:34 ` Kurt Van Dijck
2013-03-11 16:00 ` Marc Kleine-Budde
2013-03-11 17:20 ` Oliver Hartkopp
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=513DAC02.6080905@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=yegorslists@googlemail.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.