Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
Hmm. My impression was that Nintendo's N64 emulator does exactly that, hooking into and replacing system library calls with native code for the emulating platform. For a system like CDi where the hardware is *intentionally* unspecified, it seems potentially fruitful?
You're thinking of high-level emulation (HLE), which was pioneered in the late 90's with the N64 emulator, UltraHLE. Nintendo went that route for Virtual Console primarily for speed reasons, not due to a lack of hardware documentation on their part.
It's not quite as simple as just dropping in a new library, and away you go. The N64 had a vector coprocessor (the RSP) which handled the calculation side of both the graphics and audio stack. HLE-ing the N64 still required reverse-engineering the routines uploaded to the RSP.
Overall, there were roughly 20-40 unique sets of microcode routines. Some were used by only one or two games, some were used by a fairly large chunk. So it's not entirely the same situation with the CD-i.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
