From: "Trever L. Adams" <trever_Adams@bigfoot.com>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Serial, 115Kbps, 2.2, 2.4
Date: Sun, 01 Apr 2001 19:10:04 -0400 [thread overview]
Message-ID: <3AC7B54C.2010706@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10104011432180.5518-100000@coffee.psychology.mcmaster.ca>
Mark Hahn wrote:
>> There may be a possibility this is machine specific, because if it is
>> meant to forward the packet to the internal net and I slow the machine
>> down (external cache off) it works fine, turn the cache back on and it
>> is a problem.
>
>
> where's the serial port? (isa, pci?) could there be a problem
> with something being overclocked (like >8 MHz ISA, etc)?
> also, is the port's fifo detected and used?
As far as I know the system is not overclocked (standard Digital
Venturis 6200 GL PPro 200 Mhz machine). It is an ISA modem. All info I
have on the port is as follows:
Serial driver version 5.05 (2000-12-13) with MANY_PORTS SHARE_IRQ
SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
cat /proc/ioports
03f8-03ff : serial(auto)
It is a USR 56K Voice/Fax/Modem. I am unable to find the exact model.
It was definitely pre v.90 though I believe it has been updated
(Firmware) to that. I have another, though I don't remember similar
problems even though it was at the same baudrate (different machine though).
Trever Adams
next parent reply other threads:[~2001-04-02 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10104011432180.5518-100000@coffee.psychology.mcmaster.ca>
2001-04-01 23:10 ` Trever L. Adams [this message]
2001-04-02 0:44 ` Serial, 115Kbps, 2.2, 2.4 Tom Sightler
2001-04-02 6:30 ` Paul Jakma
2001-04-01 16:35 Trever L. Adams
2001-04-01 23:53 ` Jeff Chua
2001-04-02 1:34 ` Manfred H. Winter
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=3AC7B54C.2010706@bigfoot.com \
--to=trever_adams@bigfoot.com \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox