misk@sopuli.xyz to Technology@lemmy.worldEnglish · 3 days agoFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.comexternal-linkmessage-square285fedilinkarrow-up1645arrow-down110cross-posted to: news@lemmy.linuxuserspace.showframework@hardware.watchgadgets@lemmit.online
arrow-up1635arrow-down1external-linkFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.commisk@sopuli.xyz to Technology@lemmy.worldEnglish · 3 days agomessage-square285fedilinkcross-posted to: news@lemmy.linuxuserspace.showframework@hardware.watchgadgets@lemmit.online
minus-squaregravitas_deficiency@sh.itjust.workslinkfedilinkEnglisharrow-up3·2 days agoWell, more specifically: why didn’t they try to go for LPCAMM?
minus-squareenumerator4829@sh.itjust.workslinkfedilinkEnglisharrow-up1·1 day 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-squaregravitas_deficiency@sh.itjust.workslinkfedilinkEnglisharrow-up1·22 hours agoI thought LPCAMM was designed specifically to address the bandwidth and connectivity issues that crop up around high-bandwidth + low-voltage RAM?
minus-squaregrue@lemmy.worldlinkfedilinkEnglisharrow-up2·1 day agoFrom what I understand, they did try, but AMD couldn’t get it to work because of signal integrity issues.
Well, more specifically: why didn’t they try to go for LPCAMM?
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?
From what I understand, they did try, but AMD couldn’t get it to work because of signal integrity issues.