misk@sopuli.xyz to Technology@lemmy.worldEnglish · 2 days agoFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.comexternal-linkmessage-square272fedilinkarrow-up1641arrow-down110cross-posted to: framework@lemmy.mlsffpc@lemmy.world
arrow-up1631arrow-down1external-linkFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.commisk@sopuli.xyz to Technology@lemmy.worldEnglish · 2 days agomessage-square272fedilinkcross-posted to: framework@lemmy.mlsffpc@lemmy.world
minus-squarewise_pancake@lemmy.calinkfedilinkEnglisharrow-up19·edit-21 day agoQuestion about how shared VRAM works So I need to specify in the BIOS the split, and then it’s dedicated at runtime, or can I allocate VRAM dynamically as needed by workload? On macos you don’t really have to think about this, so wondering how this compares.
minus-squarebrucethemoose@lemmy.worldlinkfedilinkEnglisharrow-up4·24 hours agoOn my 7800, it’s static. The 2GB I allocate is not usable for the CPU, and compute apps don’t like it “overflowing” past that. This is on Linux, on a desktop, ASRock mobo. YMMV.
minus-squarepriapus@sh.itjust.workslinkfedilinkEnglisharrow-up3·22 hours agoIt will most likely be dynamic, with the option to statically set it.
Question about how shared VRAM works
So I need to specify in the BIOS the split, and then it’s dedicated at runtime, or can I allocate VRAM dynamically as needed by workload?
On macos you don’t really have to think about this, so wondering how this compares.
On my 7800, it’s static. The 2GB I allocate is not usable for the CPU, and compute apps don’t like it “overflowing” past that.
This is on Linux, on a desktop, ASRock mobo. YMMV.
It’s typically dynamic
It will most likely be dynamic, with the option to statically set it.