From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Sebastian Haas <dev@sebastianhaas.info>
Cc: "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 20:44:40 +0200 [thread overview]
Message-ID: <52487518.80008@pengutronix.de> (raw)
In-Reply-To: <CADGMhsXTbEc5ifQEbNM=dS3OP6uwGrvGfZ3OCvWJ=aXJyzGs+A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2223 bytes --]
On 09/29/2013 07:45 PM, Sebastian Haas wrote:
> I think Heinz-Jürgens' arguments are not that wrong. There are a bunch
> of example in the kernel of concurring solution for the same issues
> every single one with different advantages and disadvantages (just
> compare how many solution for virtualization are available kvm, xen,
> paravirt, ...).
You're right.
> There must be space in kernel for the classical chardev CAN-approach.
> Sharing common code to access the different controllers must be
> possible.
That's already implemented in the Kernel, it's called a driver.
> I think there are a bunch of use cases out there which are easier and
> more efficiently solved with a simple chardev API. A simple chardev
> CAN driver like can4linux provide doesn't depend on the whole
> networking subsystem which may be imported of real embedded systems
> with strong memory constraints (less memory footprint, smaller
> kernel).
The smallest system we're running Linux is a Cortex M3, it's on chip RAM
is to small for Kernel + Userspace, so you need an external RAM chip
anyways.
> The Socket approach has some real advantages (multi-user for single
> CAN controller, iptables filtering, netutil integration, buffering,
> ..), but many of them may be considered as disadvantages as well (no
> control of the message flow in terms of timing and ordering, no
You you have ordering problem? That's a bug? Which driver/hardware?
> exclusive use of the interface, networking dependency). Implementing
> an automatic bitrate detection or application driver busoff recovery
> is a pain in the ass with SocketCAN.
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?
How can we make busoff recovery better? What's the most annoying point?
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 --]
next prev parent reply other threads:[~2013-09-29 18:44 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 [this message]
2013-09-29 19:23 ` Max S.
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=52487518.80008@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=dev@sebastianhaas.info \
--cc=hj.oertel@t-online.de \
--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.