From: Kevin Wolf <kwolf@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Pavel Hrdina <phrdina@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] fdc-test: Check RELATIVE SEEK beyond track 0/80
Date: Tue, 24 Jul 2012 11:35:44 +0200 [thread overview]
Message-ID: <500E6C70.9010901@redhat.com> (raw)
In-Reply-To: <CAAu8pHu23YFn8Tc225U_UA8mkzny-2KGN0XxK6f3V0EsFU4EsQ@mail.gmail.com>
Am 23.07.2012 19:09, schrieb Blue Swirl:
> On Tue, Jul 17, 2012 at 9:03 AM, Pavel Hrdina <phrdina@redhat.com> wrote:
>> I tested it on the real floppy and the behavior is more complicated.
>
> This reminds me of an idea: it could be interesting to make qtest test
> real hardware, for example using a serial port to feed commands and
> get responses. The same protocol which libqtest uses could be
> interpreted by a boot loader level program or kernel module.
The existing qtest cases wouldn't necessarily work there because they
don't care about timing. Not sure if it's worth the effort writing real
drivers in qtest cases just to be able to run them against real hardware
occasionally.
Kevin
next prev parent reply other threads:[~2012-07-24 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 14:35 [Qemu-devel] [PATCH 0/2] More RELATIVE SEEK fun Kevin Wolf
2012-07-16 14:35 ` [Qemu-devel] [PATCH 1/2] fdc-test: Clean up a bit Kevin Wolf
2012-07-16 14:36 ` [Qemu-devel] [PATCH 2/2] fdc-test: Check RELATIVE SEEK beyond track 0/80 Kevin Wolf
2012-07-17 9:03 ` Pavel Hrdina
2012-07-23 17:09 ` Blue Swirl
2012-07-24 9:35 ` Kevin Wolf [this message]
2012-07-24 20:01 ` Blue Swirl
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=500E6C70.9010901@redhat.com \
--to=kwolf@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=phrdina@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).