@[email protected] to [email protected]English • 2 months agoFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.comexternal-linkmessage-square284fedilinkarrow-up1643cross-posted to: [email protected][email protected][email protected]
arrow-up1643external-linkFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.com@[email protected] to [email protected]English • 2 months agomessage-square284fedilinkcross-posted to: [email protected][email protected][email protected]
minus-square@[email protected]linkfedilinkEnglish3•2 months agoWell, more specifically: why didn’t they try to go for LPCAMM?
minus-square@[email protected]linkfedilinkEnglish2•2 months agoFrom what I understand, they did try, but AMD couldn’t get it to work because of signal integrity issues.
minus-square@[email protected]linkfedilinkEnglish1•2 months agoBecause you’d get like half the memory bandwidth to a product where performance is most likely bandwidth limited. Signal integrity is a bitch.
minus-square@[email protected]linkfedilinkEnglish1•2 months agoI thought LPCAMM was designed specifically to address the bandwidth and connectivity issues that crop up around high-bandwidth + low-voltage RAM?
Well, more specifically: why didn’t they try to go for LPCAMM?
From what I understand, they did try, but AMD couldn’t get it to work because of signal integrity issues.
Because you’d get like half the memory bandwidth to a product where performance is most likely bandwidth limited. Signal integrity is a bitch.
I thought LPCAMM was designed specifically to address the bandwidth and connectivity issues that crop up around high-bandwidth + low-voltage RAM?