On Thu, Sep 1, 2016 at 2:24 PM, Roopesh K P <roopeshkp@xxxxxxxxxxxxxxx> wrote:
> Today I tested the CAN with R-CAR M2 (Koelsch board) because r8a7791 is
> listed in CAN driver compatibility list .
>
> ' dmesg | grep -i can ' shows
>
> vcan: Virtual CAN interface driver
> slcan: serial line CAN interface driver
> slcan: 10 dynamic interface channels.
> CAN device driver interface
> rcar_can e6e80000.can: device registered (reg_base=e78f2000, irq=218)
> can: controller area network core (rev 20120528 abi 9)
> can: raw protocol (rev 20120528)
> can: broadcast manager protocol (rev 20120528 t)
> can: netlink gateway (rev 20130117) max_hops=1
>
> I can't see any pfc error/warning message which is happened in the case of
> R-CAR E2 (ALT board), but couldn't get the expected result in R-CAR M2
> Koelsch board also.
>
> For testing purpose , I checked the result of Virtual CAN (vcan) , it is
> working fine.
>
> Then my question is ,
>
> Is it not possible to test native (real hardware) CAN interface like can0 in
> Koelsch or ALT board ?
CAN is not enabled in arch/arm/boot/dts/r8a7791-koelsch.dts, as the Koelsch
board doesn't have the needed interfaces?
I believe ALT also lacks these interfaces.
The only boards where it's currently supported are r8a7791/porter and
r8a7792/blanche.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
