Can we bundle the microcode update directly with the kernel? Normally this kind of thing is anathema to the upstream kernel developers, they're historically big fans of mechanism in the kernel and policy in userspace, but they've chosen to flip that policy on its head for this specific case and put the policy in the kernel, too.
Could we / should we take the next step and bundle the microcode directly with the kernel? I'm not entirely sure what the implementation would look like, maybe we'd check it into the kernel package directly, maybe we'd still keep the microcode in its own source package and use it as a `Build-Depends:` for the kernel, and copy it that way... perhaps there's other, better, choices. I'm just curious if we could make this simpler by recognizing that the mechanism/policy split has been violated, and run with it. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2130658 Title: hashed microcode updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/2130658/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
