Hello Peter, are you aware that a TCP stack is not needed for this module as it's implemented in the chip already? And Q40 compatibility is not needed for a BBQL
of course I am aware. That's why I wrote "if
a native stack was
required" when replying to Derek.
But are you aware that QLwIP already contains a multitasking TCP/IP stack, so an on-chip stack saves no work?
I have no idea why you seem to call QLwIP Q40/Q60 specific. As I pointed out in Edinburgh, I already used it on a QL over serial line. The lowest layer is of course chip-specific, but the same goes for Wiznet.
My post was just meant to show the probably most simple hardware solution.
I am not in opposition to the Wiznet at all. Just notice that losing Q40, Q60 and Q68 compatibility will split TCP/IP development between the native hardware platforms. We would end up with three flavours:
1. TCP/IP stack running on PC (emulators)
2. TCP/IP stack running on QL (QLwIP)
3. TCP/IP stack running on a chip (Wiznet)
It is quite unrealistic to make the software interfaces compatible.
Kind regards, Peter