From: David Lawyer <dave@lafn.org>
To: linux-serial@vger.kernel.org
Subject: Re: serial port speeds >115k; PnP modem ID must contain modem substring
Date: Sun, 23 Feb 2003 23:11:36 -0800 [thread overview]
Message-ID: <20030224071136.GA495@lafn.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0302232044110.5171-100000@deadrat.localdomain>
On Sun, Feb 23, 2003 at 09:59:57PM -0800, rich+ml@lclogic.com wrote:
> Internal modems usually just have a simulated uart for software
> compatibility and baud rate is irrelevant (same for parity, stop bits,
> FIFO, etc). Set to 5 baud and see if you get same performance.
I set to 300 baud and couldn't connect. Then at 1200 baud it connected but
download speeds were around 60 bytes/sec. I estimated the received rate
from the /proc dir and it was close to 1200 baud. So mine must have a
real UART.
Some modems brag that they can do 230.4k baud. This is a serial port
speed. So it seems like a real UART. So what percent of internal
modems will operate at a high baud rate when one specifies low baud rate?
>
> == Rich
>
> On Fri, 21 Feb 2003, Tim wrote:
>
> > Date: Fri, 21 Feb 2003 15:09:39 -0500
> > From: Tim <delt@gate-way.net>
> > To: linux-serial@vger.kernel.org
> > Subject: serial port speeds >115k; PnP modem ID must contain modem
> > substring
> >
> > I have a Diamond/Supra v90 ISA modem (model SUP2124) in my
> > Linux system running 2.4.20. I've noticed that for the
> > type of file I commonly access (large html text table) 115k
> > port speed seems to be a significant bottleneck. (These
> > files compress to <10% of raw size. Transfer speed is
> > reported as ~10.5kByte/s, even if I reduce my modem speed
> > from the typical 45kbps to 28.8.) The modem documentation
> > says it is capable of 230k port speed, so I tried specifying
> > 230400 in my ppp config, which resulted in 9600 baud port
> > speed; stty returns an error.
> >
> > At this point in my education, my guess is that the modem is
> > being treated like a 16550A without extended FIFOs or 230k
> > port speed. If my modem was detected as a modem by Linux,
> > would setserial -a show something more?
> >
> > # setserial -a /dev/ttyS3
> > /dev/ttyS3, Line 3, UART: 16550A, Port: 0x02e8, IRQ: 10
> > Baud_base: 115200, close_delay: 50, divisor: 0
> > closing_wait: 3000
> > Flags: spd_normal skip_test
> >
> > I am not a programmer, but have been looking at the comments
> > in serial.c:
> >
> > There seems to be an ISA PnP device device search, the success
> > of which depends on finding the string "modem" in PnP id:
> > dev->name or dev->bus->name must contain "modem" substring;
> >
> > However, the modem in this system was installed with PnP
> > disabled and does not have modem in its string:
> > # ANSI string -->SupraExpress 56i Voice<--
> >
> > What are the consequences of failing this test? If the
> > string were changed, could the test succeed with the modem
> > jumper not in PnP mode?
> >
> > There seems to be a "quickie test to see how big the FIFO is".
> > How can I cause the results of that test to be logged?
> >
> > I now have CONFIG_SERIAL=y.
> > If I compile serial as a module, are there parameters that
> > can be added to modules.conf to enable available features
> > beyond what a 16550A has, or perhaps someone has patches
> > that would enable these features?
> >
> > TIA,
> > Tim.
> >
> > -
David Lawyer
next prev parent reply other threads:[~2003-02-24 7:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 20:09 serial port speeds >115k; PnP modem ID must contain modem substring Tim
2003-02-22 4:56 ` whitnl73
2003-02-22 9:20 ` David Lawyer
2003-02-23 15:45 ` PnP Rage Hal MacArgle
2003-02-24 4:24 ` David Lawyer
2003-02-24 14:05 ` Hal MacArgle
2003-02-24 5:59 ` serial port speeds >115k; PnP modem ID must contain modem substring rich+ml
2003-02-24 7:11 ` David Lawyer [this message]
2003-02-24 22:50 ` rich+ml
2003-02-24 17:57 ` port speeds >115k Tim
2003-02-25 1:25 ` whitnl73
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=20030224071136.GA495@lafn.org \
--to=dave@lafn.org \
--cc=linux-serial@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