All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Menschel <menschel.p@posteo.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can <linux-can@vger.kernel.org>
Subject: Re: Testing CAN on Allwinner A20 / Banana Pi
Date: Sat, 19 Mar 2016 13:50:01 +0100	[thread overview]
Message-ID: <56ED4AF9.6090500@posteo.de> (raw)
In-Reply-To: <56ED4725.8080209@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]

Thanks Marc,

that works apparently.

ifconfig -a
can0      Link encap:UNSPEC  Hardware Adresse
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:16  Metrik:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:10
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:35


Regards,
Patrick





Am 19.03.2016 um 13:33 schrieb Marc Kleine-Budde:
> On 03/19/2016 01:27 PM, Patrick Menschel wrote:
>> you mentioned that you have a running Bpi with mainline kernel.
>>
>> My question would be if you're also running mainline u-boot with device
>> tree bindings.
> 
> I'm running a u-boot, not sure which version.
> 
>> I'm now running mainline kernel from stable branch
>> compiled with sunxi_defconfig thus CAN driver is built-in and mainline
>> u-boot according to
>>
>> http://linux-sunxi.org/Mainline_Kernel_Howto
>> http://linux-sunxi.org/Mainline_U-boot
>> .
>>
>> I've added can0 entries manually to
>>
>> arch/arm/boot/dts/sun7i-a20.dtsi
>> arch/arm/boot/dts/sun7i-a20-bananapi.dts
>>
>> since they are missing in the stable branch.
>>
>> Compiling to dtb and back to dts now resolves to
>>
>> 		can@01c2bc00 {
>> 			compatible = "allwinner,sun4i-a10-can";
>> 			reg = <0x1c2bc00 0x400>;
>> 			interrupts = <0x0 0x1a 0x4>;
>> 			clocks = <0x31 0x4>;
>> 			status = "okay";
>> 			pinctrl-names = "default";
>> 			pinctrl-0 = <0x32>;
>> 		};
>>
>> That does look plausible from my perspective.
>>
>> Unfortunately I'm still missing /dev/can0 and have no clue why.
> 
> CAN devices are network devices and will not show up in "/dev". Have a
> look at:
> 
>     ifconfig -a
> 
>> If your Bpi works with legacy u-boot, I would try that next.
> 
> Marc
> 


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3709 bytes --]

  reply	other threads:[~2016-03-19 12:50 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
2016-03-19 12:27   ` Patrick Menschel
2016-03-19 12:33     ` Marc Kleine-Budde
2016-03-19 12:50       ` Patrick Menschel [this message]
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=56ED4AF9.6090500@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 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.