Great, thanks LGB and Bruce for the clarification! These are good news, transfering data will be very fast!
I am currently working on the DHCP implementation, but as soon as it makes sense I can start with the W5300 driver for the Enterprise.

My idea would be to do some kind of self modification on start-up for the I/O ports used inside the code (after the detection when you know what they would be modified to ...).

This is what I would do in any case. At least my W5100 driver for the Amstrad CPC (which would use indirect I/O as well) only has two routines, which really have to deal with the base I/O port: setup the address and return the data port; one for register memory access, one for RX/TX buffer access. The W5300 shouldn't be much more complex. So such an I/O port "relocator" is not a problem at all.

Congratulation Bruce! These are fantastic news!
I want to play battleship on my EP against another Z80, soon

Wow!!
I would appreciate it a LOT when you would do W5300 emulation in XEP128! Even if it wouldn't be 100% accurate it still helps us so much to speed up ethernet support for the EP! The modifications, which would then be needed for Bruces' upcoming hardware would be only limited to the little low-level driver routines, so that's not a problem at all. It's always cool to have the software already finished, before the hardware is available I am very interested in the exact data how to access the emulated W5300 and in writing and testing a driver with the help of your emulator! (I was already writing a driver for a planned Amstrad CPC W5100 project, which doesn't exist yet )
Regarding interrupts:
No, good news, SymbOS doesn't use them as well. It polls the active sockets, and with the W5300 it will be the same. So no sweat here!

Tomorrow we will have a beta release of several SymbOS network stuff, so the timing is great!

That's true, it detects the mouse during startup. It has to decide if it will handle the signals from control port 1 as coming from a joystick or from a mouse. If it's a mouse, it will stay in mouse mode, otherwise it will stay in joystick mode. For the MSX version I added a key combination to start this detection later again. It seems, that I have to do the same for the EP now, too
I never had this problem with MSX emulators btw. Here you always choose in the settings, what is connected at which control port (joystick or mouse or nothing). Can't you do the same in Xep128?

IIRC Bruce is using the indirect access, which is working with I/O ports. Did you already ask Bruce how it will be accessed?

During the last days a lot stuff happend. The Network Daemon is now fully configurable, and the new "Driver" tab shows the status of the LEDs of the currently used MSX W5100 card. EdoZ made a little video for demonstating this:

https://www.youtube.com/watch?v=gAHQ4fkgOMc

You can see, how especially TX, RX and Link react on EdoZ char typing in the Telnet console.
At the same time Trebmint completed a huge part of the network support in the Unify IDE. That made it possible to write a simple but fully working internet messenger, called the "Simple Messenger", for SymbOS with Unify, which only consists of 30 lines of code - the initial development took 5 minutes

And so today we were able to have this very special moment: I started two instances of the messenger as a server on my 8bit machine in Germany, and EdoZ from The Netherlands and NYYRIKKI from Finland connected as clients from their Z80 computers directly over the internet. So I had two chat sessions running on my Z80. As this worked well, NYYRIKKI and EdoZ opened a direct chat session as well. All three MSX were connected to each other at the same time!

(click to enlarge)

(click to enlarge)



TBH we had a lot fun again today!

But as I want to have it running everywhere I also created the "localhost" driver this week. It already supports TCP and a fake kind of DNS, which is fine for 90% of the apps.
This was a test on the Amstrad CPC:



Let's keep this all finished for a beta release end of this month And I am looking forward so much to the EP ethernet hardware!! (since April all work on this project is completely platform independant, so every line of code is for the EP as well!).