From: "Andreas Bollhalder" <bolle@geodb.org>
To: qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] enabling bus-master IDE driver
Date: Mon, 8 Nov 2004 17:51:04 +0100 [thread overview]
Message-ID: <000f01c4c5b3$22a8c440$6401a8c0@geodb.org> (raw)
In-Reply-To: <1099908910.418f472ebd9ff@imp5-q.free.fr>
Tried to load UDMA.SYS from FreeDOS. It complains about a too old BIOS
doesn't load. Has anybody any experience with this ?
Andreas
-----Original Message-----
From: qemu-devel-bounces+bolle=geodb.org@nongnu.org
[mailto:qemu-devel-bounces+bolle=geodb.org@nongnu.org] On Behalf Of
zitu
Sent: Monday, November 08, 2004 11:15 AM
To: qemu-devel@nongnu.org; Jens Axboe
Subject: Re: [Qemu-devel] enabling bus-master IDE driver
*This message was transferred with a trial version of CommuniGate(tm)
Pro*
Quoting Jens Axboe <qemu@kernel.dk>:
> On Sun, Nov 07 2004, Hetz Ben Hamo wrote:
> > > > > - put_le16(p + 49, 1 << 9); /* LBA supported, no DMA */
> > > > > + put_le16(p + 49, 1 << 9 | 1 << 8); /* DMA and LBA
supported */
> >
> > Care to put all the changes in 1 patch please, so I can put it on
my web
> site?
>
> Here you go.
>
(...)
On win95 guest, I can mark dma box and it stays marked. But
performance on
hdd did not change much.
On win xp guest, I still stay on PIO mode, unfortunately.
On Linux, no change. My original patched version already had DMA ok.
Any chance you'd have a fix for xp guest ?
Thanks for the previous patch.
Zitu
--
_______________________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-11-08 17:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 20:35 [Qemu-devel] enabling bus-master IDE driver Simon Frew
2004-11-05 13:32 ` zitu
2004-11-05 15:02 ` zitu
2004-11-06 1:53 ` Jason Brittain
2004-11-06 14:27 ` Johannes Schindelin
2004-11-06 21:52 ` Jason Brittain
2004-11-07 9:03 ` Jens Axboe
2004-11-07 9:21 ` Jens Axboe
2004-11-07 9:38 ` Jens Axboe
2004-11-07 11:01 ` Hetz Ben Hamo
2004-11-07 11:16 ` Jens Axboe
2004-11-08 10:15 ` zitu
2004-11-08 16:51 ` Andreas Bollhalder [this message]
2004-11-09 7:38 ` Paul Jakma
2004-11-09 10:28 ` Hetz Ben Hamo
2004-11-09 13:53 ` Paul Jakma
2004-11-11 17:29 ` Jason Brittain
2004-11-11 19:06 ` Jens Axboe
2004-11-11 19:02 ` Jason Brittain
2004-11-11 19:16 ` Jens Axboe
2004-11-12 8:42 ` Jens Axboe
2004-11-07 11:02 ` James Boddington
2004-11-10 1:41 ` James Boddington
2004-11-06 21:57 ` James Boddington
2004-11-06 22:11 ` James Boddington
2004-11-06 23:46 ` zitu
2004-11-07 0:41 ` jeebs
2004-11-07 7:12 ` Jason Brittain
-- strict thread matches above, loose matches on Subject: below --
2004-11-05 15:37 Juergen Keil
2004-11-05 15:43 ` zitu
2004-11-05 15:45 ` zitu
2004-11-05 15:52 ` Jens Axboe
2004-11-05 16:10 ` zitu
2004-11-05 17:30 ` Damien Mascord
2004-11-12 14:27 Juergen Keil
2004-11-12 18:02 ` Jason Brittain
2004-11-12 19:07 Juergen Keil
2004-11-16 19:41 ` Juergen Lock
2004-11-23 5:12 ` Norikatsu Shigemura
2004-11-25 21:12 ` Juergen Lock
2004-11-26 10:48 Juergen Keil
2004-11-28 20:09 ` Juergen Lock
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='000f01c4c5b3$22a8c440$6401a8c0@geodb.org' \
--to=bolle@geodb.org \
--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).