HDMI vs DisplayPort?... DiiVA is the answer from China!
During the early 2000’s, when OEM starting to question the use of LVDS to interface with display devices, two standards has emerged: High-Definition Multimedia Interface (HDMI) and DisplayPort. HDMI has been developed by silicon Image, surfing on the success of Digital Video Interface (DVI), and was strongly supported by a consortium counting Hitachi, Ltd., Panasonic Corporation, Philips Consumer Electronics International B.V., Silicon Image, Inc., Sony Corporation, Technicolor S.A. (formerly known as Thomson) and Toshiba Corporation, the “founders”. Pretty impressive list, at least in the Consumer Electronic market! The Video Electronics Standards Association (VESA) decided to launch a competing standard, DisplayPort. DisplayPort was back-up by companies linked to the PC market, like HP, AMD, Nvidia, Dell and more… The competition looked promising, as both standards exhibits the same high level features: based on high speed differential serial signaling, packet based protocol, layered based architecture, allowing to increase bandwidth by using 1 to 3 lanes (HDMI) or 1 to 4 (DP) for the most significant.
To read the full article, click here
Related Semiconductor IP
- Chiplet Die-to-Die Interconnect IP Solution
- High speed MACsec Engine 100G/200G/400G/800G/1.6T
- Temperature/Voltage sensors
- AMBA Bus Host to eSPI Controller/Target
- AMBA Bus Host to eSPI Controller
Related Blogs
- HDMI, DisplayPort, MHL IPs + Engineering Team = Good Move
- DisplayPort 2.1 vs DisplayPort 1.4: A Detailed Comparison of Key Features
- Rethinking Display Safety: Why RISC-V-Supervised DisplayPort Subsystems Enable Secure, Isolated Automotive Architectures
- The Semiconductor World vs TSMC vs EDA
Latest Blogs
- Cadence Achieves Successful Silicon Validation of 1st IP Test Chips on Intel 18A
- From Classical CAN and CAN FD to CAN XL: Functional Safety and Security for Next-Generation In-Vehicle Communication
- Accelerating Embedded Memory Performance with 16-bit xSPI PSRAM IP
- Why nonce reuse can break AES-GCM security in embedded systems
- PQSecure™-Agility Earns NIST CAVP Validation