Page MenuHomeFreeBSD

FAQ: package was renamed cpudata-microcode
ClosedPublic

Authored by emaste on Aug 28 2023, 1:08 PM.
Tags
None
Referenced Files
F109441683: D41615.diff
Wed, Feb 5, 2:55 AM
Unknown Object (File)
Mon, Jan 27, 5:00 PM
Unknown Object (File)
Sun, Jan 26, 6:19 PM
Unknown Object (File)
Wed, Jan 8, 11:34 PM
Unknown Object (File)
Dec 13 2024, 3:53 PM
Unknown Object (File)
Nov 25 2024, 2:42 PM
Unknown Object (File)
Oct 18 2024, 12:42 PM
Unknown Object (File)
Oct 9 2024, 10:14 PM
Subscribers
None

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

emaste created this revision.
This revision is now accepted and ready to land.Aug 28 2023, 1:09 PM

Since we have cpu-microcode ports for both AMD and Intel, should we remove Intel(R)?

documentation/content/en/books/faq/_index.adoc
628
documentation/content/en/books/faq/_index.adoc
628

Or maybe "AMD and Intel CPU microcode updates"?

documentation/content/en/books/faq/_index.adoc
628

Depends on if we want to add other CPU vendors in the future. :-)

documentation/content/en/books/faq/_index.adoc
628

That makes sense since we don't want to mislead those with CPUs from other manufacturers.

Some other points to consider.

It will be key to find the appropriate balance between simple and precise. If you think this information is helpful, I can add it.

documentation/content/en/books/faq/_index.adoc
628

@lwhsu I don't think we want to keep extending this list if/when that happens as it would get too awkward, but for now I think listing AMD and Intel makes sense.

If we do add a third vendor we should probably extend this with a description of the individual cpu-microcode-<vendor> ports anyhow.

This revision was automatically updated to reflect the committed changes.

We could instruct users to install the port for their vendor, rather than the meta port that pulls in microcode for both vendors.

Yeah, we probably should have more extensive documentation on microcode and early loading, although it might go beyond a FAQ entry then -- maybe a separate article that's referenced from here?