juanba romance wrote: > Hello, all, > I am currently developing a RTDM/xenomai driver for the CANbus chipset 82527 > that i think it could have some interest > it has the next features:
Thanks for moving our private thread here! See, now we know that Wolfgang is already working on 82527 support for RT-Socket-CAN - something I wasn't aware of as well. > > 1. Specific management for the remote frames CANbus feasibility, it > couple the real-time data bus flow with a user software feedback to > handshake remote frames and update mailbox callback for the auto-replied > messages Mind to elaborate what you precisely gain here compared to "open-coded" designs (loop closed over the application)? Can you quantify the improvements? > 2. Transparent use to push/suck data from the driver using a common > data format > 3. Capability to push a bunch of CANbus messages in a single system > call. The bunch is copied to a kernel domain ring buffer to guarantee low > latencies at the user side. A specific kernel thread sucks the ring > pushing > the user request into the chipset That was discussed before in the context of Socket-CAN. My feeling is that it /could/ be useful in case you have to issue longer streams of CAN frames at high rates, and specifically if your CAN hardware can handle these streams autonomously. Is the 82527 able to do so? In any case, this would complicate the existing stack and driver and would first require careful evaluation of the achievable improvement (lower latency, lower system load?). > 4. Driver readout using a native RT message queue where the control > and data flow is published And this way you make your driver unportable, e.g. to move it over the RTDM layer Wolfgang wrote for the -rt kernel. RTDM drivers are ought to use RTDM services (or Linux ones), not other skins. If a generally useful service is lacking, we need to think about adding it - to RTDM. > 5. Multichipset capabilities, right now a commercial PC104 board with > two devices is used. The on board CPU is a SBC VIA C3 1GHz processor > softwared with the stack xenomai-2.3,1/vanilla-2.6.20-15/Adeos- > ipipe-1.7-03 > 6. board monitoring through the /proc file system entry > 7. Local Data Transfers controlled with RT-alarms Another violation - but this one is easily avoidable with RTDM timers that come with API revision 6 (upcoming Xenomai 2.4). > 8. Virtual support to check applications/driver usage/design, right > now only the chipset is virtualised, but plans to have network transactions > are on going > 9. ISR hardware optimizations focused on the network readout to > gurantee low latencies Any numbers? > 10. Easy porting to other i82527 based on boards > 11. Full transmission operation handling the 16 message object set > > We have in plan also > > 1. Capabilities to filtering/masking the incoming flow at the driver > stage allowing that the same context, using the "xenomai nomenclature" feed > specific threads using some kind of binding/configuration process. This is > an open issue cause i don't have a clear approach to follow.. > 2. can-festival coupling Look, with Socket-CAN, you would now already have CAN-Festival binding. :) But maybe this library scenario can be used to explain why you need to do things in a special way and what you can gain that way. Looking forward! > > I think this is the full picture, i look forward.. > > Best regards.. > Jan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
