From: Vincent Palatin <vincent.palatin_qemu@m4x.org>
To: qemu-devel@nongnu.org
Cc: Vincent Palatin <vincent.palatin_qemu@m4x.org>,
Jan Kiszka <jan.kiszka@web.de>, David Ahern <daahern@cisco.com>
Subject: [Qemu-devel] [PATCH 2/2] ehci: Fix debug traces
Date: Mon, 10 May 2010 04:32:08 +0200 [thread overview]
Message-ID: <1273458728-24918-3-git-send-email-vincent.palatin_qemu@m4x.org> (raw)
In-Reply-To: <1273458728-24918-1-git-send-email-vincent.palatin_qemu@m4x.org>
- fix build error when activating traces
- properly display the config flags register
Signed-off-by: Vincent Palatin <vincent.palatin_qemu@m4x.org>
---
hw/usb-ehci.c | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/hw/usb-ehci.c b/hw/usb-ehci.c
index e724653..ab9a23e 100644
--- a/hw/usb-ehci.c
+++ b/hw/usb-ehci.c
@@ -469,6 +469,10 @@ static const char *addr2str(unsigned addr)
case PORTSC_BEGIN ... PORTSC_END:
r = "PORT STATUS";
break;
+
+ case CONFIGFLAG:
+ r = "CONFIG FLAG";
+ break;
}
return r;
@@ -1956,7 +1960,7 @@ static void ehci_map(PCIDevice *pci_dev, int region_num,
{
EHCIState *s =(EHCIState *)pci_dev;
- DPRINTF("ehci_map: region %d, addr %08lX, size %ld, s->mem %08X\n",
+ DPRINTF("ehci_map: region %d, addr %08llX, size %lld, s->mem %08X\n",
region_num, addr, size, s->mem);
s->mem_base = addr;
cpu_register_physical_memory(addr, size, s->mem);
--
1.5.6.5
next prev parent reply other threads:[~2010-05-10 2:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 2:32 [Qemu-devel] ehci fixes Vincent Palatin
2010-05-10 2:32 ` [Qemu-devel] [PATCH 1/2] ehci: Fix error detection when registering a new list base address Vincent Palatin
2010-05-10 2:32 ` Vincent Palatin [this message]
2010-05-10 2:36 ` [Qemu-devel] Re: ehci fixes David S. Ahern
2010-05-10 13:43 ` Vincent Palatin
2010-05-12 19:29 ` Jan Kiszka
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=1273458728-24918-3-git-send-email-vincent.palatin_qemu@m4x.org \
--to=vincent.palatin_qemu@m4x.org \
--cc=daahern@cisco.com \
--cc=jan.kiszka@web.de \
--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).