From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Can I use DOSEMU for testing device driver code?
Date: Sun, 15 Feb 2004 14:15:42 +0300 [thread overview]
Message-ID: <402F54DE.9080600@aknet.ru> (raw)
Hello.
Ryan Underwood wrote:
>> The problem in (B) seems to be that all of my transmitted characters
>> disappear into a sort of 'virtual' UART to be transmitted later, whilst
>> the RTS signal seems to come out of the port in 'real' time.
> I don't think that is happening. i.e. in,out instructions are directly
> executed, there is no emulation involved.
No, the "problem B" was about an
emulated access, which is indeed
going via an emulated UART.
Its latency was considerably
reduced in dosemu-1.2.0 (not in
any 1.1), but still of course can't
match the direct access.
The fact that RTS gets out of sync
with the TX looks like a bug, most
likely the emulated FIFO is being
switched on when it shouldn't. But
sigh, looks like that bug will have
to wait for the next time:)
Btw, from the docs I have, it is
unclear whether there are some
ways to disable the FIFO, other than
by writing to FCR directly. But I
strongly suspect that at least
changing the DLAB state also should
disables it, which may explain this
problem.
If someone have an info on that -
would be nice to have a look.
next reply other threads:[~2004-02-15 11:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 11:15 Stas Sergeev [this message]
[not found] <4034D439.5080308@edenyard.co.uk>
2004-02-19 18:36 ` Can I use DOSEMU for testing device driver code? Ged Haywood
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 20:12 Stas Sergeev
2004-02-12 21:53 easlab
2004-02-13 8:17 ` Edenyard
2004-02-13 12:01 ` Bart Oldeman
2004-02-14 12:52 ` Edenyard
2004-02-15 4:58 ` Ryan Underwood
2004-02-16 11:27 ` Edenyard
2004-02-17 7:52 ` Ryan Underwood
2004-02-17 9:36 ` Ged Haywood
2004-02-15 5:04 ` Ryan Underwood
2004-02-12 6:11 synthespian
2004-02-12 10:15 ` Ryan Underwood
2004-02-14 19:00 ` EL Henry
2004-02-15 4:53 ` Ryan Underwood
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=402F54DE.9080600@aknet.ru \
--to=stsp@aknet.ru \
--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