From: Patrick Menschel <menschel.p@posteo.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Subject: Re: Testing CAN on Allwinner A20 / Banana Pi
Date: Sat, 12 Sep 2015 15:40:27 +0200 [thread overview]
Message-ID: <55F42B4B.90806@posteo.de> (raw)
In-Reply-To: <55F3ECAC.7040508@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2153 bytes --]
Hi,
the CAN4Linux Setup was made according to this walkthrough:
http://www.lemaker.org/thread-209-2-1-2.html
http://can-bus.996267.n3.nabble.com/can4linux-for-the-BananaPi-td4110.html
Transceiver is a Texas Instruments SN65HVD230DR 3,3V.
I have no application running with the CAN4Linux but I ran a few test
programs, such as a CAN dump.
I have an EDC17 that's flooding the CAN Bus with 11bit messages <1ms.
The BPi is capable to keep up with it.
An RPi with MCP2515 and socketcan instantly gives up.
I haven't tried it on the new RPi2 though.
Regards,
Patrick
Am 12.09.2015 um 11:13 schrieb Marc Kleine-Budde:
> On 09/12/2015 10:51 AM, Patrick Menschel wrote:
>
>> I'm new to socketcan and like to test the recent driver for the
>> Allwinner A20 on a BPi.
>>
>> I've got a BPi running CAN4Linux and like to setup a second BPi running
>> socketcan.
>
> Is your CAN4Linux setup working? It's good to have a working CAN station
> to talk to.
>
>> I have some basic questions prior to get started with the project:
>>
>> 1.
>> Which kernel version is necessary for the current socketcan?
>> I use the standard linux-sunxi kernel from the repos as this worked well
>> with CAN4Linux.
>> https://github.com/linux-sunxi/linux-sunxi.git
>
> I'm using mainline linux on my Bpi. Works quite well. I don't use the
> graphics, though.
>
>> 2.
>> I haven't been able to locate the recent driver on the repos.
>> https://git.kernel.org/cgit/linux/kernel/git/mkl/linux-can-next.git/
>> https://git.kernel.org/cgit/linux/kernel/git/mkl/linux-can.git/
>>
>> Did I miss something, because none of the related commits I see in the
>> mailing list are present in the repo?
>
> The driver by Gerhard Bertelsmann is still under review, you have to
> apply the patches:
>
> http://article.gmane.org/gmane.linux.can/8511/raw
> http://article.gmane.org/gmane.linux.can/8512/raw
>
> to your kernel manually. You have to switch on the CAN driver in you dts
> as documented in patch 8511. Note: When using the patch from the gmane
> archive you have to replace the " <at> " by a "@" sign.
>
> Marc
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3709 bytes --]
next prev parent reply other threads:[~2015-09-12 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 8:51 Testing CAN on Allwinner A20 / Banana Pi Patrick Menschel
2015-09-12 9:13 ` Marc Kleine-Budde
2015-09-12 13:40 ` Patrick Menschel [this message]
2016-03-19 12:27 ` Patrick Menschel
2016-03-19 12:33 ` Marc Kleine-Budde
2016-03-19 12:50 ` Patrick Menschel
2016-03-19 12:53 ` Marc Kleine-Budde
2016-03-21 9:27 ` gianluca
2016-03-21 13:05 ` Patrick Menschel
2016-03-21 16:14 ` Marc Kleine-Budde
2016-03-21 17:08 ` Patrick Menschel
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=55F42B4B.90806@posteo.de \
--to=menschel.p@posteo.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).