Am 22.08.2011 14:22, schrieb Ansell, John: > > Hi guys, > > > > Apologies if this is a repost, I fear I may have hijacked another thread by > mistake (sorry René!).
Hi John, no problem :) > > > > > 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. > > > > 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'. I think, without support for CAN in the ip tool, you are a bit lost. The best solution is to compile your own ip, which is part of iproute2. CAN support should be part of it since 2 (?) years. Best regards, René > > > How can I get my can interfaces 'up'? Can I set the bitrate from a userland > task, maybe via ioctls or something? > > Has anybody got a busybox build to work? > > I don't see a CAN device in /dev - should I? > > > > I'd be very grateful for any pointers! > > > > Best regards > > John Ansell > > > _______________________________________________ > Socketcan-users mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/socketcan-users _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
