Re: WANTED: Translator from German

On 29 Jul., 22:42, Peter Dassow <z8...@xxxxxxxx> wrote:

Ok, let's clarify it now... just to have a network stack isn't enough to
do anything else but processing packets.

You have much more than a network stack, you have a BSD-like Socket-
Interface ready to use the rfc-protocols, this is like call a bdos-
function in CP/M.

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.

Yes - in principle, there a 3 logical levels, low level for PIO-
communication with the commands of the KCNET-Protocol, second level
for alter the registers of the stack and third the socket commands.
For implementing a common rfc you need only level 3 for the
communication parts of the rfc.

I wrote the 22k CPMNET for testing the interface on all 3 levels in a
menu-driven program and it has already a DHCP-Client, PING-Client and
TFTP CLIENT+Server - with this little effort (Memory) you are ready to
transfer files in your whole network to and from any tftp-client or -
server and this with the given speed of 22kB/s (PIO-limitation) - your
CP/M computer has no chance, to write the UDP-Packets of 512 Bytes
with this speed, my HDD-Write-Speed is with ZSDOS/Z-System and GIDE
about 2-3 kB/s.


So it's a special kind of hardware interface just
for use with the KC85?

You can use the interface with a standard Z80-PIO, thats all. But you
must build the interface and you must have a PIO or assemble an
additional PIO in your Z80-System, thats your part of work. The CPMNET
is ready for use:
- set the symbol KC85 to NO
- register the PIO-adress of your system
- control used terminal codes on top of the program
Now make the COM and it should work - of course without guarantee from
my side, it is a hobby-project, not a commercial product.

We (KC-Club) are now developing a special modul for the KC85 - this
modul is a special kind of hardware.
.

Relevant Pages

  • Re: [PATCH] Ethernet cleanup; 802.1p input and M_PROMISC
    ... IFF_DRV_RUNNING can be a way for the interface driver to tell us: ... shouldn't be pumping traffic into the network stack. ... ether_input/ether_demuxsplit was to accomodate Netgraph. ...
    (freebsd-net)
  • Re: Special schedulers, one CPU only kernel, one only userland
    ... >> However I am still unclear on what happens if a detach() is racing with the ... > Note that we first down the interface via fxp_stopand then we unhook it ... > ether_ifdetachthe network stack can't get to the fxp device anymore. ...
    (freebsd-arch)
  • Re: WANTED: Translator from German
    ... The KC85 goes to ON-LINE ONES. ... have its good old KC85 at the network and/or Internet. ... ready and encases the underlying driver functions of the KCNET interface. ... TCPIP and Ethernet with a Windows or a Linux PC. ...
    (comp.os.cpm)