* Problem with running custom hardware card, 1.1.5 seems to make it worse...
@ 2003-06-11 7:20 Barclay McInnes
2003-06-11 8:48 ` Justin Zygmont
0 siblings, 1 reply; 6+ messages in thread
From: Barclay McInnes @ 2003-06-11 7:20 UTC (permalink / raw)
To: linux-msdos
Everyone;
I've got an ANA-200 Analog I/O board that I'm trying to get running
under DOSEmu so that we can switch this particular machine to Linux
permanently, but I've been battling with only some success. Info about the
card itself is here:
http://www.bsof.com/a200prod.htm
In a nutshell, it needs to communicate with the DOS based analyzer program
we run, on a port between 0x200 and 0x2FF. With DOSEmu 1.1.4 I had it sort
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. The message
that appeared in the DOS app indicated this anyway, since it stated that the
com was too slow and I needed at least a 486/66 for it to work properly.
This is on a PII/350, so obviously the raw hardware itself is more than up
to the task, the slowdown being in the emulation layers. So, with great joy
I tried 1.1.5 since one of the points listed was that I/O was improved, and
was hoping this would be the final key to finish off this beast of a
problem. But under 1.1.5, the card is not detected at all. Tried all
addresses in the card's range to no luck. It's like it just isn't there at
all....
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?
Thanks
Barclay McInnes.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with running custom hardware card, 1.1.5 seems to make it worse...
2003-06-11 7:20 Barclay McInnes
@ 2003-06-11 8:48 ` Justin Zygmont
0 siblings, 0 replies; 6+ messages in thread
From: Justin Zygmont @ 2003-06-11 8:48 UTC (permalink / raw)
To: Barclay McInnes; +Cc: linux-msdos
does setting hogthreshhold to 0 help with the speed?
On Wed, 11 Jun 2003, Barclay McInnes wrote:
> Everyone;
> I've got an ANA-200 Analog I/O board that I'm trying to get running
> under DOSEmu so that we can switch this particular machine to Linux
> permanently, but I've been battling with only some success. Info about the
> card itself is here:
>
> http://www.bsof.com/a200prod.htm
>
> In a nutshell, it needs to communicate with the DOS based analyzer program
> we run, on a port between 0x200 and 0x2FF. With DOSEmu 1.1.4 I had it sort
> 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. The message
> that appeared in the DOS app indicated this anyway, since it stated that the
> com was too slow and I needed at least a 486/66 for it to work properly.
> This is on a PII/350, so obviously the raw hardware itself is more than up
> to the task, the slowdown being in the emulation layers. So, with great joy
> I tried 1.1.5 since one of the points listed was that I/O was improved, and
> was hoping this would be the final key to finish off this beast of a
> problem. But under 1.1.5, the card is not detected at all. Tried all
> addresses in the card's range to no luck. It's like it just isn't there at
> all....
> 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?
>
> Thanks
> Barclay McInnes.
>
>
> -
> 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
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with running custom hardware card, 1.1.5 seems to make it worse...
@ 2003-06-11 9:07 Stas Sergeev
2003-06-12 5:39 ` Barclay McInnes
0 siblings, 1 reply; 6+ messages in thread
From: Stas Sergeev @ 2003-06-11 9:07 UTC (permalink / raw)
To: linux-msdos
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with running custom hardware card, 1.1.5 seems to make it worse...
2003-06-11 9:07 Problem with running custom hardware card, 1.1.5 seems to make it worse Stas Sergeev
@ 2003-06-12 5:39 ` Barclay McInnes
0 siblings, 0 replies; 6+ messages in thread
From: Barclay McInnes @ 2003-06-12 5:39 UTC (permalink / raw)
To: Stas Sergeev, linux-msdos
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with running custom hardware card, 1.1.5 seems to make it worse...
@ 2003-06-12 9:50 Stas Sergeev
2003-06-12 10:43 ` Ged Haywood
0 siblings, 1 reply; 6+ messages in thread
From: Stas Sergeev @ 2003-06-12 9:50 UTC (permalink / raw)
To: linux-msdos; +Cc: Barclay McInnes
Hello.
Barclay McInnes wrote:
> 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
Good. Still wondering why it is not a
default.
Although it would still make sense if you
find the 1.1.4.x pre-release where the
things got broken and open up a bug entry
at BTS to help us to fix the problem for
good. Downgrading is the worst fix ever
possible.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with running custom hardware card, 1.1.5 seems to make it worse...
2003-06-12 9:50 Stas Sergeev
@ 2003-06-12 10:43 ` Ged Haywood
0 siblings, 0 replies; 6+ messages in thread
From: Ged Haywood @ 2003-06-12 10:43 UTC (permalink / raw)
To: DOSEMU users mailing list
Hi Stas,
On Thu, 12 Jun 2003, Stas Sergeev wrote:
> Downgrading is the worst fix ever possible.
Not if it makes it work.
You're starting to sound like a developer... :)
73,
Ged.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-06-12 10:43 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-06-11 9:07 Problem with running custom hardware card, 1.1.5 seems to make it worse Stas Sergeev
2003-06-12 5:39 ` 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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox