On 07/20/2011 07:49 AM, Grigory Abuladze wrote:
Hi
With regards to this
http://lists.meego.com/pipermail/meego-ivi/2011-July/000652.html
http://wiki.meego.com/In-vehicle/Roadmap/Vehicle_Network_API
A few comments:
1. Possible Use Cases:
.. Pay-As-You-Drive : Insurance companies can provide App, which
reports the driver’s driving habits with his consent. The data can be
used to discount insurance fee…
Should be read as “The data WILL BE used to INCREASE insurance fee.”
Don’t even mention all connected to privacy and so on :)
2. CAN stack.
Do you hear something about
SocketCAN http://en.wikipedia.org/wiki/SocketCAN ?
Which is:
- mature, comes from real automotive
- integrated into kernel
- ndev based, not chardev
- has build in virtual CAN adapter
- has HW specific drivers support from almost all CAN HW modules
manufacturers
Shouldn’t we just reuse already available and easily integrable
technology instead of reinvent CAN-stack wheel again?
I believe the goal is to build an API on top of CAN to abstract OEM
specific implementation/protocol details away from applications.
SocketCAN can very well be used in conjunction with this API to do the
low level reading and writing to the bus. Otherwise, SocketCAN is not
terribly useful as SocketCAN doesn't understand what information is
available in any given vehicle.
_______________________________________________
MeeGo-ivi mailing list
[email protected]
http://lists.meego.com/listinfo/meego-ivi
