You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Xemu/MEGA65 has ethernet emulation (using TAP driver in Linux, so it's kinda Linux specific) however:
It emulates an older behaviour of MEGA65 which has changed since then, and does not work this way any more
It had bugs, since it was not thread-safe
No IRQ was emulated
Since it uses Linux TAP driver, it's Linux specific (it's possible that some other UNIX-like system works, even MacOS, but surely not Windows, for example)
It would be nice to have a "fake" DHCP server in Xemu, so if a MEGA65 software uses DHCP to get its IP, it will get one. it would greatly decrease the network setup complexity needed for Xemu without the requirement of a real DHCP server bound to the tap interface which Xemu can use
This issue is intended to remedy at least point 1 from the list above, ideally point 2 as well. For point three, a totally different approach should be used (or "as well"), what I have no idea about, yet (what can use on Windows for similar purpose, if it's possible at all).
Currently mega65-core has some issues with ethernet: MEGA65/mega65-core#523 It's wise to see it being "perfect" then trying to refactor my ethernet emulation to match that (so it can be compared) with the changes.
The text was updated successfully, but these errors were encountered:
So far, "ethernet I/O mode" (much like VIC-4 I/O mode but with Ethernet
registers in the high 2K of I/O space) was largely ignored by Xemu. This
commit tries to introduce a more-or-less correct support. Note, this
alone still not enough to have working ethernet emulation again
(see issue #242 for that ...).
Xemu/MEGA65 has ethernet emulation (using TAP driver in Linux, so it's kinda Linux specific) however:
This issue is intended to remedy at least point 1 from the list above, ideally point 2 as well. For point three, a totally different approach should be used (or "as well"), what I have no idea about, yet (what can use on Windows for similar purpose, if it's possible at all).
Currently mega65-core has some issues with ethernet: MEGA65/mega65-core#523 It's wise to see it being "perfect" then trying to refactor my ethernet emulation to match that (so it can be compared) with the changes.
The text was updated successfully, but these errors were encountered: