I recently shared some test results here: viewtopic.php?t=388366
That experience raised a broader question: as a hardware manufacturer, we often face challenges making our firmware fully compatible with different Raspberry Pi OS builds. At the moment, our firmware usually needs to be tuned separately for each image.
From a commercial and scalability perspective, this creates difficulties:
It increases adaptation costs when working with different software vendors.
It makes it harder to offer customers standardized, plug-and-play hardware.
I’d like to ask the community:
Are there established practices or approaches for making firmware integration with Raspberry Pi OS more standardized?
Is there an ecosystem-level solution (or tooling) that can help reduce the amount of per-image customization?
I’d really appreciate hearing your thoughts or experiences on this.
Thank you,
That experience raised a broader question: as a hardware manufacturer, we often face challenges making our firmware fully compatible with different Raspberry Pi OS builds. At the moment, our firmware usually needs to be tuned separately for each image.
From a commercial and scalability perspective, this creates difficulties:
It increases adaptation costs when working with different software vendors.
It makes it harder to offer customers standardized, plug-and-play hardware.
I’d like to ask the community:
Are there established practices or approaches for making firmware integration with Raspberry Pi OS more standardized?
Is there an ecosystem-level solution (or tooling) that can help reduce the amount of per-image customization?
I’d really appreciate hearing your thoughts or experiences on this.
Thank you,
Statistics: Posted by jammm — Mon Sep 08, 2025 5:48 am