qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Christian MICHON" <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] USB EHCI development nearing completion
Date: Thu, 4 Jan 2007 10:53:17 +0100	[thread overview]
Message-ID: <46d6db660701040153o5e1ee5e9o86393b1659f80e24@mail.gmail.com> (raw)
In-Reply-To: <200701040945.l049j3dY027801@fozzy.burkley.net>

I tested it on win32 host.
Apparently a typo mistake (see updated patch)

how to use it ?

diff -Nur ehci.patch ehci-xian.patch
--- ehci.patch  Thu Jan  4 09:50:17 2007
+++ ehci-xian.patch     Thu Jan  4 10:40:26 2007
@@ -1722,7 +1722,7 @@
 +    printf ("buffer is %p (+%d)\n", s->buffer, (uint8_t*)s->buffer -
(uint8_t*)s);
 +
 +    pci_conf = s->dev.config;
-+    pci_conf[0x00] = 0x86
++    pci_conf[0x00] = 0x86;
 +    pci_conf[0x01] = 0x80; // Intel VID
 +    pci_conf[0x02] = 0x55;
 +    pci_conf[0x03] = 0x55; // Made up product ID


On 1/4/07, Mark B <qemu@corbally.net> wrote:
>
> Paul,
>
> I don't see anything to do with EHCI in Chromium.  I was just referring to
> the 3D patch as an example - maybe this is causing confusion.
>
> Did anyone else get a chance to look at the EHCI emulation patch?
>
> Thanks,
>
> Mark
>

--
Christian

  reply	other threads:[~2007-01-04  9:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-24  9:57 [Qemu-devel] USB EHCI development nearing completion Mark B
2006-12-24 12:18 ` Hetz Ben Hamo
2006-12-27 13:38   ` Fabrice Bellard
2006-12-27 21:21     ` Mark B
2006-12-27 21:34       ` Paul Brook
2007-01-04  8:44         ` Mark B
2007-01-04  9:53           ` Christian MICHON [this message]
2007-01-04 20:24             ` Mark B
2007-01-05 21:34               ` Thiemo Seufer
  -- strict thread matches above, loose matches on Subject: below --
2006-12-23 15:46 Mark Burkley

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=46d6db660701040153o5e1ee5e9o86393b1659f80e24@mail.gmail.com \
    --to=christian.michon@gmail.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).