Hello Mike, On 15.07.2011 20:01, Mike Brown wrote: > I'm developing software for the Freescale P1010 microcontroller, running: > > Linux buildroot 2.6.35.13 #30 Mon Jun 20 10:49:21 CDT 2011 ppc GNU/Linux
AFAIK the last 2.6.35 kernel is 2.6.35.9 > It has two FlexCAN CAN 2.0B interfaces which are configured as: > > ip link set can0 up type can bitrate 1000000 > ip link set can1 up type can bitrate 1000000 > > I've got two apps running that utilize SocketCAN to access the CAN device, > both open the same interface (can0). App B is listening for a packet with a > specific ID/mask. App A starts and sends a packet with the appropriate ID > that B should catch, but B never sees it. If I start App B on the second CAN > interface, it does see the pack (as expected). > > I have queried CAN_RAW_LOOPBACK via getsockopt() and it says it is a 1. > > Also if I create a vcan interface, and both A and B open that interface, all > works as expected. > > What might need to do to get the Flexcan interface to behave the same as the > virtual can interface? There was a problem that has been introduced in the 2.6.35 in the networking stack that has been fixed in the stable series, see: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.35.y.git;a=commitdiff;h=a5f18b1cca50987eb7773bb0be0d8730dfb10306 Please check, if this patch is also part of your 2.6.35.13 tree. Best regards, Oliver _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
