From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Problem with running custom hardware card, 1.1.5 seems to make it worse...
Date: Wed, 11 Jun 2003 13:07:39 +0400 [thread overview]
Message-ID: <3EE6F15B.80802@yahoo.com> (raw)
Hello.
Barclay McInnes wrote:
> of working. The DOS program could find the card on
> address 0x200, but claimed that the com between itself
> and the card was too slow.
Have you tried the "fast" flag for
the $_ports option? And does it load
your CPU to 100% ?
> So, with great joy I tried 1.1.5 since one of the points
> listed was that I/O was improved,
But this was only for the I/O that is
done via some filesystem device nodes
and for the socket I/O. So networking
performance is really improved, but
the port I/O is unaffected. Furthermore,
unless you use the "fast" port I/O,
it can be even slower now due to a
client-server approach.
> Are there any alterations I need to make to the
> dosemu.conf file between versions, or can anyone think of
> anything else I can try either with 1.1.5 or a previous
> iteration?
Maybe it is due to some changes in
configuration, but this can be a bug
just as well.
Does your driver uses some particular
IRQ that you specify in $_irqpassing ?
Try producing a debug log, such as
-D9+T for ports I/O and -D9+r for IRQs
and maybe this will shed some light on
the problem. And then also you can see
in what 1.1.4.x pre-release the problem
started to happen.
next reply other threads:[~2003-06-11 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 9:07 Stas Sergeev [this message]
2003-06-12 5:39 ` Problem with running custom hardware card, 1.1.5 seems to make it worse Barclay McInnes
-- strict thread matches above, loose matches on Subject: below --
2003-06-12 9:50 Stas Sergeev
2003-06-12 10:43 ` Ged Haywood
2003-06-11 7:20 Barclay McInnes
2003-06-11 8:48 ` Justin Zygmont
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=3EE6F15B.80802@yahoo.com \
--to=stssppnn@yahoo.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