Re: Problem with running custom hardware card, 1.1.5 seems to make it worse...

["Barclay McInnes" <barc@netdud.com>]

Thanks for the advice!  It was indeed loading the CPU to 100% during
attempted communication, what ultimately got the card working was switching
back to 1.1.4 and using the (previously unknown to me) "fast" flag.  I guess
I must have missed that one in the docs somewhere :).
Thanks again!
Barclay McInnes

----- Original Message ----- 
From: "Stas Sergeev" <stssppnn@yahoo.com>
To: <linux-msdos@vger.kernel.org>
Sent: Wednesday, June 11, 2003 2:07 AM
Subject: Re: Problem with running custom hardware card, 1.1.5 seems to make
it worse...


> 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.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html