Relevant implementation/design discussions are logged in the GH PRs, if anyone is curious:
Cherry-pick of dbus interface from master into resolute (includes links to all original dbus PR discussions): https://github.com/canonical/ubuntu-drivers-common/pull/178 MIDR detection PR: https://github.com/canonical/ubuntu-drivers-common/pull/173 dmidecode detection PR: https://github.com/canonical/ubuntu-drivers-common/pull/172 In addition to the human and copilot reviews in the PRs, I also ran the Resolute [0] and Stonking [1] Ubuntu upload diffs through a review session with GPT 6 Astra to look for potential regressions, and found no major areas of concern. The only items flagged were not relevant to u-d-c's known or planned usages. One finding was of interest - some functions like list_gpgpu have been dead code since a 2020 refactor - so I'll plan to remove those in future devel releases. [0] https://launchpad.net/~mitchellaugustin/+archive/ubuntu/ubuntu-drivers-proposed/+files/ubuntu-drivers-common_1%3A0.10.9_1%3A0.10.9+ubuntu0.1.diff.gz [1] https://launchpad.net/~mitchellaugustin/+archive/ubuntu/ubuntu-drivers-proposed/+files/ubuntu-drivers-common_1%3A0.10.11_1%3A0.10.12.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2165071 Title: Unable to detect packages to install based on CPU type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2165071/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
