All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Jander <david@protonic.nl>
To: Andri Yngvason <andri.yngvason@marel.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	"Rost, Martin" <Martin.Rost@tonfunk.de>
Subject: Re: MCP2515 implementation is slow
Date: Thu, 27 Nov 2014 08:46:27 +0100	[thread overview]
Message-ID: <20141127084627.6888dc6b@archvile> (raw)
In-Reply-To: <20141126123242.13254.31551@shannon>

On Wed, 26 Nov 2014 12:32:42 +0000
Andri Yngvason <andri.yngvason@marel.com> wrote:

> Quoting Rost, Martin (2014-11-26 12:02:13)
> > Hi all,
> > 
> > > this VERY POOR chip.
> > As the mcp251x is voted down by the list members regularly, is there an
> > alternative you guys would recommend?
> > 
> Well, sja1000 is pretty solid. They're used for example in the peak_pci.

It is actually pretty sad that one still tends to mention this old dinosaur.
It has a terribly slow parallel multiplexed bus-interface that works on 5V. If
you want to connect it to a modern ARM SoC, you will have to implement some
quite expensive level-shifting and then probably bit-bang the interface via
GPIO's or use an (even more expensive and complicated) CPLD or FPGA to do the
bus-translation. You are kidding, right?

To go back to the sad reality of CAN interfaces: No, there seems to be no
good alternative whatsoever.

If you want SocketCAN on an embedded system, choose a SoC that has built-in CAN
controllers or connect a supported commercial CAN interface via USB or (if you
have it) PCIe. Please note that many commercial (USB-) CAN-interfaces are not
capable of producing 100% bus load at higher bitrates. USB has too much
latency and the dongles tend to have too little buffer-space (there's often a
SJA1000 crammed up inside).

Best regards,

-- 
David Jander
Protonic Holland.

  reply	other threads:[~2014-11-27  7:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 16:19 MCP2515 implementation is slow Pankajkumar Misra (RBEI/EEA2)
2014-11-25 16:47 ` gianluca
2014-11-26  5:02   ` Pankajkumar Misra (RBEI/EEA2)
2014-11-26 16:13     ` gianluca
2014-11-26 12:02   ` Rost, Martin
2014-11-26 12:32     ` Andri Yngvason
2014-11-27  7:46       ` David Jander [this message]
2014-11-27  7:33 ` David Jander

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=20141127084627.6888dc6b@archvile \
    --to=david@protonic.nl \
    --cc=Martin.Rost@tonfunk.de \
    --cc=andri.yngvason@marel.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.