Re: WANTED: Translator from German

susowa wrote:
[...]
To Peter:

ftp://ftp.ucsd.edu/hamradio/packet/tcpip/
This is only an IP-Stack - Not TCPIP and this is a very big
difference.

I didn't say that your project is the same, but anyway, thanks for the clarification.

also a "rerolled" version at http://www.kc85.susowa.homeftp.net/
>> named "KCNET", now adapted for a KC85 and additional interface hardware.

This is very incorrect! I haven't adapted or rerolled something!

The transformation of the driver C-Sources from WIZnet to Z80-ASM was
done by myself, so I could not understand your statements - did you
read the GERMAN articels about the development of the "KCNET" ?

I guessed you didn't wrote the whole thing from scratch. That should it mean.

Now to the technical details of your blog-article:

These tries consumes a lot of memory from the TPA of CP/M

I need 388 Bytes for the device-driver.
And for now exact 1711 byte for the socket-driver.

Take a CP/M with 50k TPA - you have 49 101 Byte for your Programm -
how many CP/M-programs do you know with such a size ?

Ok, let's clarify it now... just to have a network stack isn't enough to do anything else but processing packets.
Also, what I now understand (I will try to correct this in my blog) is, on the Z80 side there almost nothing but interfacing stuff.

and the execution speed is awful

Is a RAM-RAM transfer speed of about 22 kB/s with a 1,75 MHz computer
"awful" for you ?
Wich CP/M-Device can write data with this speed?

No, that would be fast. But is all done with a RAM-2-RAM transfer ?

It looks to me, that you didn't read the KCNET-articles in depth and
wrote your opinion down - you can do so, but it is not the reality and
it is not fair also - this is not a software-stack, but a hardware
stack with a conveniently software-interface to Z80-ASM.

Ok, I take this over, it's a hardware stack with a convinient software-interface. So it's a special kind of hardware interface just for use with the KC85 ? I am a bit confused now, because Emmanuel talks about a TCP/IP stack ...

So far - many greetings frrom

"susowa"

Anyway, I appreciate any efforts related with these old stuff, so please do not understand I would like to reduce your work. Still great stuff.

Regards
Peter

--
* A blog about vintage computers and CP/M - http://www.z80.eu/blog
.

Relevant Pages

  • Re: XP sometimes balks on boot-up
    ... to catch this trap. ... Memory corruption, other hardware ... The most common cause of this is hardware memory corruption. ... A kernel stack overflow. ...
    (microsoft.public.windowsxp.general)
  • Re: using MISC (post 1987 Forth hardware) opcodes
    ... This clearly had nothing to do with hardware in that an ELSE is ... Like dozens of other things Chuck explained his reasoning. ... for those interested in the conceptual foundation ... people ask why we de-emphasis the use of the stack. ...
    (comp.lang.forth)
  • Re: !p+, and thank you Jeff
    ... and looking at the SEAforth instruction set table, ... But like many other assumptions about what hardware will be ... with than mainframe style software. ... Stack depth managment is usually the biggest imaginary ...
    (comp.lang.forth)
  • Re: hardware errors, do C and Forth need different things in hardware?
    ... hardware is to people who are thinking C software ... need or want the sort of complications that this code avoids. ... If it confuses solutions for bugs it will introduce REAL bugs. ... back from the stack is greater than the size of the stack. ...
    (comp.lang.forth)
  • Re: write statement output buffer flush off on Sun
    ... > routine is usually greater than the cost of checking for a nonzero ... > are passed on the stack, passing the addresses involves memory traffic. ... branch - and it may involve additional instructions on some ... hardware, a conditional branch costs about the same whether it's ...
    (comp.lang.fortran)