Chris Verges wrote: > Hi list, > > I'm attempting to build the SocketCAN kernel modules external to the > kernel and load them in. When I do, I see the following: > > # modprobe can-raw > can: controller area network core (rev 20090105 abi 8) > NET: Registered protocol family 29 > can: raw protocol (rev 20090105) > > # modprobe at91_can > CAN device driver interface using the deprecated SYSFS interface > at91_can netdevice driver > > # ip link show > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UNKN0 > link/ether 00:09:e6:ff:ff:fe brd ff:ff:ff:ff:ff:ff > > How do I get the can0 interface to show up after modprobing the at91_can > driver? I assumed it would automagically happen. > > (Prior to this, I've been porting the SocketCAN code directly into the > kernel and building monolithic. However, this is cumbersome so I'd like > to just use the external modules rather than maintain my own kernel > line. When building into the kernel directly, can0 does show up.)
FYI, at91_can is mainline: http://lxr.linux.no/#linux+v2.6.32/drivers/net/can/Kconfig#L38 Wolfgang. _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
