It's clear that there already are examples that intermingle proprietary and Open Source. The kernel has loadable modules that can be proprietary. In that case an open source OS is consuming a proprietary driver. Mozilla can load proprietary Java applets for another example.
My assumption is that the ixCOM stuff works the same way. That is, if a GPL application knows about a public interface, it could consume that public interface - even if it's implemented with a proprietary component. In other words, the GPL application is the consumer of a proprietary ixCOM component.
I know the FUD and potential embedded Linux customers are worried. Lineo, the embedded Linux guys, has recently announced a solution: ixCOM is a component object model for Linux that leverages run-time binding. This should(?) allow for worry free combinations of components with intellectual property and GPL components.
Here's a quote from Lineo's press release at the ESC in Germany:
"Lineo ixCOM technology provides a fundamental component object framework that is streamlined for embedded platforms. It not only provides the benefits of a modern component model with reusable, maintainable plug-in components, but it also has built-in intellectual property protection for licensable third party components on Linux."
It's clear that there already are examples that intermingle proprietary and Open Source. The kernel has loadable modules that can be proprietary. In that case an open source OS is consuming a proprietary driver. Mozilla can load proprietary Java applets for another example. My assumption is that the ixCOM stuff works the same way. That is, if a GPL application knows about a public interface, it could consume that public interface - even if it's implemented with a proprietary component. In other words, the GPL application is the consumer of a proprietary ixCOM component.
I know the FUD and potential embedded Linux customers are worried. Lineo, the embedded Linux guys, has recently announced a solution: ixCOM is a component object model for Linux that leverages run-time binding. This should(?) allow for worry free combinations of components with intellectual property and GPL components. Here's a quote from Lineo's press release at the ESC in Germany: "Lineo ixCOM technology provides a fundamental component object framework that is streamlined for embedded platforms. It not only provides the benefits of a modern component model with reusable, maintainable plug-in components, but it also has built-in intellectual property protection for licensable third party components on Linux."