Chris Verges wrote: >> Does it work with other bitrates? Does your "ip" understand >> the type CAN? What does the following command show: >> >> ip -d -s link show can0 > > # ip -d -s link show can0 > 3: can0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN qlen 1000 > link/can > RX: bytes packets errors dropped overrun mcast > 0 0 0 0 0 0 > TX: bytes packets errors dropped carrier collsns > 0 0 0 0 0 0 > > It understands the type CAN, but for some reason, all of the details are > missing now. Using iproute2 from GIT tag > 274ba1a52a4076388018744cc3d828d1ac29628d. (That was the first w/ CAN > support, IIRC.)
I'm a bit puzzled, also your previous error message indicates, that can->bittiming_const is not defined. How do you build your modules? Wolfgang. _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
