[{"data":1,"prerenderedAt":246},["ShallowReactive",2],{"$fwuenr1OZcDw8TjcC-BzsU1lhSGBFolBhwdGCSmwMXKw":3,"$fojHSG2c2udKYhjlxrA_OBNWuHb2j-EfJo-1Agapdodg":4,"$fVqO0k1BAadQrWkzSdzKIzB9FEw46o3cTAskVE807S0o":147,"mdc--ayrxix-key":198},null,{"id":5,"name":6,"description":8,"sessions":11,"colors":145},515,{"en":7,"zh-hant":7},"Open-EP (E-Paper) Community",{"en":9,"zh-hant":10},"Open-EP is a Taiwan-based community dedicated to open-source electronic paper (E-Paper) technologies. We focus on promoting the development and application of E-Paper display modules in embedded systems. Our contributors include hardware engineers, embedded software developers, and makers who are passionate about low-power display technologies.\r\n\r\nOur main activities include:\r\n\r\n1. Open-Source Hardware Development:\r\nWe maintain the open-ep.org project and provide open hardware designs for E-Paper driver boards.\r\n\r\n2. Cross-Platform Support:\r\nWe support multiple processor platforms, including Renesas, NXP, and Raspberry Pi. We develop various applications for these platforms and release them all as open source.\r\n\r\n3. Linux Kernel Contributions:\r\nWhile E-Paper is traditionally MCU-oriented, we focus on addressing industry pain points by submitting E-Paper–related Device Tree patches and DRM drivers to the mainline Linux kernel. We are proud to have had our contributions reviewed and accepted upstream.\r\n\r\n4. Technical Sharing:\r\nWe regularly participate in conferences in Taiwan and internationally, sharing our experience in E-Ink controller integration, display optimization, and embedded platform porting.\r\n\r\nWe believe E-Paper technology has tremendous potential in IoT, wearable devices, and AI-powered smart displays. Through open collaboration, we aim to lower technical barriers and enable more developers to easily integrate E-Paper into their projects.","Open-EP 是一個來自台灣、專注於開源電子紙（E-Paper）技術的社群，致力於推廣電子紙顯示模組在嵌入式系統中的應用與開發。我們的社群貢獻者包含硬體工程師、嵌入式軟體開發者，以及對低功耗顯示技術有興趣的創客。 \r\n\r\n社群主要活動包括： \r\n\r\n1. 開源硬體開發：維護 open-ep.org 專案，提供開放的電子紙模組驅動板設計。\r\n2. 跨平台支援：支援多種處理器平台，包括 Renesas、NXP、Raspberry Pi 等, 我們都有編寫各種應用並全部開源。\r\n3. Linux 核心貢獻：電子紙通常都以MCU應用為主, 我們針對業界痛點為主線 Linux 核心提交電子紙相關的 Device Tree 補丁與DRM驅動程式, 並已經得到了審核通過的殊榮。\r\n4. 技術分享：定期參與過台灣與國際研討會，分享 E-Ink 控制器整合、顯示最佳化、以及嵌入式平台移植經驗 。\r\n\r\n我們相信電子紙技術在物聯網、穿戴裝置、AI智慧顯示等領域具有巨大潛力，希望透過開源協作，降低技術門檻，讓更多開發者能夠輕鬆地將電子紙整合到他們的專案中。",{"2026-08-08":12},[13,39,60,82,105,124],{"id":14,"room":15,"start":18,"end":19,"language":20,"track":21,"speakers":23,"zh":31,"en":35,"tags":36,"uri":38},"9KULK9",{"en":16,"zh-hant":17},"TR412-1","","2026-08-08T14:40:00+08:00","2026-08-08T15:10:00+08:00","中文",{"id":5,"name":22},{"en":7,"zh-hant":7},[24],{"id":25,"avatar":26,"zh":27,"en":30},"3WYPUV","https:\u002F\u002Fpretalx.coscup.org\u002Fmedia\u002Favatars\u002F3WYPUV_gVKahcC.webp",{"name":28,"bio":29},"蔡丞銳","大家好，我是Triangle，目前是一名熱愛硬體的 Maker。平時喜歡把玩各種感測器與顯示模組，致力於尋找軟硬體整合的最佳解法。\r\n\r\n這次的專案源自我被市面上極度碎片化的電子紙驅動「雷」過無數次的血淚史。秉持著「看不慣就自己造輪子」的開源精神，我決定動手整合出一套跨型號的通用 API，並深入研究底層波形榨出了灰階功能。我深信開源的價值在於為社群填坑、降低開發門檻，希望這次的分享能幫助大家不再受電子紙型號所苦，輕鬆把精力花在打造更酷炫的專案上！\r\n[GitHub](https:\u002F\u002Fgithub.com\u002FmeteorTriangle)",{"name":28,"bio":29},{"title":32,"describe":33,"type":34},"解密 E-paper 驅動：跨型號硬體抽象層設計與灰階 Waveform 實作","電子紙（E-paper）憑藉著超低功耗與護眼特性，在物聯網設備與自造者專案中大受歡迎。然而，開發者往往面臨一個巨大的痛點：「驅動程式極度碎片化」。市面上常見的電子紙模組（如 Waveshare 系列），即使尺寸相同，內部控制晶片與初始化指令也可能完全不同，導致開發者經常需要重複造輪子，難以將程式碼跨型號移植。\r\n\r\n本議程將分享如何打造一套跨型號的電子紙通用 API。透過建立完善的硬體抽象層（HAL），開發者只需撰寫一次程式碼，即可無縫適配多款不同型號的電子紙模組，大幅降低開發與維護成本。\r\n\r\n此外，本議程的另一大技術亮點是「灰階功能的逆向與實作」。許多平價電子紙模組在官方預設下僅支援純黑白顯示，我們將深入探討電子紙的刷新原理，解析如何透過控制硬體波形（Waveform LUT）或演算法，突破硬體原廠限制，在通用 API 的架構下成功榨出平滑的灰階顯示效果。\r\n\r\n這套解決方案目前已實作於 [ESP32 \u002F Arduino \u002F stm32 \u002F Rpi \u002F Rpi pico] 平台，並以 [ C ] 開源。無論你是深受電子紙驅動折磨的 Maker，還是對底層波形控制感興趣的開發者，都能在這場議程中獲得實用的解法與啟發。","Talk",{"title":32,"describe":33,"type":34},[37],"Intermediate","https:\u002F\u002Fcoscup.org\u002F2026\u002Fsession\u002F9KULK9",{"id":40,"room":41,"start":42,"end":43,"language":20,"track":44,"speakers":46,"zh":54,"en":57,"tags":58,"uri":59},"BRNRVS",{"en":16,"zh-hant":17},"2026-08-08T16:10:00+08:00","2026-08-08T16:40:00+08:00",{"id":5,"name":45},{"en":7,"zh-hant":7},[47],{"id":48,"avatar":49,"zh":50,"en":53},"VLD79B","https:\u002F\u002Fpretalx.coscup.org\u002Fmedia\u002Favatars\u002FVLD79B_tGakcEq.webp",{"name":51,"bio":52},"Summer Lin","Hello, 我是Summer. 目前在Smartbox technology擔任firmware engineer, 韌體開發主要以zephyr RTOS為主. Smartbox technology 為有溝通障礙的殘障人士設計專用的電腦, 致力於深入研究使用者的需求, 開發出能幫助他們溝通的產品. 這對我來說是非常有意義的工作。\r\n在這之前我在台灣有10年的韌體開發經驗, 從最底層的韌體開發到Linux device driver 以及應用程式都有一些經驗, 希望我的演講可以帶給正在開發路上的你有點幫助.",{"name":51,"bio":52},{"title":55,"describe":56,"type":34},"Streaming Images from PC to an LCD on Zephyr over USB","Many embedded display systems rely on tightly coupled firmware or vendor-specific tooling, making it difficult to integrate with desktop applications or iterate quickly on UI workflows.\r\n\r\nIn this talk, I will present a practical end-to-end pipeline for streaming images from a host computer to an embedded LCD display, At its core is running open-source Zephyr RTOS. The system uses a custom USB protocol transfers, enabling efficient and flexible communication between a PC-side application (implemented in C#).\r\n\r\nI will walk through the system architecture, including USB protocol design, framebuffer handling, and integration with Zephyr’s display API, along with practical development experiences such as debugging, transfer performance, and reliability considerations, and approaches that can also be extended to lower-power display technologies such as e-paper systems.\r\n\r\nThe talk focuses on reusable design approaches and avoids proprietary implementation details. Attendees will gain a reusable model for building similar host-to-device display pipelines in their own projects.",{"title":55,"describe":56,"type":34},[37],"https:\u002F\u002Fcoscup.org\u002F2026\u002Fsession\u002FBRNRVS",{"id":61,"room":62,"start":19,"end":63,"language":64,"track":65,"speakers":67,"zh":75,"en":78,"tags":79,"uri":81},"CVHJQU",{"en":16,"zh-hant":17},"2026-08-08T15:40:00+08:00","English",{"id":5,"name":66},{"en":7,"zh-hant":7},[68],{"id":69,"avatar":70,"zh":71,"en":74},"URL8AA","https:\u002F\u002Fpretalx.coscup.org\u002Fmedia\u002Favatars\u002FURL8AA_yjhFhy7.webp",{"name":72,"bio":73},"Leon Anavi","Leon Anavi is an open source enthusiast and a senior software engineer at Konsulko Group. He is an active contributor to various Yocto\u002FOpenEmbedded meta layers, Automotive Grade Linux (AGL) and many other open source projects. His professional experience includes web and mobile application development for various platforms as well as porting and maintaining embedded Linux distributions to Raspberry Pi and devices with x86-64, i.MX6, i.MX8, NVIDIA Tegra, RISC-V, Amlogic, Rockchip and Allwinner (aka sunxi) SoC. Leon holds a masters in Information Technology from the Technical University Sofia. His previous speaking experience includes talks about open source software and hardware during virtual and in-person events in San Francisco, San Diego, Portland (OR), Hong Kong, Shanghai, Shenzhen, Brussels, Lyon, Berlin, Edinburgh, London, Cambridge, Bratislava, Prague, Nice, Sofia and his hometown Plovdiv.",{"name":72,"bio":73},{"title":76,"describe":77,"type":34},"Smart Home Displays with ePaper: A Maker’s Guide Using ESP32 and the Arduino Ecosystem","ePaper displays are an ideal solution for always-on low power smart home interfaces, offering excellent readability and near zero energy consumption when static. In this session, we show how makers can build their own smart home displays using ESP32 based XIAO modules and the Arduino ecosystem.\r\n\r\nStarting from the basics, you will learn how to interface a 4.2\" monochrome ePaper display driven by the SSD1680 controller using the open source Seeed GFX Library. The presentation covers hardware comparison of the XIAO ePaper Display breakout boards and explains their differences and typical use cases. The session demonstrates how to render dynamic content such as sensor data, home automation status information, and custom dashboards while optimizing for low power operation. By the end, you will have a practical foundation for building your own battery powered smart home displays suitable for digital signage, room dashboards, and portable information panels.\r\n\r\nThis talk is suitable for everyone and no previous experience is required. It will be hopefully useful both for engineers and makers who are interested in using ePaper displays in their projects, whether they are just getting started or looking to expand their existing skills.",{"title":76,"describe":77,"type":34},[80],"Elementary","https:\u002F\u002Fcoscup.org\u002F2026\u002Fsession\u002FCVHJQU",{"id":83,"room":84,"start":85,"end":86,"language":20,"track":87,"speakers":89,"zh":97,"en":100,"tags":103,"uri":104},"MCWCLS",{"en":16,"zh-hant":17},"2026-08-08T13:30:00+08:00","2026-08-08T14:00:00+08:00",{"id":5,"name":88},{"en":7,"zh-hant":7},[90],{"id":91,"avatar":92,"zh":93,"en":96},"UFGYUX","https:\u002F\u002Fpretalx.coscup.org\u002Fmedia\u002Favatars\u002FUFGYUX_nReSj4p.webp",{"name":94,"bio":95},"Wig Cheng","一個開源軟體開發愛好者, 主攻Linux\u002FAndroid BSP開發, 常在AOSP, Linux Kernel upstream做微薄貢獻. 也是台灣Open-EP, 日本Kakip社群的維護者",{"name":94,"bio":95},{"title":98,"describe":99,"type":34},"open-ep: 從硬體設計到 Mainline Kernel, 一個 e-paper 社群的完整開源實踐","市面上的 e-paper 模組大多依賴廠商提供的 SPI userspace 函式庫，且大多都是MCU的應用，無法與 Linux 標準顯示堆疊整合。更關鍵的是，這些模組的硬體設計和機構細節往往不透明，開發者只能被動接受。\r\nopen-ep 是一個「從硬體到內核全面開源」的社群。我們的 PixPaper 系列產品：\r\n\r\n1. 硬體與機構自主設計\r\n- PCB layout、connector 選型、機構設計全部由社群完成，不依賴 ODM\r\n2. DRM driver upstream\r\n- 已進入 mainline Linux kernel，並獲得 LWN.net 報導\r\n- 因為upstream審核很耗時, 我們也有在vendor kernel實做DRM driver\r\n3. 多 OS 生態支援\r\n- 針對ARM Yocto BSP、Android AOSP、Ubuntu OS, freeRTOS 等不同系統特性擴充應用場景\r\n4. 資安問題納入考慮\r\n- 加入BSP的應用，我們還是會考慮到SBOM的建置與CVE漏洞修補，以符合不同國家(如歐盟CRA)的軟體資安標準\r\n\r\n軟體這不只是「把 driver 推進 kernel」，而是完整展示一個小規模社群如何：\r\n\r\n從電路設計開始就考慮 mainline 相容性\r\n與 kernel maintainer 溝通，讓 patch 順利進入 upstream\r\n平衡「賣產品維持營運」與「推動開源標準化」的雙重目標\r\n透過 COSCUP、UBUCON ASIA, OSPN Japan等技術社群建立信任\r\n\r\n我們相信，硬體開源不只是「公開 schematic」，而是從設計階段就融入開源生態的思維。open-ep 想證明，即使是資源有限、需要自願貢獻者幫忙的社群，也能對 mainline Linux 和產業標準做出實質貢獻。",{"title":101,"describe":102,"type":34},"open-ep: From Hardware Design to Mainline Kernel — A Complete Open Source Practice for E-Paper Community","Most e-paper modules on the market rely on vendor-provided SPI userspace libraries and are primarily designed for MCU applications, making them incompatible with the standard Linux display stack. More critically, the hardware design and mechanical details of these modules are often opaque, leaving developers with no choice but to accept them as-is.\r\nopen-ep is a community practicing \"full-stack open source from hardware to kernel.\" Our PixPaper product line features:\r\n\r\n1. Self-designed Hardware and Mechanical Structure\r\n- PCB layout, connector selection, and mechanical design are all completed by the community without relying on ODMs\r\n\r\n2. DRM Driver Upstream\r\n- Merged into mainline Linux kernel and covered by LWN.net\r\n- Since upstream review is time-consuming, we also implement DRM drivers in vendor kernels\r\n\r\n3. Multi-OS Ecosystem Support\r\n- Extended application scenarios across ARM Yocto BSP, Android AOSP, Ubuntu OS, FreeRTOS, and other systems\r\n\r\n4. Security Considerations\r\n- For BSP applications, we address SBOM generation and CVE vulnerability patching to comply with software security standards in different regions (such as the EU CRA)\r\n\r\nThis goes beyond \"pushing drivers into the kernel\" — it demonstrates how a small-scale community can:\r\n\r\nConsider mainline compatibility from the circuit design phase\r\nCommunicate with kernel maintainers to successfully upstream patches\r\nBalance \"selling products for sustainability\" with \"promoting open source standardization\"\r\nBuild trust through technical communities like COSCUP, UBUCON ASIA and OSPN Japan.\r\n\r\nWe believe hardware open source is not just about \"publishing schematics,\" but integrating open source ecosystem thinking from the design stage. open-ep aims to prove that even resource-limited communities relying on volunteer contributions can make substantial contributions to mainline Linux and industry standards.",[80],"https:\u002F\u002Fcoscup.org\u002F2026\u002Fsession\u002FMCWCLS",{"id":106,"room":107,"start":63,"end":42,"language":64,"track":108,"speakers":110,"zh":118,"en":121,"tags":122,"uri":123},"SFVHC9",{"en":16,"zh-hant":17},{"id":5,"name":109},{"en":7,"zh-hant":7},[111],{"id":112,"avatar":113,"zh":114,"en":117},"ZMEB9N","https:\u002F\u002Fpretalx.coscup.org\u002Fmedia\u002Favatars\u002FZMEB9N_BH6PvuZ.webp",{"name":115,"bio":116},"Alex Lennon","Alex Lennon has been working with embedded Linux and OpenEmbedded for at least 15 years (possibly longer, but his memory is shot). He's the founder of Dynamic Devices Ltd and delivered a keynote at Yocto Project Summit 2022.\r\n\r\nOver the past few months, Alex has been experimenting with AI-assisted development workflows for Yocto projects, learning what works, what doesn't, and where the real productivity gains lie. His recent work includes automated hardware testing, remote target debugging, and power optimization workflows - all enhanced by AI collaboration.\r\n\r\nAlex believes the embedded community needs to figure out AI integration together, sharing both the successes and the failures to develop practical best practices.",{"name":115,"bio":116},{"title":119,"describe":120,"type":34},"Agentic AI and Rust on Linux: Accelerating Jaguar E-Ink Bring-Up with SSH, Webcams, and Yocto","This session is about **speeding up embedded bring-up** for the **Jaguar EInk Display**: **colour e-paper** on **NXP i.MX93 SOC** with **Yocto \u002F OpenEmbedded** customisation, plus a **Zephyr-based companion chip** for **power management**—targeting **5+ years** operation with the **PMU** approach for realistic **scheduled static signage** workloads.\r\n\r\nThe Linux side display and controller integration are implemented as a **Rust userspace application** on the Linux image—code people often call a “driver,” but here it is **userspace engineering**, iterated like any other critical service.\r\n\r\nThe focus is **agentic AI** (e.g. **Cursor-class agents**) and how it changes the loop when you feed it **real hardware feedback**. I will describe a workflow we relied on: **SSH** to boards (including remote lab setups), **automated deploy** of rebuilt artefacts, and **webcam capture** of what is actually on the panel—fed back into the agent loop so “what we think we programmed” is checked against **what appears on hardware**. That closes the gap between compile-only optimism and **hardware truth**.\r\n\r\nI will cover **partitioning** between **Linux + Rust app** and **Zephyr on the PMU** at an architectural level (**rail sequencing, sleep\u002Fwake, responsibilities**). **PMU application firmware remains closed source**; I will not present proprietary files—only the **integration surface**, **debug strategy**, and lessons that remain useful when part of the stack is private.\r\n\r\nThe product direction includes **long-life maintenance** thinking aligned with **UK-CE RED** and **EU CRA** expectations around **secure boot** and **OTA**—discussed **technically**, not as legal advice.\r\n\r\n### Open artefacts\r\n- [meta-dynamicdevices](https:\u002F\u002Fgithub.com\u002FDynamicDevices\u002Fmeta-dynamicdevices)\r\n- [eink-power-cli](https:\u002F\u002Fgithub.com\u002FDynamicDevices\u002Feink-power-cli)\r\n- [esp-eink](https:\u002F\u002Fgithub.com\u002FDynamicDevices\u002Fesp-eink) (older open e-paper reference material)\r\n\r\n### Audience\r\n\r\nEmbedded \u002F Linux developers; Rust curiosity helps; deep kernel internals not required.\r\n\r\n### Outline (30 minutes)\r\n1. Goals and architecture (**Linux + eink display rust app + Zephyr PMU**)\r\n2. Yocto customisation highlights using Foundries.io stack for secure boot and OTAU\r\n3. Agentic workflow (**SSH**, deploy, logs)\r\n4. Webcam-in-the-loop verification for panel outcomes\r\n5. Failures and guardrails; Q&A (**Open-EP** collaboration themes)\r\n\r\n### Takeaways\r\n\r\n- A repeatable pattern for **remote hardware feedback loops** with agents  \r\n- Pointers to **public repos**\r\n\r\n### Related\r\n- Prior talk (agentic Yocto-era workflows): [Yocto Project Summit 2025.12](https:\u002F\u002Fpretalx.com\u002Fyocto-project-summit-2025-12\u002Ftalk\u002F3KKPQM\u002F)\r\n- Product framing: [etablone](https:\u002F\u002Fetablone.com\u002F)",{"title":119,"describe":120,"type":34},[37],"https:\u002F\u002Fcoscup.org\u002F2026\u002Fsession\u002FSFVHC9",{"id":125,"room":126,"start":86,"end":18,"language":20,"track":127,"speakers":129,"zh":137,"en":140,"tags":143,"uri":144},"VBEX7Y",{"en":16,"zh-hant":17},{"id":5,"name":128},{"en":7,"zh-hant":7},[130],{"id":131,"avatar":132,"zh":133,"en":136},"LJQFGG","https:\u002F\u002Fpretalx.coscup.org\u002Fmedia\u002Favatars\u002FLJQFGG_QkuaMFR.jpg",{"name":134,"bio":135},"王良丞\u002FLCWang","嵌入式系統工程師\u002Fembedded engineer",{"name":134,"bio":135},{"title":138,"describe":139,"type":34},"從 SPI 顯示面板到 Android 螢幕：ARM64 平台的 DRM 顯示驅動整合之旅","Android 的圖形顯示架構主要是針對 HDMI、eDP、MIPI-DSI 等高效能顯示介面所設計。然而，在許多嵌入式系統中，仍然會使用像 SPI 這類較為特殊的顯示介面，而這些介面通常並不在 Android 標準顯示管線的主要支援範圍內。\r\n\r\n本次演講將分享一個實際案例：如何在 ARM64 平台上，將一個基於 SPI 介面的自訂顯示驅動程式整合進 Android 14 的圖形顯示架構。該驅動程式是基於 Linux DRM（Direct Rendering Manager）框架實作，用於驅動一個透過 SPI 連接的小尺寸電子紙顯示器。\r\n\r\n演講將以 RK3588 平台為實際案例，說明 Linux DRM 子系統與 Android graphics stack 之間的整合流程。我們會解析 SurfaceFlinger、Hardware Composer（HWC3）與 DRM\u002FKMS 之間的互動關係，以及在 Android 系統中導入非標準顯示裝置時可能遇到的各種挑戰。",{"title":141,"describe":142,"type":34},"From SPI Panel to Android Screen: Integrating a Custom DRM Display Driver on ARM64","Android's graphics stack is primarily designed for high-performance display interfaces such as HDMI, eDP, and MIPI-DSI. However, many embedded systems still rely on unconventional display interfaces like SPI, which are rarely supported by Android's standard display pipeline.\r\n\r\nThis talk presents a real-world case study of integrating a custom SPI-based display driver into the Android 14 graphics stack on an ARM64 platform. The driver is implemented using the Linux DRM framework and drives a small e-paper display connected through SPI.\r\n\r\nUsing RK3588 as a practical example, this session walks through the full integration process between the Linux DRM subsystem and the Android graphics stack. We will explore how SurfaceFlinger, Hardware Composer (HWC3), and DRM\u002FKMS interact, as well as the challenges encountered when bringing up a non-standard display device in Android.",[37],"https:\u002F\u002Fcoscup.org\u002F2026\u002Fsession\u002FVBEX7Y",{"2026-08-08":146},"#4ecdc4",[148,154,160,165,169,173,177,182,188,193],{"id":149,"imageVertical":150,"imageHorizontal":151,"link":152,"weight":153},"QNAP-news","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1-HQ9oQMOngtqM3yL-1DBHRhzWbuyxgfE&&sz=w4000","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1aVhw014dwVLuxbNadE314lnl992FcjS_&&sz=w4000","https:\u002F\u002Fwww.qnap.com\u002Fgo\u002Fsolution\u002Fvirtualization",2,{"id":155,"imageVertical":156,"imageHorizontal":157,"link":158,"weight":159},"Cathay-news","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=10ndsUHILq9m_boaoilHTERyTXCsCBlSX&&sz=w4000","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=11_VlhFrCYcNOHML4z0jm6AmyL7MxNTfl&&sz=w4000","https:\u002F\u002Fwww.cathayholdings.com\u002Fholdings\u002Fbrand\u002Ffintech",6,{"id":161,"imageVertical":162,"imageHorizontal":163,"link":164,"weight":159},"esunbank-news","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1aNURMNN83oIZHAtBzm2rUZODKVBO29dt&&sz=w4000","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=17OA0eu-N510ePhhDuiSuBV_4mdlU5gfi&&sz=w4000","https:\u002F\u002Fwww.esunbank.com\u002Fzh-tw\u002Fpersonal",{"id":17,"imageVertical":166,"imageHorizontal":167,"link":168,"weight":159},"https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1_NsnJt2O238fO_dLl19RR4SNbyRErIJY&&sz=w4000","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1Q989E0GWazdVSPcGvZLMYzsNSh4cV2-g&&sz=w4000","https:\u002F\u002Fwww.mysql.com\u002F",{"id":17,"imageVertical":170,"imageHorizontal":171,"link":172,"weight":159},"https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1d4-1ZBMs6GqYcYytlYrSVZhs8Jgye5l3&&sz=w4000","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1Ea4CNZ-14siicP3xYm78l3AF41iAb9Om&&sz=w4000","https:\u002F\u002Fberry-ai.com",{"id":17,"imageVertical":174,"imageHorizontal":175,"link":176,"weight":159},"https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1A9Q35aOO4LDtI1-MVbIlLoGBmWn2VwZg&&sz=w4000","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=13Oz8Eq6MXXspGEqwi5QGbwYyDNeU1idK&&sz=w4000","https:\u002F\u002Fnitra.com\u002F",{"id":178,"imageVertical":179,"imageHorizontal":180,"link":181,"weight":153},"kktix-news","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=11md6cNzKBG-OF_e_9G5ZCLujoyck96as&&sz=w4000","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1ec5tuBMqbKDfPakOPWZF93Q55JI7DOOl&&sz=w4000","https:\u002F\u002Fkktix.com\u002F",{"id":183,"imageVertical":184,"imageHorizontal":185,"link":186,"weight":187},"gamesofa-news","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1HkRfiNOhKrH2zTaOHjTkDnAmoDPqV5_c&&sz=w4000","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1IVAroDzzryU5AIY4qMMVztg4hu-FXaIM&&sz=w4000","https:\u002F\u002Fwww.gamesofa.com",3,{"id":189,"imageVertical":190,"imageHorizontal":191,"link":192,"weight":153},"onlyoffice-news","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1H7dguSsKUH9aS9vxK-RhI519LEQjaak-&&sz=w4000","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1IchePy7nwLT4TXnLYLf8o6HS4TKOOjFd&&sz=w4000","https:\u002F\u002Fwww.onlyoffice.com\u002F",{"id":194,"imageVertical":195,"imageHorizontal":196,"link":197,"weight":153},"SUN-SQUARE-news","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=19TU_W9JBLzrRYVSQPG4cbbckhWLy0JaS&&sz=w4000","https:\u002F\u002Fdrive.google.com\u002Fthumbnail?id=1-2rlsJngO4Qiu0SElyXhMYmsjmGokHu_&&sz=w4000","https:\u002F\u002Fsunsquare.tech\u002F",{"data":199,"body":200},{},{"type":201,"children":202},"root",[203,211,216,241],{"type":204,"tag":205,"props":206,"children":207},"element","p",{},[208],{"type":209,"value":210},"text","Open-EP is a Taiwan-based community dedicated to open-source electronic paper (E-Paper) technologies. We focus on promoting the development and application of E-Paper display modules in embedded systems. Our contributors include hardware engineers, embedded software developers, and makers who are passionate about low-power display technologies.",{"type":204,"tag":205,"props":212,"children":213},{},[214],{"type":209,"value":215},"Our main activities include:",{"type":204,"tag":217,"props":218,"children":219},"ol",{},[220,226,231,236],{"type":204,"tag":221,"props":222,"children":223},"li",{},[224],{"type":209,"value":225},"Open-Source Hardware Development:\nWe maintain the open-ep.org project and provide open hardware designs for E-Paper driver boards.",{"type":204,"tag":221,"props":227,"children":228},{},[229],{"type":209,"value":230},"Cross-Platform Support:\nWe support multiple processor platforms, including Renesas, NXP, and Raspberry Pi. We develop various applications for these platforms and release them all as open source.",{"type":204,"tag":221,"props":232,"children":233},{},[234],{"type":209,"value":235},"Linux Kernel Contributions:\nWhile E-Paper is traditionally MCU-oriented, we focus on addressing industry pain points by submitting E-Paper–related Device Tree patches and DRM drivers to the mainline Linux kernel. We are proud to have had our contributions reviewed and accepted upstream.",{"type":204,"tag":221,"props":237,"children":238},{},[239],{"type":209,"value":240},"Technical Sharing:\nWe regularly participate in conferences in Taiwan and internationally, sharing our experience in E-Ink controller integration, display optimization, and embedded platform porting.",{"type":204,"tag":205,"props":242,"children":243},{},[244],{"type":209,"value":245},"We believe E-Paper technology has tremendous potential in IoT, wearable devices, and AI-powered smart displays. Through open collaboration, we aim to lower technical barriers and enable more developers to easily integrate E-Paper into their projects.",1784991555714]