Is there a reason to use CpuId?

[halentin]

I ran into issues with LinearSolve failing to precompile on our 32-Bit-Tests. It appears the issue stemmed from an upstream bug m-j-w/CpuId.jl#62 (comment).
I submitted a PR that should fix it upstream, but is there even any good reason to use CpuId at all in this case?
It appears CpuId is only used to check for "EPYC" in the CPU-Name:

LinearSolve.jl/src/LinearSolve.jl

Line 49 in 1c30db0

if Preferences.@load_preference("LoadMKL_JLL", !occursin("EPYC", CpuId.cpubrand()))

On both machines i tested it on (one having an EPYC-CPU), Julias builtin Sys.cpu_info()[1].model returns the same String (minus some spaces) as CpuId.cpubrand().
So maybe this dependency could be completely removed and replaced by the builtin function?

[ChrisRackauckas]

This was just because that's how @chriselrod showed me how we could do it. If you have a way to do it without CpuId please make a PR.

[chriselrod]

This was just because that's how @chriselrod showed me how we could do it. If you have a way to do it without CpuId please make a PR.

I also showed an example using cpubrand.