Is anyone else affected by this problem?Look, I get it—it’s open source, and that’s great. But we’re not talking about some esoteric feature here. This is core hardware support that’s been broken-by-design for years across multiple generations of hardware. Expecting every user who wants multichannel HDMI output to reverse-engineer Broadcom's silicon and implement a compliant ALSA interface from scratch? That’s not empowerment. That’s abdication.If you think the driver is broken... This is Linux. Download the source code and either fix it to your liking, or just write a new one.
Yes, it would be nice to find some help with getting full functionality out of a Pi's HDMI port. But at this point I believe it's a highly flawed design that is impossible to get full functionality out of.
Relevant thread is here.
viewtopic.php?p=2322885#p2322885
The tools are only powerful if the architecture respects the user. Right now, Raspberry Pi’s HDMI stack is an anti-pattern in user trust, driver transparency, and functional documentation. So no, I’m not going to write a kernel module just to make my AVR light up the right way. I’m going to make noise until the people who shipped the thing fix the mess they built
Statistics: Posted by ame — Fri Jun 27, 2025 3:41 am