From: Marc Kleine-Budde <mkl@pengutronix.de>
To: John Whitmore <arigead@gmail.com>
Cc: linux-can@vger.kernel.org
Subject: Re: baudrate detection
Date: Sat, 14 Dec 2013 14:29:02 +0100 [thread overview]
Message-ID: <52AC5D1E.2010802@pengutronix.de> (raw)
In-Reply-To: <20131212184012.GA18112@griso.site>
[-- Attachment #1: Type: text/plain, Size: 2111 bytes --]
On 12/12/2013 07:40 PM, John Whitmore wrote:
> I'm coming from the embedded micro controller end of using CAN and have created
> my own CAN Network nodes. Now I'm working with a MCP2515 connected to the
> Raspberry Pi, so looking at the Linux Kernel.
A SPI based CAN adapter like the mcp2515 are known to have bad
performance, you probably will have better CAN experience with an USB
adapter.
> On my existing nodes the Initialisation of the CAN device the node either knows
> the baudrate to setup or it does not. A node that is a fixed node on the
> network knows the baudrate of the network, although this can be changed on the
> fly. Other devices are not a fixed part of the network and are connected
> dynamically to the network for testing or management purposes. These nodes
> don't know the baudrate of the network so automatically detect it. When they
> detect the baudrate they then connect and inform the higher application code
> that the network is connected, so they can proceed.
>
> I was thinking of adding this auto baudrate detection functionality to the
> RaspberryPi but being new to Linux development I'm struggling with whether
> this functionality should be in Kernel or User Space. I was initially thinking
> User Space but given that numerous applications can be using the CAN Network
> you really want to centralise this functionality. That possibly means Kernel
> Space?
>
> So before I start to do something I thought I'd ask the experts. Does
> automatic baudrate detection belong in Kernel Space or out in Userland? Maybe
> it's already in the existing Kernel I've just missed it.
I think for prototyping the algorithm you should start in userspace, the
you can present it here and then we can discuss if it's better suited in
a library or in the kernel space.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
prev parent reply other threads:[~2013-12-14 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 18:40 baudrate detection John Whitmore
2013-12-14 13:29 ` Marc Kleine-Budde [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=52AC5D1E.2010802@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=arigead@gmail.com \
--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 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.