On 22.08.2011 14:22, Ansell, John wrote: > Hi guys,
Hi John, i'll try to enhance the answer from Rene a bit ;-) > I need some advice regarding starting up the can0 and can1 devices please. > > > > Hardware is an AT91SAM9 (ARM) driving two MCP2515 controllers, one on each of > the SPI ports. SocketCAN support is built into the kernel, 2.6.38. dmesg shows > probes are successful and the CAN drivers are being loaded. Then you should see the CAN netdevices also in /proc/net/dev There are no CAN files created in /dev/xxx as the CAN devices use the network driver model like ethernet cards. > > I'm using busybox to handle the commands. Trouble is, its ip command doesn't > support the 'type can' or 'bitrate' parameters so the can devices stay down. > > How can I get my can interfaces up? Can I set the bitrate from a userland > task, maybe via ioctls or something? As Rene wrote, you need a 'recent' 'ip' from the iproute2 package: http://git.kernel.org/?p=network/iproute2/iproute2.git;a=summary > > Has anybody got a busybox build to work? In our setup we disabled the 'ip' tool in busybox and compiled the 'ip' from iproute2 ... > > I dont see a CAN device in /dev should I? That's correct that you don't see things in /dev/xxx .-) Regards, Oliver _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
