public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Can I use DOSEMU for testing device driver code?
Date: Fri, 13 Feb 2004 23:12:02 +0300	[thread overview]
Message-ID: <402D2F92.70005@aknet.ru> (raw)


Hello.

Edenyard wrote:
> It appears that DOSEMU has BIG problems when one wants to do this sort
> of thing and nobody quite seems to know why.
Yes, this is the case sometimes, but
usually it is not.

> Last time I asked about this on the mailing list, the response
> I got was, "What's RTS?"....
What have you expected? You haven't
provided the test-case program, no
logs either, you haven't even opened
a bug report on SF tracker.
No reply only means that noone had
that problem previously.
I am using the serial ports via dosemu
at work every day, I can toggle both RTS
and CTS lines as well as the TX line,
the oscilloscope was attached just in
case - so if you sumbit a bug report
and provide at least some info and a
test-case, perhaps your problem would
have been resolved long ago already.
I was saying that in that list many
times and I can only repeat: problems
are not get fixed themselves! You have to
do at least something to get them fixed,
at least open a bug report and provide
a test-case (or logs, but logs not always help).
Unfortunately even when explicitly asked,
many people are not willing to submit a bug
report. Nothing can be done in that case -
game over. On the other hand, some users
are not only providing a bug reports, but
are also willing to do many additional
tests that are required, and in most cases
that works very good. Please see this as
a recent example:
http://sourceforge.net/tracker/index.php?func=detail&aid=884096&group_id=49784&atid=457447

Hope that helps. Be reasonable. You were
asked "What's RTS" not because noone
knew that:)

             reply	other threads:[~2004-02-13 20:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 20:12 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-15 11:15 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=402D2F92.70005@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