Jeremy Cline's Blog

Another Flock to Fedora conference has come and gone, and like last year, this one was held in Prague.

Way back in September I apologized for the gap since my last update.

About seven years ago, a ticket was filed noting aarch64 systems were shipping with Secure Boot enabled, and that Fedora should start signing its boot path to support these devices out of the box.

It’s been a while since my last update about content signing in Fedora, so I figured I should write one before the end of this month.

In my last post on Fedora’s signing infrastructure, I ended with some protocol changes I would be interested in making.

Over the past few months I’ve spent some time on-and-off working on Sigul and some related tools.

For the last few months, one of the things I’ve been working on in Fedora is adding support for SecureBoot on Arm64.

While at Flock to Fedora 2024, someone noted, to paraphrase a conversation from a month ago, that working with Fedora’s messaging infrastructure seemed more intimidating now that it’s transitioned from ZeroMQ to AMQP.

In the previous post, we learned what HDR is: a larger luminance range that requires more bits per component, new transfer functions to encode that luminance, and potentially some metadata.

In recent months I have been investigating high dynamic range (HDR) support for the Linux desktop, and what needs to be done so that a user could, for example, watch a high dynamic range video.