@Jean-Francois Lessard Thanks for your comprehensive answers. They helped me a lot, but as ill luck would have it, new questions arose ... As far as I can tell, the driver is loaded at second 2.7, which is perfectly early enough for me. Once the driver is ready to operate 8888 should be visible. Well, should .. I managed to get it running once and then I changed the config or the board dts or whatever and I never reached this state again, what a sh*t! May be you can spot any error in the dts, but I have the feeling that the error lurks somewhere else. You are so right, one can comment accurately on my questions if there is no dts you can look at. This time I attach my full dts to this post, promised. BTW, like I said before, I have an H96 Max V56, which has an FD6551 on the board. So there is no confusion. Rest assured, brightness is behaving as expected but is waaay to dark for me. If only those leds had white color ... Well I have made the led display "brighter" in a rather unconventional way -> I used a saw and sawed out a little rectangle from the front. Maybe my tv box doesn't look as pleasing as before, but the led display is much brighter now. Form follows function , ya know?! 🤣 Since the led display did work once, I think both SDA and SCL are configured correctly. i2c-6 is, in fact, the i2c node the kernel assigned to the tm16xx driver. When my tv box starts, somewhere in the kernel log I get i2c-gpio display-client: using lines 12 (SDA) and 11 (SCL) ... tm16xx 6-0024: Failed to set brightness: -6 tm16xx 6-0024: Failed to initialize display: -6 (-6 is ENXIO -> no device) The driver simply is unable to talk to the chip and I really don't know why. BTW my kernel has version 6.12.12 and the tm16xx is not built in but is a .ko Understood, I tried them and they worked, but thanks for the explanation (I found them earlier on your Github pages.) Yep, later. Led display isn't working right now ... 🙂 I have the feeling that using pinctrl would necessitate a "slight" rewrite of your driver and at the moment my inclination to go down this rabbit hole is, well, limited... But the question is,if there is a pinctrl definition regarding these two GPIO lines, will this definition interfere with the definition of the gpio lines in the display-client section? When using pinctrl I couldn't find any way to set the baud rate used for the communication. Is it unnecessary or is there some sort of auto-negotiation? So if you have any idea how I can arrive at a working led display again, please(!) let me know. Currently I'm at my wits end. All the best, Deetsh P.S.: oh, there is one thing I need to ask you: Do you know a way to make testing new versions of the dts easier than building an image and downloading in the emmc? myboard.dts

Hell Hello, No, sorry, I don't have any news from my side. I'm taking a break from this project but I plan to get back to it soon. If you get any progress, let me know, I'm interested! o, No, sorry, I don't have any news on my side. I'm making a break on this project but will go back to find a solution soon. If you get some interesting steps let me know!

As we approach our next point release, the focus shifts entirely towards bug fixing and stabilization. Feature development is on hold this month to ensure that core functionalities like network connectivity, video output, and booting processes are solid. We aim to resolve as many issues as possible during this period. However, we encourage users to report any recognized problems here so that they can be addressed in future updates. Target for next release We are targeting kernel v6.12 for our current builds and v6.13 for edge builds, while vendor kernels will remain at their latest versions. We are releasing major upgrade on Rockchip vendor kernel. We focus on providing stable builds where we have active maintainers who are well-versed in the current status of images. If you’re interested in contributing, consider stepping up. For Aspiring Maintainers (tl;dr;): Review the status of the board(s) you want to maintain, including vendor, current, and optionally edge kernels. Address issues as early as possible, ideally before the last week of the month. Once ready, release the updates in one go. Update the board configuration from .csc to .conf here and add yourself as a maintainer. Adjust extensions if needed here. Release Deadline: February 20th If there’s something you can’t manage, please open a ticket. Thank you for your contributions and dedication. Stay well and safe! The Armbian team The post Release is coming! first appeared on Armbian. View the full article

What do you mean by that. Please be specific as I don't know what you are referring to.

@Constantin Gatej added on first page, thanks!