119
Valve still waiting on a 'generational leap' for Steam Deck 2 - but it's coming
(www.gamingonlinux.com)
this post was submitted on 16 Oct 2024
119 points (99.2% liked)
PC Gaming
8563 readers
678 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That sounds like a nightmare to code for.
That the kernel developers to decide, the deve wouldn't need to change angthingz but i doubt the idea too, how can sincronize the arm and x86? How to you handle libraries of the different architectures
The libraries would probably be easy. We’ve already got x86 and amd64 libraries on the same machine, but the kernel I imagine would be awful. Would two kernels have to run on the same machine? What about memory access? What about the scheduler? Would it really be more efficient than emulation? For every x86 instruction, there is either an equivalent instruction or an equivalent set of instructions for ARM.
Correct me if I'm wrong, but afaik, applications talk through APIs. It shouldn't matter if app runs x86 and kernel is ARM
But the code that loads other code (launches an app, switches to it, etc) needs to be running on the same CPU, afaik.