Mike

@andralex How confident are you in this implementation? For some reason, noone from team DRuntime seems very interested in it (or maybe you're just too scary). Are you willing to...

> I'm unclear on how Higgs got broken, and probably we need to get to the bottom of that. Where can be failures be seen and how do they manifest...

> @JinShil we really need to restrict these new template hooks to NOT depend on anything but templates. Yes, I understand that, but we have to do it incrementally.

I'm referring to the general case, not anything specific. Converting the existing runtime hooks to templates is a major task. It involves refactoring DMD and druntime simultaneously. Also, because the...

@6by9 Thank you. Adding `video=HDMI-A-1:800x480M-32@60` to cmdline.txt resolved the frame buffer color depth issue. It is now reporting 32-bit as it should. However, when using `vc4-kms-v3d`, the driver still appears...

Reopening because I think the firmware should pass the color depth to the kernel driver, or some other solution where there is better cooperation between the firmware and the driver...

Playing around with this a little more today, I discovered that the `video=` kernel command line argument is already being passed by default. Here's the output of `cat /proc/cmdline` when...

My use case is for sharing code and ideas with others. So, for example, I could post an example to illustrate a minimal runtime with an object.d and a main.d,...

Tried a minimal runtime test with this: https://run.dlang.io/is/rrhgJL ``` [email protected](105): Option -o- currently not supported by rdmd ``` I'm not sure what that means.

So cool!. Thanks. I'm OK to close this issue if you consider it solved.