“The ceo kind of explains why in this video.”
Framework CEO explains memory limitation from the AMD chip.
Full comment
this video The ceo kind of explains why in this video. In essence it seems to be a limitation of the chip from AMD
My Framework Investment Should NOT Have Worked Out
2.4M views · Feb 25, 2025 · 17:37 · 0 HN recommenders · 5 mentions · discussed 2025
Linus Tech Tips covers Framework's newly announced devices, including its first desktop, with comments from Framework's CEO about the company's design decisions.
Why Hacker News points people here: Used as a source for the Framework CEO's explanation of why the desktop's memory could not be socketed or modular.
“This sort-of-interview of Nirav Patel (ceo of framework) explains in a bit more detail”HN comment, 2025
What Hacker News said 5
Source for Framework laptop CPU details.
Full comment
The two CPU models are i3-1215U and i5-1334U [1] which are 15 W parts with 2 P cores. They should be OK. [1] this video
“they tried and AMD assigned an engineer on getting modular memory to work and decided it's not possible.”
CEO explains why modular memory was not possible.
Full comment
According to the Framework CEO on the Linus Tech Tips video about this thing [1], they tried and AMD assigned an engineer on getting modular memory to work and decided it's not possible. Unless there's another company out there shipping this CPU with replaceable memory, I'll believe them. Even with LPCAMM, physics just doesn't work out. Of course, there are plenty of slower desktops you can buy where all the memory can be swapped out. If you want a repairable desktop like that, you're not stuck with Framework in the same way you would be with laptops. You'll probably struggle to get the same memory bandwidth to make full use of AMD's chips, though. [1]: this video
“This sort-of-interview of Nirav Patel (ceo of framework) explains in a bit more detail”
Framework CEO explains why socketed RAM was not feasible.
Full comment
As stated previously, the sockets reduce signal integrity, which doesn't necessarily make them "bad," but is why Framework wasn't able to used socketed ram to maximize the potential of this CPU. This sort-of-interview of Nirav Patel (ceo of framework) explains in a bit more detail: this video Basically, they need to use LPDDR5X memory, which isn't available in socketed form, because of signal integrity reasons. Which means you won't see an improvement if you solder your ram directly, I think mostly because your home soldering job will suffer signal integrity issues, but also because your RAM isn't LPCAMM and isn't spread across a 256 bit bus.
“here's a quote from the CEO explaining (to some degree) the choice”
CEO quote on why LPCAMM does not work with Strix Halo.
Full comment
I agree, but here's a quote from the CEO explaining (to some degree) the choice: “So we did actually ask AMD about this the first time they told us about Strix Halo. It was literally our first question: ‘How do we get modular memory? We are Framework after all.’ And they didn’t say no actually, they did assign one of their technical architects to really really go deep on this—they ran simulations, they ran studies, and they just determined it’s not possible with Strix Halo to do LPCAMM. The signal integrity doesn’t work out because of how that memory’s fanning out over the 256-bit bus.” (from this video via link )