From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Osmialowski Subject: Re: Obsolete documentation? Date: Mon, 17 Feb 2020 16:07:54 +0100 (CET) Message-ID: References: <85e27a46-034f-f927-9169-e633c18909e8@gmail.com> <06A225A8D60249BC967DAD92CDEC4AF6@PotthastHP> <718029432.180460.1581950843768@com4.strato.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="98048-624174455-1581952075=:19553" Return-path: In-Reply-To: <718029432.180460.1581950843768@com4.strato.de> Sender: linux-8086-owner@vger.kernel.org List-ID: To: Georg Potthast 2 Cc: Paul Osmialowski , Derek Johansen , "Marc-F. Lucca-Daniau" , ELKS This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --98048-624174455-1581952075=:19553 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Umh... To configure Telix under DOS you need to provide the first I/O port = and IRQ, so I guess it talks to the hardware directly. Also the other side = (minicom under Linux) works according to selected communication speed with = Telix on the XT side. Also, ELKS has I/O ports hardcoded, so I doubt it=20 communicates with BIOS for serial I/O, see in=20 elks/arch/i86/drivers/char/serial.c: static struct serial_info ports[NR_SERIAL] =3D { {(char *)0x3f8, 4, 0, DEFAULT_LCR, DEFAULT_MCR, NULL}, {(char *)0x2f8, 3, 0, DEFAULT_LCR, DEFAULT_MCR, NULL}, {(char *)0x3e8, 5, 0, DEFAULT_LCR, DEFAULT_MCR, NULL}, {(char *)0x2e8, 2, 0, DEFAULT_LCR, DEFAULT_MCR, NULL}, }; static char irq_port[NR_SERIAL] =3D { 3, 1, 0, 2 }; Port 3f8 is the one I entered in Telix under FreeDOS. On Mon, 17 Feb 2020, Georg Potthast 2 wrote: > Hi Paul, > I recall that DOS used the BIOS to send and receive data via the serial p= ort. This resulted in a usable speed of 1200 baud max. Lower speeds were mo= re reliable. Therefore all communication programs used interrupt driven dat= a input and no DOS or BIOS calls. I assume ELKS also uses the BIOS and ther= efore you are limited to 1200 baud in case of a 8086 processor and have to = expect missing data then. >=20 > Georg >=20 > > Paul Osmialowski hat am 17. Februar 2020 um 00:26 = geschrieben: > >=20 > >=20 > > Hi Georg, > >=20 > > I'm using null-modem cable I've made myself and been using it for years= =20 > > (it corsses-over Rx/Tx and hardware control lines). It works nicely wit= h=20 > > Telix running under FreeDOS on my XT and minicom on 'big' Linux, at spe= ed=20 > > 115200, which is the top speed for 8250 chip on the XT side. > >=20 > > With ELKS it's not that nice. I've managed to configure getty in=20 > > /etc/inittab to use /dev/ttyS0 at the default speed (9600bps), and it=20 > > kinda worked, except it was losing bits from time to time. I'd removed = > > getty line from /etc/inittab for other experiments, then I've tried to = > > 'cat' some text files between ELKS and Linux (and vice versa), and=20 > > although a text sent from ELKS to Linux looked good, the other way roun= d=20 > > it was disaster. I've tried different speeds (using 'stty' on both side= s).=20 > > Finally, it looked almost OK at 1200bps, but still I had an impression,= =20 > > bit-banging serial port on my old ZX Spectrum +3 offered better=20 > > communication stability at 4800bps than this! > >=20 > > Eventually, I've managed to establish SLIP connection between ELKS and = > > Linux, with telnetd running on ELKS, and I could open telnet connection= =20 > > that worked for a while... not too long though. I guess, serial connect= ion=20 > > support must be looked upon in ELKS before doing experiments with SLIP. > >=20 > > Trying to follow your instructions, I've encountered some problems with= =20 > > the 'ifconfig' line: > >=20 > > - there's no 'up' param in your example; usually I'm adding it after th= e=20 > > interface name (e.g. 'ifconfig sl0 up ....'), > >=20 > > - the destination address option is different in various versions of=20 > > ifconfig; in your example it was 'pointtopoint', but my 'ifconfig' didn= 't=20 > > like it; turned out, in my case it should be 'dstaddr' (which some goog= led=20 > > pages listed as obsolete). > >=20 > > Thanks, > > Paul > >=20 > > On Sun, 16 Feb 2020, Georg Potthast wrote: > >=20 > > > ELKS does NOT have a special version of SLIP. Therefore you can commu= nicate > > > with any Linux host provided you manage to configure this. I would re= commend > > > to follow my instructions first to get an understanding how to set th= is up. > > > Then make a serial cross over connection cable and test that using two > > > terminal programs on each side. Getting the wires linked correctly and > > > providing the hardware signals is not trivial for someone who has not= done > > > that before. If you can send across what you type you can start confi= guring > > > SLIP over this line. > > >=20 > > > Georg > > >=20 > > > -----Urspr=FCngliche Nachricht----- From: Paul Osmialowski > > > Sent: Sunday, February 16, 2020 7:37 PM > > > To: Georg Potthast > > > Cc: Paul Osmialowski ; Derek Johansen ; Marc-F. Lucca-Daniau ; ELKS > > > Subject: Re: Obsolete documentation? > > >=20 > > > Hi Georg, > > >=20 > > > Will it connect to SLIP/CSLIP interface as implemented in normal Linux > > > kernel (CONFIG_SLIP)? > > >=20 > > > Thanksm > > > Paul > > >=20 > > > On Sun, 16 Feb 2020, Georg Potthast wrote: > > >=20 > > > > I wrote a SLIP documentation which shows how to setup a SLIP connec= tion > > > > between an ELKS system running in QEMU und the host where QEMU is r= unning. > > > > You > > > > could send data from the host to the ELKS system and vice versa. Th= is is > > > > this > > > > document: > > > > elks/Documentation/html/user/setup_slip.html > > > > To me this seemed easier to set up instead of two ELKS systems conn= ected > > > > with > > > > a cross-over serial cable. > > > >=20 > > > > Georg > > > >=20 > > > > -----Urspr=FCngliche Nachricht----- From: Marc-F. Lucca-Daniau > > > > Sent: Sunday, February 16, 2020 6:05 PM > > > > To: Paul Osmialowski ; Derek Johansen > > > > Cc: ELKS > > > > Subject: Re: Obsolete documentation? > > > >=20 > > > > Hello Derek and Paul, > > > >=20 > > > > ELKS is indeed still SLIP capable : > > > > https://github.com/elks-org/elks/issues/304 > > > >=20 > > > > One has just to change the command line of 'ktcp' to remove Etherne= t and > > > > put back SLIP. > > > >=20 > > > > Documentation is quite outdated. Georges made an effort to document > > > > Ethernet and some other things while debugging networking features,= but > > > > there are still many legacy documents that need to be reorderer and= updated. > > > >=20 > > > > Thanks, > > > >=20 > > > > MFLD > > > >=20 > > > >=20 > > > > Le 16/02/2020 ? 12:08, Paul Osmialowski a =E9crit : > > > > > So what happened to SLIP support in ELKS? 8-bit ISA ethernet cards > > > > > (with RJ-45 connector) are very rare (I have only one of them, wo= rk > > > > > nicely > > > > > under FreeDOS and in theory it should be supported by ELKS's ne2k= > > > > > driver, > > > > > but it isn't). Within my one more XT machine to play with ELKS, s= erial > > > > > port is the only means of external communication. PPP/IP or SLIP = is > > > > > something ELKS should definitely have IMHO. > > > > > > > > > > Cheers, > > > > > Paul > > > > > > > > > > On Sat, 15 Feb 2020, Derek Johansen wrote: > > > > > > > > > > > Does elks/Documentation/text/networking_guide.txt make > > > > > > elks/Documentation/text/networking.txt obsolete? The latter in > > > > > > Section 2 says ELKS only supports SLIP connections. I don't th= ink > > > > > > this is still true? > > > > > > > > > >=20 > > > >=20 --98048-624174455-1581952075=:19553--