Yes, CONFIG_CAN_CALC_BITTIMING=y
this is the default config that is supplied with the precompiled kernel. I assume this is what was actually used. I suppose I will have to re-compile the kernel to be sure, But I want to hit all the bases first. For dmesg I get for can0: kobject: 'spr-can.0' (0c033a630) kobject_uevent_env kobject: 'spr-can.0' (0c033a630) fill_kobj_path: path = /devices/platform/spr-can.0 and similar for can1 Wolfgang Grandegger wrote: > > On 03/09/2011 06:38 PM, Charles H wrote: >> >> >> >> Charles H wrote: >>> >>> Hello: >>> according th the documentation tha came with my SPEAR 320 demo board I >>> should be able to configure the CAN interface thus: >>> >>> ip link set can0 type can bitrate 125000 >>> but I get : >>> RTNETLINK Answers : operation not supported >>> It sounds like the kernel is not configured properly for IPROUTE2 >>> support >>> but I cant find what is missing in the config. default .config for >>> board >>> is attached http://old.nabble.com/file/p31101885/spear320_defconfig >>> spear320_defconfig :-/ > > What does "dmesg" report? Is CONFIG_CAN_CALC_BITTIMING=y? > > Wolfgang. > _______________________________________________ > Socketcan-users mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/socketcan-users > > -- View this message in context: http://old.nabble.com/ip-link-problem-STLinux-tp31101885p31109081.html Sent from the Socket-CAN Users mailing list archive at Nabble.com. _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
