@misk@sopuli.xyz to Technology@lemmy.worldEnglish • 7 months agoFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.comexternal-linkmessage-square282fedilinkarrow-up1644cross-posted to: framework@lemmy.mlnews@lemmy.linuxuserspace.showsffpc@lemmy.world
arrow-up1644external-linkFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.com@misk@sopuli.xyz to Technology@lemmy.worldEnglish • 7 months agomessage-square282fedilinkcross-posted to: framework@lemmy.mlnews@lemmy.linuxuserspace.showsffpc@lemmy.world
minus-square@gravitas_deficiency@sh.itjust.workslinkfedilinkEnglish3•7 months agoWell, more specifically: why didn’t they try to go for LPCAMM?
minus-square@enumerator4829@sh.itjust.workslinkfedilinkEnglish1•7 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@gravitas_deficiency@sh.itjust.workslinkfedilinkEnglish1•7 months agoI thought LPCAMM was designed specifically to address the bandwidth and connectivity issues that crop up around high-bandwidth + low-voltage RAM?
minus-square@grue@lemmy.worldlinkfedilinkEnglish2•7 months 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.