Op 26 jul. 2012, om 11:03 heeft "AnilKumar, Chimata" [off-list ref] het volgende geschreven:

On Thu, Jul 26, 2012 at 14:16:33, Koen Kooi wrote:

quoted

Op 25 jul. 2012, om 14:23 heeft AnilKumar Ch [off-list ref] het volgende geschreven:

quoted

Add Bosch D_CAN controller device tree data to AM33XX dtsi file
by adding d_can device node with all the necessary parameters.

Signed-off-by: AnilKumar Ch <redacted>
---
arch/arm/boot/dts/am33xx.dtsi |    5 +++++
1 file changed, 5 insertions(+)

diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 9b974dc..2db2ffb 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot/dts/am33xx.dtsi

@@ -163,5 +163,10 @@

			#size-cells = <0>;
			ti,hwmods = "i2c3";
		};
+
+		dcan1: d_can@481D0000 {
+			compatible = "bosch,d_can";
+			ti,hwmods = "d_can1";
+		};
	};

I scanned the linux-networking mailinglist and l-o-ml, but I can't find the patchset that actually adds the d_can drivers, could you provide a link to that? I have 2 different CAN capes I'd like to test on beaglebone.

You can find it from linux-next or net-next trees, D_CAN support is added
to C_CAN driver.

http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;
a=commitdiff;h=69927fccd96b15bd228bb82d356a7a2a0cfaeefb

Thanks! I'll try merging net-next into l-o master and see if I can get the CAN boards to work.

regards,

Koen