A similar list for the memory map would be useful too, I have been wondering about this.

ETNET is adjustable for both, but the I/O location is realted to the memory location:

Memory (512k)	I/O (16 bytes)
20-3f	10-1f
40-5f	20-2f
60-7f	30-3f
80-9f	40-4f
a0-bf	50-5f
c0-df	60-6f
e0-fb*	70-7f

* special EP64 mode to make the RAM continuous for badly-written programs

So more briefly  the I/O is the first memory segment / 2.

(sorry I don't know how to make a table display better than that)

Imagine ONE, not to big card, attached to the Enterprise edge connector, which is also the power supply.
Inside, lots of memory, slots for memory card, connector for the disk (maybe even SSD), USB ports etc.
Outside, only one IDC connector for new, experimental devices.
No jumpers. All configured from the menu on the computer screen (such witchcraft is already Zozo ).
Dreamy ...

Hi pear,

If you want to include an ethernet interface in with that lot the module I'm using (datasheet) only needs /CS, /RD /WR (and address & data lines of course). The tricky part is the code but I can help you out there just need 2 segments from a 29C010 FLASH

B.

What else (serial card, EPNET, ZX Emulator, internal) ?

I/O port list from Lgb
And some addition:
-Z180 ports moved to 40-7Fh at the initialisation
-08-0Fh used by the SID sound card

E0h-E7h: IDE-CF 8-bit

Which ports use an SD card reader ?
Well, how many card readers at the same time you want to use?
As a last resort, you can still take advantage of the full 16-bit addressing ports.

Which ports use an SD card reader ?
Well, how many card readers at the same time you want to use?
As a last resort, you can still take advantage of the full 16-bit addressing ports.

No port is used. SD card reader is a "BASIC cartridge replacement" like solution and uses normal memory addresses instead of I/O operations.

By the way, what's the advantage of CF over SD? Since the SD solution for EP is already well established, I am curious what CF can give that it's better. If it's better at all Sorry for the dumb question, I've never had CF card, and I never used, that's why I ask this.

To read the CF card does not need additional processor that handles the SPI protocol. Nothing else.

I see, but the SPI protocol is handled by a CPLD in the SD cartridge, so there you don't need to "talk" SPI directly by the EP either. Or you mean, that you can save a CPLD here ...

Ok, I may get the point now, I am sorry I thought the CF card is needed on the all-in-one stuff because there is some fundamental problem with the already existing SD card cartridge solution and that was what I didn't understand ...

I think, the actual (or near future) variety in hardware is infinitely better than the lonely desert of the past.

And the best is that all the bits will be compatible.