There were sellers buying the smallest RAM units, changing the RAM chips, and then reselling them as the higher RAM SKUs. The sellers who do this don’t always care to use good RAM chips and may even use QA reject parts. When the unit doesn’t work correctly, the anger and RMA requests are directed back at the Raspberry Pi foundation.
"Each chip is programmed with the timing settings and storage size settings of just the RAM we ship it with, and doesn't know how to boot with anything else." I don't know if you could call that "blocking." I mean you could call it that but I don't know if that's legally what it would be.
So European institution following this discussion would be wise to ASAP formally request RP Foundation to describe it either as a blocking security mechanism, or just a compatibility issue.
Between current inaction and eventual action, it settles the position of RP foundation, so they can't switch back and forth between "these people are circumventing security" vs "its just an unintended incompatibility", as long as they don't reveal their position its neither here nor there.
Aurornis · · focus · HN ↗
DoctorOetker · · focus · HN ↗
Aurornis · · focus · HN ↗
smilespray · · focus · HN ↗
Aurornis · · focus · HN ↗
smilespray · · focus · HN ↗
iso1631 · · focus · HN ↗
smilespray · · focus · HN ↗
Aurornis · · focus · HN ↗
smilespray · · focus · HN ↗
asdfasgasdgasdg · · focus · HN ↗
DoctorOetker · · focus · HN ↗
Between current inaction and eventual action, it settles the position of RP foundation, so they can't switch back and forth between "these people are circumventing security" vs "its just an unintended incompatibility", as long as they don't reveal their position its neither here nor there.