Back in October was an initial proposal for a DRM splash screen client for the Linux kernel that would be primarily useful for embedded systems for rendering a simple “splash screen” when updating the system firmware/software, early display activation at boot, during system recovery, or similar processes. Sent out today was a second revision to the DRM splash screen code.
There is already Plymouth as a great boot splash screen solution for Linux systems while this DRM splash screen primarily aims to fill different niches mainly in the embedded space when needing to display a simple graphic or similar. Stemming from objections raised during the original round of code review, user-driven functionality like configurable messages and a progress bar was dropped from this proposed code. Those solutions are best off left to user-space tooling.
I was so confused by the term DRM for a moment…
Writing an article about something and using only acronyms/initialisms without first defining them is just terrible writing.
The company we sell software for uses way too many acronyms. They also send out training registry emails, and I think nobody signs up because they don’t know what the acronym is referring to.
I.e Email:
Dear BlahBlah, Register for our DLMX webinar focused in FOH. There’s new LMT coming this year.
Me: Delete
Same, why the hell would we want DRMs in linux ?
to render stuff?
We originally understood DRM as digital rights management, hence the confusion…
Yeah, that happens.
There’s a third ‘DRM’ now, in this space which I recently read about. Although I forget what it was.
The overlap irritates the hell out of me. The context is usually close enough to make it confusing as hell for a while.