--- title: Open Source Summit North America | daily.dev description: Five Collabora engineers presented at Open Source Summit North America, covering NVMe performance in Linux (including virtualized environments), running... canonical: https://daily.dev/posts/open-source-summit-north-america-8qxnp8cp2 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Open Source Summit North America | daily.dev og:description: Five Collabora engineers presented at Open Source Summit North America, covering NVMe performance in Linux (including virtualized environments), running... og:url: https://daily.dev/posts/open-source-summit-north-america-8qxnp8cp2 og:image: https://api.daily.dev/og/posts/8qXnp8CP2.png og:image:alt: Open Source Summit North America og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Open Source Summit North America **[Collabora Blog](https://daily.dev/sources/collabora)** · 5 min read · 0 upvotes · 0 comments ## Summary Five Collabora engineers presented at Open Source Summit North America, covering NVMe performance in Linux (including virtualized environments), running Android on mainline graphics using DRM Atomic Modesetting and Explicit Synchronization, Linux performance analysis tools (perf, valgrind), buffer sharing synchronization in DRM/V4L2, and using Open Build Service (OBS) for automated multi-architecture package building and distribution. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can Android run on top of mainline Linux graphics instead of vendor-specific drivers? Android can run on mainline Linux graphics through DRM Atomic Modesetting and Explicit Synchronization added to the kernel. The drm_hwcomposer component bridges Android's graphics abstraction layer to the mainline DRM API, with additional changes to Mesa and the abstraction layer itself. This enabled Qualcomm, i.MX, and Intel-based platforms to run Android using the mainline graphics stack. _Developers working on Android-on-mainline graphics track related kernel and Mesa developments on daily.dev._ ### What is Explicit Synchronization in DRM and why does it matter for mainline Linux graphics? Explicit Synchronization in DRM lets userspace control the synchronization of buffers between drivers, enabling smarter and more efficient decisions than implicit synchronization. It was a prerequisite for running Android on mainline graphics, and V4L2 was also gaining support for it. Extensions were also being developed to improve performance in complex use cases like Android apps running inside ChromeOS. _Engineers following DRM and V4L2 development keep up with kernel graphics changes on daily.dev._ ## Similar posts on daily.dev - [Open Source in Prague: A week of talks, hands-on demos, and community\!](https://daily.dev/posts/open-source-in-prague-a-week-of-talks-hands-on-demos-and-community--w2mxqffp2) · Collabora Blog · 0 upvotes · 0 comments - [Exploring AI, observability and community at OSS Summit Korea 2025](https://daily.dev/posts/exploring-ai-observability-and-community-at-oss-summit-korea-2025-yln8gi6zf) · CNCF · 1 upvotes · 0 comments - [Bootlin at Open Source Summit Europe 2026 and Linux Plumbers 2026 – Bootlin](https://daily.dev/posts/bootlin-at-open-source-summit-europe-2026-and-linux-plumbers-2026-bootlin-q2stqmdxm) · Bootlin · 0 upvotes · 0 comments --- Tags: [#open-source](https://daily.dev/tags/open-source), [#linux](https://daily.dev/tags/linux), [#android](https://daily.dev/tags/android) [View this post on daily.dev](https://daily.dev/posts/open-source-summit-north-america-8qxnp8cp2) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Open Source Summit North America","url":"https://daily.dev/posts/open-source-summit-north-america-8qxnp8cp2","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/open-source-summit-north-america-8qxnp8cp2"},"datePublished":"2026-08-11T08:53:52.145Z","dateModified":"2026-08-11T09:19:17.623Z","description":"Five Collabora engineers presented at Open Source Summit North America, covering NVMe performance in Linux (including virtualized environments), running...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/64a2bdbf560a3fbeb3d606ca9c8b4ba8?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/64a2bdbf560a3fbeb3d606ca9c8b4ba8?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Collabora Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collabora Blog","logo":"https://media.daily.dev/image/upload/s--ZGZ0FjqS--/f_auto,q_auto/v1786438306/logos/collabora?_a=BAMAMicg0","url":"https://daily.dev/sources/collabora"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/open-source-summit-north-america-8qxnp8cp2","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,linux,android","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collabora Blog","item":"https://daily.dev/sources/collabora"},{"@type":"ListItem","position":3,"name":"Open Source Summit North America"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/open-source-summit-north-america-8qxnp8cp2#faq","mainEntity":[{"@type":"Question","name":"How can Android run on top of mainline Linux graphics instead of vendor-specific drivers?","acceptedAnswer":{"@type":"Answer","text":"Android can run on mainline Linux graphics through DRM Atomic Modesetting and Explicit Synchronization added to the kernel. The drm_hwcomposer component bridges Android's graphics abstraction layer to the mainline DRM API, with additional changes to Mesa and the abstraction layer itself. This enabled Qualcomm, i.MX, and Intel-based platforms to run Android using the mainline graphics stack. Developers working on Android-on-mainline graphics track related kernel and Mesa developments on daily.dev."}},{"@type":"Question","name":"What is Explicit Synchronization in DRM and why does it matter for mainline Linux graphics?","acceptedAnswer":{"@type":"Answer","text":"Explicit Synchronization in DRM lets userspace control the synchronization of buffers between drivers, enabling smarter and more efficient decisions than implicit synchronization. It was a prerequisite for running Android on mainline graphics, and V4L2 was also gaining support for it. Extensions were also being developed to improve performance in complex use cases like Android apps running inside ChromeOS. Engineers following DRM and V4L2 development keep up with kernel graphics changes on daily.dev."}}]} ```