[renaming the 'Q: do HAL signals exist independently of components yes/no?' thread because it warrants its own.]
now that hal_* functions might be reduced to userland and init/cleanup: Is there any need for HAL components to use hal_ functions other than to *allocate and deallocate* objects? I think the set of necessary-in-RT-land functions for regular (non-halcmd/non-management) components can be further cut down to: hal_init, hal_alloc, hal_read, hal_exit hal_*new, hal_newf hal_export_funct The others could be moved to a class 'HAL management API' which should not be used in normal components; a bit like what hal_priv.h was intended to cover. Background: this reduces complexity of any futute RT/in-kernel interface to HAL. - Michael ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
