linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Max S." <max@schneidersoft.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "Sebastian Haas" <dev@sebastianhaas.info>,
	"Heinz-Jürgen Oertel" <hj.oertel@t-online.de>,
	linux-can@vger.kernel.org
Subject: Re: adding can4linux to drivers/char
Date: Sun, 29 Sep 2013 19:23:42 +0000	[thread overview]
Message-ID: <1380482622.14050.15.camel@blackbox> (raw)
In-Reply-To: <52487518.80008@pengutronix.de>

This isn't on topic to this thread...
Just thought I'd note:

On Sun, 2013-09-29 at 20:44 +0200, Marc Kleine-Budde wrote:
> If there is a need for bitrate detection, feel free request it here. I
> think there are some controllers that support this in hardware, while
> others don't. Is there a known working algorithm for bitrate detection?

Most controllers have listen only mode, in which the error counters are
frozen. It is then possible to systematically try all common bit-rate
configurations, and listen for good frames. works best when you start
with high speeds and work your way down. Listen only mode baud sniffing
will require at least two other nodes (one to send, one to ack..)

Some controllers also have a mode similar to listen only, but that also
internally connect the TX signal to the RX signal. this way you only
need 1 other node to send non acked frames. the autobauding node will
then ack those frames for itself only. Atmel calls this mode LOOPBACK...
even though its not a typical "LOOPBACK".

Additionally when using micros with on-board CAN controllers the RX pin
can be temporarily reprogrammed to an input. With a pin change interrupt
and a timer it is then possible to measure the TQ used by other nodes.



  reply	other threads:[~2013-09-29 19:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 23:03 adding can4linux to drivers/char Heinz-Jürgen Oertel
2013-09-21  9:17 ` Oliver Hartkopp
2013-09-21 19:57   ` Wolfgang Grandegger
2013-09-21 13:38 ` Marc Kleine-Budde
2013-09-21 16:37   ` Sebastian Haas
2013-09-21 17:09     ` Marc Kleine-Budde
2013-09-21 18:17       ` Oliver Hartkopp
     [not found]         ` <CADGMhsXaJOpbdCgEAoOguZWX2rS_P0a-H5UDZwUWiHD4Nj=upw@mail.gmail.com>
2013-09-22 10:40           ` Marc Kleine-Budde
2013-09-22 11:01           ` Oliver Hartkopp
2013-09-23 13:46       ` Marc Kleine-Budde
2013-09-21 19:55 ` Wolfgang Grandegger
2013-09-29 16:28   ` Heinz-Jürgen Oertel
2013-09-29 17:44     ` Marc Kleine-Budde
2013-09-29 17:45     ` Sebastian Haas
2013-09-29 18:44       ` Marc Kleine-Budde
2013-09-29 19:23         ` Max S. [this message]
2013-09-29 19:17           ` Heinz-Jürgen Oertel
2013-09-29 19:43           ` autobaud detection (was: Re: adding can4linux to drivers/char) Marc Kleine-Budde
2013-09-30  7:30         ` adding can4linux to drivers/char Sebastian Haas
2013-09-30 10:20           ` Kurt Van Dijck
2013-09-29 19:23       ` Heinz-Jürgen Oertel
2013-09-30  9:35         ` Oliver Hartkopp
2013-10-01 20:20           ` AW: " May, Stefan
2013-10-02  7:49             ` Oliver Hartkopp
2013-10-02  8:43             ` Linux CAN CUSE hacks, SocketCAN and RT Was: " Pavel Pisa
2013-10-02  9:47               ` Wolfgang Grandegger
2013-09-29 19:41     ` Wolfgang Grandegger
2013-09-30  7:40       ` Sebastian Haas
2013-09-30  8:21         ` Wolfgang Grandegger

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=1380482622.14050.15.camel@blackbox \
    --to=max@schneidersoft.net \
    --cc=dev@sebastianhaas.info \
    --cc=hj.oertel@t-online.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    /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).