4 ms·

> How much work would be required ... Can't speak to his NIC emulation (unless he borrowed it from jor1k), but otherwise it'd take roughly a flight from PDX to

> How much work would be required ... Can't speak to his NIC emulation (unless he borrowed it from jor1k), but otherwise it'd take roughly a flight from PDX to CHS for the NIC, plus another 2-3 hours for a dead simple virtual switch, plus a few days of watching the switch crash in various odd ways while HN, Reddit, and Slashdot beat it up. Edit: If anyone is keen to experiment around with v86, jor1k, or a similar project and you want plug-n-play network support, I maintain the websocket proxy used by jor1k (and probably used by v86 in some demo or another). As far as I'm concerned, please no commercial use (I've made it stupid easy to host your own for that), but otherwise as long as you're not doing stupid things with it that will cause me to lose my hosting account, go nuts! To use it just start sending/reading ethernet frames to/from wss://relay.widgetry.org/. Also if you do use it, please flick me a message (e-mail is in my profile) to let me know what you're doing with it and how you're getting on.

IamHWengineer 10y ago
Bro, How much time does it need to replicate a project like V86? I have close to 6 years in C++. I work for intel/amd but not on emulation, I do HW design. I want to know if this can be completed in 4-6 months doing work on the night only.. TIA.
- benjamincburns 10y ago
  No clue how far you'd get, but I'd think you could come up with something interesting in that time frame. It's a lot more approachable than you might think. I'm not well acquainted with Copy, so I don't know how long the bulk of the work took him. I'd suggest pinging him or Sebastian Macke (the guy behind jor1k) if you'd like to know more. My understanding was that Sebastian chose OpenRISC in part because of the simplicity of the instruction set. I got the impression that this made the task a bit more approachable than x86 emulation, and gave him more hope for achieving a good emulation speed. And, in fact, it's quite snappy considering what it is. However I think he had to put a fair amount of effort into gcc and glibc debugging to really get it off the ground, and I know that he used to put a bunch of time into tuning the cores for each new version of asm.js, though I'm not sure how in flux it is these days.
- s-macke 10y ago
  Just take a look at the link to the third talk I gave a few days ago about jor1k. https://github.com/s-macke/jor1k/wiki/Technical-details https://github.com/s-macke/jor1k/wiki/Technical-details This talk give a few details about time frames and what someone has to do to emulate such a machine. If it is just about booting Linux you can do it in around 2000 lines (first commit of jor1k) if you take an easy architecture such as OpenRISC. Take a look at slide no. 10 and you might get an idea about the complexity of the other architectures. Slight 15 and 16 give you an idea why OpenRISC can be emulated much faster than any other architecture. A downside of such an non-mainstream CPU is less support. Indeed as Benjamin said, at least 50% of the time went into bugfixing and enhancing the toolchain. In the end the MIPS architecture might be optimal for a fast emulation and a well maintained toolchain.

IamHWengineer 10y ago

Bro, How much time does it need to replicate a project like V86? I have close to 6 years in C++. I work for intel/amd but not on emulation, I do HW design. I want to know if this can be completed in 4-6 months doing work on the night only.. TIA.

benjamincburns 10y ago
No clue how far you'd get, but I'd think you could come up with something interesting in that time frame. It's a lot more approachable than you might think. I'm not well acquainted with Copy, so I don't know how long the bulk of the work took him. I'd suggest pinging him or Sebastian Macke (the guy behind jor1k) if you'd like to know more. My understanding was that Sebastian chose OpenRISC in part because of the simplicity of the instruction set. I got the impression that this made the task a bit more approachable than x86 emulation, and gave him more hope for achieving a good emulation speed. And, in fact, it's quite snappy considering what it is. However I think he had to put a fair amount of effort into gcc and glibc debugging to really get it off the ground, and I know that he used to put a bunch of time into tuning the cores for each new version of asm.js, though I'm not sure how in flux it is these days.
s-macke 10y ago
Just take a look at the link to the third talk I gave a few days ago about jor1k. https://github.com/s-macke/jor1k/wiki/Technical-details https://github.com/s-macke/jor1k/wiki/Technical-details This talk give a few details about time frames and what someone has to do to emulate such a machine. If it is just about booting Linux you can do it in around 2000 lines (first commit of jor1k) if you take an easy architecture such as OpenRISC. Take a look at slide no. 10 and you might get an idea about the complexity of the other architectures. Slight 15 and 16 give you an idea why OpenRISC can be emulated much faster than any other architecture. A downside of such an non-mainstream CPU is less support. Indeed as Benjamin said, at least 50% of the time went into bugfixing and enhancing the toolchain. In the end the MIPS architecture might be optimal for a fast emulation and a well maintained toolchain.