From: Paul Osmialowski <pawelo@king.net.pl>
To: David Given <dg@cowlark.com>
Cc: Paul Osmialowski <pawelo@king.net.pl>,
Georg Potthast <nospam@georgpotthast.de>,
Derek Johansen <djohanse678@gmail.com>,
"Marc-F. Lucca-Daniau" <mfld.fr@gmail.com>,
ELKS <linux-8086@vger.kernel.org>
Subject: Re: Obsolete documentation?
Date: Mon, 17 Feb 2020 14:10:48 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.21.1.2002171358470.15349@localhost.localdomain> (raw)
In-Reply-To: <CALgV52jgt1U0MNAxEy6jsDykdkMHGGopBxT4o6itW4UzWrXx5A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]
On Mon, 17 Feb 2020, David Given wrote:
> On Mon, 17 Feb 2020 at 00:30, Paul Osmialowski <pawelo@king.net.pl> wrote:
> I'm using null-modem cable I've made myself and been using it for years
> (it corsses-over Rx/Tx and hardware control lines). It works nicely with
> Telix running under FreeDOS on my XT and minicom on 'big' Linux, at speed
> 115200, which is the top speed for 8250 chip on the XT side.
>
>
> Exactly which 8250 is it? Some versions had major bugs which needed non-backwards-compatible workarounds in the BIOS. If the ELKS driver doesn't have these workarounds, which is likely if it's been targeted at later versions of the 8250 which didn't have the bugs,
> then it's likely not to work very well. I also believe (heard from Random Person On The Internet) that driving an 8250 at high speed is difficult due to the very small buffer, and you need very good interrupt performance, which I don't know if ELKS has.
>
> Information on the different 8250s is here: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/serial-uart/index.html
>
In this particular case (Amstrad PC 2086) it's on-board Amstrad 40049 UART
(the same chip as used for a serial port in Amstrad Portable PC models), I
don't know any more details, except that all DOS programs (e.g. Norton SI)
report it as 8250. Yet at my old home I have Turbo XT with old, long 8-bit
ISA I/O card having two regular 8250's on it and as far as I remember, it
was the first time I experienced losing bits while communicating ELKS and
Linux running on a bigger PC.
next prev parent reply other threads:[~2020-02-17 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 4:51 Obsolete documentation? Derek Johansen
2020-02-16 11:08 ` Paul Osmialowski
2020-02-16 17:05 ` Marc-F. Lucca-Daniau
2020-02-16 18:10 ` Georg Potthast
2020-02-16 18:37 ` Paul Osmialowski
2020-02-16 21:17 ` Georg Potthast
2020-02-16 23:26 ` Paul Osmialowski
[not found] ` <CALgV52jgt1U0MNAxEy6jsDykdkMHGGopBxT4o6itW4UzWrXx5A@mail.gmail.com>
2020-02-17 13:10 ` Paul Osmialowski [this message]
2020-02-17 14:47 ` Georg Potthast 2
2020-02-17 15:07 ` Paul Osmialowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.21.1.2002171358470.15349@localhost.localdomain \
--to=pawelo@king.net.pl \
--cc=dg@cowlark.com \
--cc=djohanse678@gmail.com \
--cc=linux-8086@vger.kernel.org \
--cc=mfld.fr@gmail.com \
--cc=nospam@georgpotthast.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox