From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Florian Feldbauer <florian@ep1.ruhr-uni-bochum.de>,
linux-can@vger.kernel.org
Subject: Re: Writing socketCAN module for my own hardware
Date: Wed, 01 Oct 2014 15:11:56 +0200 [thread overview]
Message-ID: <542BFD9C.1000308@pengutronix.de> (raw)
In-Reply-To: <542BF9FD.5060209@ep1.ruhr-uni-bochum.de>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
On 10/01/2014 02:56 PM, Florian Feldbauer wrote:
>> BTW: what's the use-case of the rpi, better buy a beagle bone black.
>> IIRC you need to attach the CAN phy, and you're ready to go. It comes
>> with two internal CAN cores, the first one is quite easy to setup, the
>> second one uses the same pins as one the the I2C busses, which has to be
>> disabled then... And you can use a proper mainline kernel.
> I'm working at the university for experimental hadron physik. And for
> our experiment we need a low budget, high performance CANbus interface
> running under Linux.
High performance and bit banging in one sentence (or SoC) is a bit
contradictory :)
> We came up with the idea of the Rpi, since it's small, it has ethernet,
> and it is
> cheap (~30 euro). And with the sja1000 connected to the GPIOs you can
> achieve
> the high data throughput (up to 6666 extended data frames with 8 byte
> length @1Mbit/s)
Beagle Bone is about ~60€ in single quantities.
> Actually I don't know if any other embedded linux board like the beagle
> bone
> was considered...
:(
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: 181 bytes --]
next prev parent reply other threads:[~2014-10-01 13:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 7:51 Writing socketCAN module for my own hardware Florian Feldbauer
2014-08-12 8:24 ` Marc Kleine-Budde
2014-08-12 8:57 ` Florian Feldbauer
2014-08-12 10:01 ` Marc Kleine-Budde
2014-10-01 7:26 ` Florian Feldbauer
2014-10-01 7:49 ` Marc Kleine-Budde
2014-10-01 12:32 ` Florian Feldbauer
2014-10-01 12:41 ` Marc Kleine-Budde
2014-10-01 12:56 ` Florian Feldbauer
2014-10-01 13:11 ` Marc Kleine-Budde [this message]
2014-10-09 15:06 ` Florian Feldbauer
2014-10-09 16:13 ` Marc Kleine-Budde
2014-10-10 7:43 ` Florian Feldbauer
2014-10-10 8:06 ` Marc Kleine-Budde
2014-10-10 8:09 ` Florian Feldbauer
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=542BFD9C.1000308@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=florian@ep1.ruhr-uni-bochum.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 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).