qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Matteo <sgala@sgala.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] blackberry and qemu
Date: Wed, 20 Jun 2007 17:17:21 +0200	[thread overview]
Message-ID: <20070620151721.GQ1452@sgala.com> (raw)

Hi! I was trying to use Blackberry Desktop under Windows XP under a QEMU
virtual machine under Linux.

My problem is that the device is recognized as device id 0fca:0006 and
after some seconds it switch to 0fca:0004 . So when I make a "usb_add
host:0fca:0006" QEMU lose my request and if I try to make a "usb_add
host:0fca:0004" the system forever wait something with the CPU at 100%.

Someone have successful experience?

I'll try with a USB bluetooth dongle to bypass the USB interface... i
hope that this will help...

Thanks

Matteo

p.s.: The original qemu patch is unable to add the 0fca:0004 because is
a multiple usb device so I patched the qemu debian package 0.9.0-2 with
this patch http://lists.gnu.org/archive/html/qemu-devel/2007-04/msg00662.html
but i have the described problems...
p.p.s: I have a BB 8100 

                 reply	other threads:[~2007-06-20 15:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070620151721.GQ1452@sgala.com \
    --to=sgala@sgala.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).