Stockholm, Embedded World, Nuremberg, Germany, said that it will support the multi-core alliance's new multi-core communication API (MCAPITM) by ensuring that the MCAAPI is deployed in the Enea LINX interprocess communication (IPC) solution to ensure the close linkage process and multi-core Interoperability between devices. LINX technology has been deployed in more than 1.7 billion devices, including telecommunications equipment, automobiles and mobile devices. In addition, Enea, a member of the multi-core alliance, will also join and participate in the Alliance's MCAPI working group to assist in the long-term development of the standard.
MCAPI is an evolutionary message delivery standard initiated by the multi-core alliance. The MCAPI API specification is designed to capture the basic elements of communication and synchronization required by a decentralized (multi-core and/or on-board chip on a chip). Although MCAPI now specifies a dedicated API for an application, it leaves the underlying protocol execution to the MCAPI installer. This ensures the compatibility of the application code, but it does not guarantee the interoperability between MCAPI end nodes or system nodes, perhaps a multi-core device or a set of homogeneous or heterogeneous CPUs. Enea's LINX has provided an established, open, interoperable protocol for all devices, all internal connections, and all OS/RTOS environments. Enea installs the MCAPI API standard on its existing LINX protocol, providing the market with an MCAPI API solution that can work together across all nodes, internal connections, and OS/RTOS platforms. The LINX protocol specification and Linux open source reference implementation apply to SpurceForge. Net.
"Recently, there has been a growing concern in the market for MCAPI, especially for silicon suppliers," said VP Marcus Hjortsberg of Enea's marketing department. "Silicon crystal manufacturers believe that the entire embedded industry wants to have an "ecosystem." Supports the compatibility and interoperability of IPC solutions, and not only for individual solutions from multi-core vendors. Enea clearly recognized this trend and decided to join the MCVAPI's advanced process.â€
“The MCAPI Working Group recently relaunched the definition and development of a subsequent version of the Multicore Alliance specification,†said Markus Levy, President of the Multicore Alliance. “Enea, based on its years of LINX experience, will provide tremendous value for the work of the working group. In addition, we also encourage other embedded development groups to join the multi-core alliance and participate in the work of our other multi-core related work groups."
Enea recently demonstrated LINEX-based MCAPI for its partners and customers. Together with Freescale, Enea developed a demo version of Freescale's AMC motherboard that consists of P2020 QorIQ processor and MSC8156 DSP to display multi-core OS including Linux, Enea eq oac (O;R) OSE and OSEck. , and communication between heterogeneous devices within a multi-core device and through multiple intrinsic connections.
MCAPI is an evolutionary message delivery standard initiated by the multi-core alliance. The MCAPI API specification is designed to capture the basic elements of communication and synchronization required by a decentralized (multi-core and/or on-board chip on a chip). Although MCAPI now specifies a dedicated API for an application, it leaves the underlying protocol execution to the MCAPI installer. This ensures the compatibility of the application code, but it does not guarantee the interoperability between MCAPI end nodes or system nodes, perhaps a multi-core device or a set of homogeneous or heterogeneous CPUs. Enea's LINX has provided an established, open, interoperable protocol for all devices, all internal connections, and all OS/RTOS environments. Enea installs the MCAPI API standard on its existing LINX protocol, providing the market with an MCAPI API solution that can work together across all nodes, internal connections, and OS/RTOS platforms. The LINX protocol specification and Linux open source reference implementation apply to SpurceForge. Net.
"Recently, there has been a growing concern in the market for MCAPI, especially for silicon suppliers," said VP Marcus Hjortsberg of Enea's marketing department. "Silicon crystal manufacturers believe that the entire embedded industry wants to have an "ecosystem." Supports the compatibility and interoperability of IPC solutions, and not only for individual solutions from multi-core vendors. Enea clearly recognized this trend and decided to join the MCVAPI's advanced process.â€
“The MCAPI Working Group recently relaunched the definition and development of a subsequent version of the Multicore Alliance specification,†said Markus Levy, President of the Multicore Alliance. “Enea, based on its years of LINX experience, will provide tremendous value for the work of the working group. In addition, we also encourage other embedded development groups to join the multi-core alliance and participate in the work of our other multi-core related work groups."
Enea recently demonstrated LINEX-based MCAPI for its partners and customers. Together with Freescale, Enea developed a demo version of Freescale's AMC motherboard that consists of P2020 QorIQ processor and MSC8156 DSP to display multi-core OS including Linux, Enea eq oac (O;R) OSE and OSEck. , and communication between heterogeneous devices within a multi-core device and through multiple intrinsic connections.