public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Trifle Menot <triflemenot@beewyz.com>
To: linux-msdos@vger.kernel.org
Subject: Re: serial performance
Date: Sat, 13 Mar 2010 05:12:48 +0000	[thread overview]
Message-ID: <201003130512.o2D5CnDN027662@beewyz.com> (raw)
In-Reply-To: <201003121557.o2CFvlHK023131@beewyz.com>

On Fri, 12 Mar 2010 15:57:44 +0000, Trifle Menot
<triflemenot@beewyz.com> wrote:

>If I start dosemu -s with this:
>
>> $_ports = "fast range 0x3F8,0x3FF"
>> $_irqpassing = "4"
>
>A speed of 57600 looks fast, like it should be.  But if I omit the
>direct hardware access, and try this:
>
>> $_com1 = "/dev/ttyS0 irq 4"
>
>57600 still works, but looks much slower on the remote side of a null
>modem cable.  Seems like I read where the code traps serial port writes
>and buffers data to /dev/ttyS0.  Is the trapping causing the slowdown?
>Is there a cure?

Digging deeper, I noticed that my PCBoard BBS recognized a 16550 when
using direct hardware access, but only a 16450 with /dev/ttyS0.

I looked at the dosemu source to try and understand why.  Being new to
the code, I'm not 100% sure of what I'm saying here, but it looks like
FIFO mode is turned on according to whatever bits are poked into the
virtual UART.  So then I looked closer my PCBoard configuration, and I
noticed a setting to "Force 16550A usage" and I turned it on.

With that setting, PCBoard now sees a 16550 when using /dev/ttyS0, and
my remote output looks fast, like 57600 should.  So poking the necessary
bits into the dosemu virtual UART fixed things up.


-- 
Web mail, POP3, and SMTP
http://www.beewyz.com/freeaccounts.php
 

  reply	other threads:[~2010-03-13  5:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12 15:57 serial performance Trifle Menot
2010-03-13  5:12 ` Trifle Menot [this message]
2010-03-13  7:39   ` Paul Crawford
2010-03-13 13:53     ` Trifle Menot

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=201003130512.o2D5CnDN027662@beewyz.com \
    --to=triflemenot@beewyz.com \
    --cc=linux-msdos@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