public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim <delt@gate-way.net>
To: linux-serial@vger.kernel.org
Subject: port speeds >115k
Date: Mon, 24 Feb 2003 12:57:38 -0500	[thread overview]
Message-ID: <20030224175738.GA349@jats9> (raw)
In-Reply-To: <20030222092008.GA492@lafn.org> <20030221.235743.8.0.whitnl73@juno.com> <20030221224119.GD350@lafn.org> <20030221200939.GA1543@jats9> <20030223104525.A206@lnx2.w8mch.ampr.org> <20030224071136.GA495@lafn.org> <Pine.LNX.4.44.0302232044110.5171-100000@deadrat.localdomain>

[cc's not required]

> > > stty returns an error.
> > 
> > What error?  Quote exactly please.

stty -F /dev/ttyS3 230400
stty: /dev/ttyS3: unable to perform all requested operations

> > If the doco says it can run faster than 115200, it should also tell
> > what you have to do to make it do so.
> 
> Yes.  It will likely say (or imply) to use a driver they supply for
> Windows only.                                       ^^^^^^^^^^^

Ha! ~"All our 56k modems are capable of supporting 230k ... go find
a driver from someone else", actually.  Or try to ID the chipset &
find the datasheet.

> > > If my modem was detected as a modem by Linux,
> > > would setserial -a show something more?
> > 
> > It was detected as a serial port.  Linux does not detect modems at
> > startup.

I guess all that modem stuff in serial.c is just for PnP addr/irq init.

> > 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?
> Is this test done by some Linux utility?

grep quickie drivers/char/serial.c

> > 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.

Well I noticed stty <anyspeed> makes no dif in an xterm, or the 
getty on a vc, but with 
http://members.gate-way.net/delt/test/500k.html
my hardware ISA modem behaves like:

CARRIER	PORT	AVG.RATE
=======	====	========
46k	115k	10.5kB/s
26k	115k	10.5kB/s
14k	115k	10.5kB/s
46k	 57k	 5.3kB/s

For viewing large html text tables with a fast browser like Dillo,
230k could ~double the speed of the whole process.

> 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?

I've seen non-rigorous test results on the net indicating that some
softmodems have no port-speed bottleneck.  It'd be great to have a GPL
HSP modem for Linux, now that GHz CPUs are the norm.  This groveling
for 230kbits/s through a device sitting directly on the system bus,
and being hobbled by hostile hw/sw producers is hard to take.  Wonder
what the absolute minimum hardware for a modem is...

  parent reply	other threads:[~2003-02-24 17:57 UTC|newest]

Thread overview: 13+ 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
2003-02-24 22:50     ` rich+ml
2003-02-24 17:57   ` Tim [this message]
2003-02-25  1:25     ` port speeds >115k whitnl73
  -- strict thread matches above, loose matches on Subject: below --
2003-02-24 19:01 Ed Vance
2003-02-24 20:28 Ed Vance

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=20030224175738.GA349@jats9 \
    --to=delt@gate-way.net \
    --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