Hello everyone, With one of my principal engineer we had a discussion about what protocol should or should not be exposed from a device driver stack. When you want to design to allow modular configuration, you may end with protocol that are used between different layers of your stack. Those protocols are private and should not be directly used by the IBV. So my question is how can a protocol be define as private or public? This concept exist in higher level framework such are .Net.
This is a little representation of the problematic where a platform specific
configuration driver needs to stay private:
UEFI App or Driver
| MydeviceProtocol(public)
V
My device driver
| MydeviceConfigurationProtocol(private)
V
My device configuration driver
Best Regards,
Mourad Souag; Firmware Architect; MCG - Oregon; 503-264-9111 [logo] Sponsors of
Tomorrow(tm)
<<inline: image001.png>>
------------------------------------------------------------------------------ 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/
_______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
