Socket CAN(二） socketcan的整体工作流程

Socket CAN整体工作流程

It would register itself with the network stack, and the network stack will expect to send and receive packets. The CAN driver then needs to send these packets to the chip over a SPI bus. So it uses the SPI infrastructure to send these packets to the actual MCP2510. Every system has different SPI devices, so this way, the MCP2510 driver doesn't have to know how the actual SPI layer works, it just knows it needs to use the SPI protocol to talk to the MCP2510. From userspace, you would use the socket API to send you data to whatever device you're communicating with via CAN. So the whole thing should go together something like this: user space talks to socket API network driver talks to CAN driver CAN driver talks to SPI driver SPI driver talks to SPI hardware messages go over the SPI bus to MCP2510 MCP2510 sends messages over the CAN bus to the actual device

http://freakrobot.blogbus.com/logs/99523985.html

相关文章：

socketcan 的使用（一） can raw write: No buffer space available /article/5327056.html

Socket CAN(二） socketcan的整体工作流程 /article/5327064.html

socketcan 的使用（三） atmel9260上Linux socketcan MCP2515调试笔记 /article/5327098.html

Socketcan的使用(四） Low Level CAN Framework Application Programmers Interface

项目主页：http://developer.berlios.de/account/setlang.php

http://en.wikipedia.org/wiki/SocketCAN

邮件列表的订阅

https://lists.berlios.de/mailman/listinfo/socketcan-core