>> Please let me know, if this is a known issue with kernel 2.6.27 and is there >> any other way to solve the same. >> >> I have seen the mails exchanged on a similar issue at >>`https://lists.berlios.de/pipermail/socketcan-core/2009-June/002657.html`
>It seems to be a known issue, but we do not have a fix yet. I will have >a closer look. Thanks for your help. As I am still learning about SocketCAN, one query regarding the CONFIG_CAN_DEV_SYSFS=y option: I read from the `kConfig` file kept at `drivers\net\can` (in the latest SocketCAN trunk on SVN) that this support has been *deprecated*. Please let me know, if I develop a driver that supports SysFS instead of netlink interface (to do away with the `warn_on_slowpath` dump ), will it qualify as a SocketCAN driver on the lines of `sja1000` driver that also supports SysFS. Actually, this may be a major stumbling point for my client ;) Regards, Bhupesh -- View this message in context: http://www.nabble.com/Query-regarding-%60warn_on_slowpath%60-dump-with-2.6.27-tp25991331p26007626.html Sent from the Socket-CAN Core mailing list archive at Nabble.com. _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
