From: Armin Burchardt <armin@uni-bremen.de>
To: Mike Purvis <mpurvis@clearpathrobotics.com>, linux-can@vger.kernel.org
Subject: Re: Standard CAN over IP
Date: Wed, 04 Feb 2015 21:44:36 +0100 [thread overview]
Message-ID: <54D284B4.5050501@uni-bremen.de> (raw)
In-Reply-To: <CACsJT9Nxv2Vuq92nnOw4eN6j-RycpqGRErsjp5R_LiMwdS13aQ@mail.gmail.com>
Hi Mike,
On 04.02.2015 21:27, Mike Purvis wrote:
> system as a socketcan can0 device. Is there some standard component
> which already does this, or at least some tooling around serializing
> CAN messages to a bytestream?
there is slcand (UART to socketcan from the can-utils package) to use
serial CAN adapters with socketcan. Implementing the (line based)
protocol in the mcu should not be too hard.
Armin (switching back to read-only mode)
next prev parent reply other threads:[~2015-02-04 21:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 20:27 Standard CAN over IP Mike Purvis
2015-02-04 20:44 ` Armin Burchardt [this message]
2015-02-04 21:38 ` Mike Purvis
2015-02-04 22:42 ` Gerhard Bertelsmann
2015-02-05 0:50 ` Tom Evans
2015-02-05 13:15 ` Mike Purvis
2015-02-06 8:33 ` Michal Sojka
2015-02-09 16:00 ` Mike Purvis
2015-02-09 18:32 ` Oliver Hartkopp
2015-02-04 23:43 ` Tom Evans
2015-02-18 17:57 ` Maximilian Güntner
[not found] ` <CACsJT9M4QbYkDvQkGfhFuwA6haNyV5zesUFtLzB5VEbxP=obBA@mail.gmail.com>
2015-02-19 3:21 ` Mike Purvis
2015-02-19 14:58 ` Maximilian Güntner
2015-02-20 11:43 ` Oliver Hartkopp
2015-02-23 12:25 ` Maximilian Güntner
2015-02-23 13:08 ` Oliver Hartkopp
2015-02-23 14:27 ` Maximilian Güntner
2015-02-23 16:22 ` Oliver Hartkopp
2015-03-20 16:54 ` Maximilian Güntner
2015-03-23 10:28 ` Pankajkumar Misra (RBEI/EEA2)
2015-03-23 13:15 ` Maximilian Güntner
2015-03-23 16:57 ` Pankajkumar Misra (RBEI/EEA2)
2015-03-23 13:23 ` GARNERO, PIERRE (P.)
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=54D284B4.5050501@uni-bremen.de \
--to=armin@uni-bremen.de \
--cc=linux-can@vger.kernel.org \
--cc=mpurvis@clearpathrobotics.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.