On Feb 5 2013 12:28 AM, Michael Haberler wrote: > Am 05.02.2013 um 01:29 schrieb Chris Morley: > >> Would your messaging scheme be just for HAL or would it replace NML >> ? > > Eventually HAL messaging will replace NML. > > Besides communicating individual signal values, it needs to be able > to convey compound objects (C structs if you will, for instance to > replace the EMCStatus access). I'll lay out in separate mail how > that's going to work and how UI's are impacted (or rather not). The > actual addition to hal_lib.c per se is fairly minimal, the rest is a > userland code affair.
would you consider using something like S expressions over 9p? I have similar in distributed environments. Since 9p has been ported to the Linux kernel main truck, it is generally available. There are also 9p stacks that also work all the way down to 8-bit embedded systems. It also works in userland. If I am not mistaken the synthetic in memory file systems has not been ported, but it is common practice to generate synthetic file systems. If people are willing to entertain that I will do a little research when I get back to my thesis (I will also be looking into zeromq and other low latency and lightweight point to point message passing systems). >> and licensing is holding back the messaging isn't it ( I mean aside >> from time) > > yes. > > Actually I'd rate the HAL messaging effort substantially lower than > the remapping effort in LOC, and it is very generic in nature. When I first read the LOC discussion I thought you were talking about Lines Of Code. Now I am not sure. What do you mean? EBo -- ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
