From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Tom Evans <tom_usenet@optusnet.com.au>, linux-can@vger.kernel.org
Subject: Re: [PATCH v5 0/5] Consolidate and unify state change handling
Date: Fri, 19 Dec 2014 10:33:51 +0100 [thread overview]
Message-ID: <5493F0FF.7070101@hartkopp.net> (raw)
In-Reply-To: <loom.20141219T004928-872@post.gmane.org>
On 19.12.2014 01:05, Tom Evans wrote:
>>
>> https://gitorious.org/linux-can/can-utils/
> ...
>
> What is the relationship (if any) between this "can-utils" package and the
> "canutils" (latest update June 2010) that we're using from here?
>
> http://www.pengutronix.de/software/socket-can/download/canutils/v4.0/
>
> I note some common authorship (Marc Kleine-Budde).
>
> Both have cansend and candump utils, but the Pengutronics one also has
> "conconfig" which we rely on.
This has some historical reasons - of course ;-)
The can-utils that are now on gitorious.org (former berlios.de) are originally
from Volkswagen Group Research.
And Pengutronix started their toolset based on the requirements to be able to
ship it with OSELAS/ptxdist based board support packages.
IIRC Pengutronix provided the canconfig they needed even before the netlink
configuration (with iproute2) was available.
To build your own CAN interface configuration tools canconfig and the
libsocketcan from Pengutronix are a good way to start.
http://git.pengutronix.de/?p=tools/canutils.git
http://git.pengutronix.de/?p=tools/libsocketcan.git
From the 'just user' perspective to send/dump/replay/visualize CAN stuff the
gitorious can-utils are recommended and provide more functionalities.
That's why there is a Debian package can-utils. To be able to make it a Debian
package and to support the autotools Marc e.g. provided the needed autotools
infrastructure in can-utils.
Regards,
Oliver
ps. to configure my CAN interfaces I'm using a can_if script for
Debian/Ubuntu, where you can configure bitrates for the interfaces using the
'ip' tool from iproute2:
https://gitorious.org/linux-can/can-misc/source/etc/can_if
Just put this into /etc/init.d and say
update-rc.d can_if defaults
Documentation is inside the can_if script.
next prev parent reply other threads:[~2014-12-19 9:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 17:54 [PATCH v5 0/5] Consolidate and unify state change handling Andri Yngvason
2014-12-07 19:16 ` Wolfgang Grandegger
2014-12-07 23:35 ` Marc Kleine-Budde
2014-12-08 7:40 ` Wolfgang Grandegger
2014-12-18 6:09 ` Tom Evans
2014-12-18 7:22 ` Oliver Hartkopp
2014-12-18 12:15 ` Andri Yngvason
2014-12-18 13:03 ` Oliver Hartkopp
2014-12-18 13:52 ` Oliver Hartkopp
2014-12-19 0:05 ` Tom Evans
2014-12-19 9:33 ` Oliver Hartkopp [this message]
[not found] ` <3595849.EjdlQbi96i@heinz>
2014-12-18 13:45 ` 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=5493F0FF.7070101@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=tom_usenet@optusnet.com.au \
/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).