From: "John R. Hogerhuis" <jhoger@speakeasy.net>
To: jasong@ccgr.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Impractical ideas?
Date: Thu, 06 May 2004 18:38:25 -0700 [thread overview]
Message-ID: <1083893904.3561.1163.camel@aragorn> (raw)
In-Reply-To: <200405062034.39658.jasong@ccgr.org>
Perhaps not. I'm used to dealing with constained systems though.
Try bit-banging a port without having the timing be deterministic.
But you may have a point on desktops. I'm no expert on the PCI bus.
-- John.
On Thu, 2004-05-06 at 18:34, Jason Gress wrote:
> I hate to feed the fire ;), but it would seem that drivers couldn't use too
> much timing information as they can never expect a certain time for anything.
next prev parent reply other threads:[~2004-05-07 1:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 16:08 [Qemu-devel] Impractical ideas? Robert Wittams
2004-05-06 18:06 ` John R. Hogerhuis
2004-05-06 21:52 ` J. Mayer
2004-05-06 22:11 ` John R. Hogerhuis
2004-05-07 1:34 ` Jason Gress
2004-05-07 1:38 ` John R. Hogerhuis [this message]
2004-05-07 9:44 ` David Woodhouse
2004-05-07 17:13 ` Irvin Probst
2004-05-07 17:51 ` Chad Page
2004-05-07 19:21 ` David Woodhouse
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=1083893904.3561.1163.camel@aragorn \
--to=jhoger@speakeasy.net \
--cc=jasong@ccgr.org \
--cc=jhoger@pobox.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).