is still unacceptable, we can bypass VFS and
implement CAN MAC driver directly on top of can_ops_s:
CAN MAC driver->can_ops_s(CAN lowhalf driver)
Then we can reuse all CAN low half drivers without change, and the
user can even sel
deally I would implement it as shown
>below. The question is though then how do deal with existing CAN character
>device implementation?
> NuttX SocketCAN implementation
> Proposal
>+-
Hi all,
This is a follow up to the SocketCAN integration into NuttX discussion. As
discussed before we proposed the idea to include SocketCAN support in NuttX to
provide a generic well-known interface for CAN transmission. The initial
feedback was great and Gregory Nutt looked into the possibil
:48 AM (GMT-06:00) To:
dev@nuttx.apache.org Subject: RE: Re: NuttX SocketCAN implementation >I believe
that both sides would be the same. Both would use BSD sockets, SocketCAN would
be added to the network stacks, and the CAN drivers would be a network
drivers.>>Your picture shows the
d go through the CAN driver -> Char driver
-> VFS -> Socket -> user space. This would add unnecessary delay and jitter
which would be certainly worse. Ideally I would implement it as shown below.
The question is though then how do deal with existing CAN character device
implem
I amn't familiar with CAN, but is it possible to implement a general
CAN MAC driver on top of CAN CHAR driver like this?
+---+
| NuttX Network driver |
| ++ ++ |
| |Syscall glue| |BSD Socket | |
| || |glue| |
| +-
NuttX CAN Implementation NuttX Ethernet Implementation
+---+ +---+
| Application | | Application |
+---+ +---+
+--
+pavel
-Original Message-
From: Peter Van Der Perk [mailto:peter.vanderp...@nxp.com]
Sent: Tuesday, February 11, 2020 6:58 AM
To: dev@nuttx.apache.org
Subject: NuttX SocketCAN implementation
Hi all,
This is a follow up to the SocketCAN integration into NuttX discussion. As
discussed
Hi all,
This is a follow up to the SocketCAN integration into NuttX discussion. As
discussed before we proposed the idea to include SocketCAN support in NuttX to
provide a generic well-known interface for CAN transmission. The initial
feedback was great and Gregory Nutt looked into the possibil
