The change is valid but I think we should drop this part. This information is not reliable. It uses legacy registers that were wrong on some on my hosts. I do think no one uses this part.

I see your proposal around i2c-tools which has some interest to report the actual capability of the dimm but not how the memory controller is configured.
This code was about the memory controller which is very vendor/product dependant.
So switch to #162 would be way better

@ErwanAliasr1 do you think we should just remove this code then?
The conversion to i2c-tools is a big change and I thought to extract the old code from detect.py first.

@elfosardo I imlplemented this when I was at enovance for my own usage. I'm pretty sure no one knows where this tool is located today, so the code is dead and useless. I'd vote for dropping this part.

removing the code in #164
I'll rebase this on top of that and use it to use i2ctools to get the memory info

#164