From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Sebastian Haas <dev@sebastianhaas.info>
Cc: Linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: RFC: improve and consolidate state change and bus-off handling
Date: Sat, 03 Dec 2011 17:53:14 +0100 [thread overview]
Message-ID: <4EDA53FA.2090105@hartkopp.net> (raw)
In-Reply-To: <4EDA0DA2.1070206@sebastianhaas.info>
On 03.12.2011 12:53, Sebastian Haas wrote:
> Hello,
>
> Am 03.12.2011 11:18, schrieb Oliver Hartkopp:
>> Hello Sebastian,
>>
>> nice to read that you're back on air ;-)
> I've started to implement a kind of a restbus simulation for Linux and I
> stumbled again over SocketCAN ;-) So I'm back on air.
Fine. When you set up a rest bus simulation probably the can-gw available in
Linux 3.2 and up is valuable for your use case:
http://patchwork.ozlabs.org/patch/112916/
>> E.g. in some vehicle setups an automatic
>> recovery from bus-off after 200ms is specified. If this is done by a 'special'
>> handler or just by the driver can not be seen from the network view.
> I'm not very familiar with the current API, but how do I as an application
> restart recovery manually. I suppose there is ioctl().
No this if done by 'ip' from the iproute2 package:
See http://lxr.linux.no/#linux+v3.1.4/Documentation/networking/can.txt#L646
Regards,
Oliver
prev parent reply other threads:[~2011-12-03 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 9:04 RFC: improve and consolidate state change and bus-off handling Wolfgang Grandegger
2011-12-02 9:41 ` Marc Kleine-Budde
2011-12-02 10:04 ` Wolfgang Grandegger
2011-12-03 9:28 ` Sebastian Haas
[not found] ` <4ED9EBAB.4060701-xpvPi5bcW5W9w4jpWW8B1qHonnlKzd3f@public.gmane.org>
2011-12-03 10:18 ` Oliver Hartkopp
2011-12-03 11:53 ` Sebastian Haas
2011-12-03 16:53 ` Oliver Hartkopp [this message]
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=4EDA53FA.2090105@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=dev@sebastianhaas.info \
--cc=linux-can@vger.kernel.org \
/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).