From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: linux-kernel@vger.kernel.org
Subject: Digi Xem Problems
Date: Thu, 12 Apr 2001 08:46:20 -0400 [thread overview]
Message-ID: <3AD5A399.71065F90@fibrespeed.net> (raw)
I'm wondering if anyone in the Linux kernel development community has
any ideas about some problems I'm having with Digi Xem boards.
We've got a Digi Xem board (two different PCI boards and an ISA board
were tested) in a Linux 2.2.19 machine to provide logins to Wyse
terminals. When logged into the Linux machine, the Wyse terminals
operate fine. If we telnet anywhere, however (including localhost), and
then generate over about 1k of screen output, the output pauses until we
generate input. If enter or space, etc. is hit on the Wyse keyboard,
the output continues. With 2.2.5, this behaviour does not happen.
We are using the epca.c driver from Digi's website (which is
substantially newer than the one included in the kernel distribution).
We have been unable to determine the cause of this pause. The delay is
very consistent (if we generate output that causes the delay, the same
output will always pause at the same point) but our driver modifications
haven't helped us any.
Digi's engineering staff _may_ look at this problem but since they don't
officially support kernels not released by RedHat, we have no
guarantees. Any ideas out there?
Please CC me on replies. Thank-you.
--
Michael T. Babcock (PGP: 0xBE6C1895)
http://www.fibrespeed.net/~mbabcock/
next reply other threads:[~2001-04-12 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 12:46 Michael T. Babcock [this message]
2001-04-12 13:34 ` Digi Xem Problems Alan Cox
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=3AD5A399.71065F90@fibrespeed.net \
--to=mbabcock@fibrespeed.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.