Mario Limonciello
Mario Limonciello
> (I assume making fwupd talk to GRUB/systemd boot is off the table?) What do they have to do with it? It's a kernel module option. > Just a thought:...
I thought we actually already had a mapping like that for this reason TBH! So go ahead if it's indeed missing in fwupd.
https://github.com/fwupd/fwupd/blob/main/libfwupd/fwupd-bios-setting.c#L386
You shouldn't need to, because we use a lowercase compare and [g_strrstr](https://docs.gtk.org/glib/func.strrstr.html) which will match both enabled/EnABLE/enableD and all those permutations. If you find another word that isn't covered for...
> Except that Richard has an API wrapping all of the attributes stuff, Just as a pedantic correction; the fwupd project has an API. Richard doesn't own it, neither do...
One more thing I want to share in case you don't know. fwupd also offers a policy that will enforce BIOS settings at startup. https://fwupd.github.io/libfwupdplugin/bios-settings.html#firmware-setting-policies
> This is neat! We basically do the same thing in https://github.com/purpleidea/mgmt/ -- if you specify a key, not only will it set that value, but it watches it with...
As a potential solution without needing to change the UI - how about if you just add VRAM + GTT and show that?
> As a potential solution without needing to change the UI - how about if you just add VRAM + GTT and show that? I've opened a PR that does...
Yeah; that's why I set the change to only apply on APU. Existing policy to only show VRAM is for dGPU.