All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Dan Christian <dchristian@cardinalpeak.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Need BT support in qemu for Zephyr
Date: Thu, 23 Apr 2020 15:11:12 +0100	[thread overview]
Message-ID: <20200423141112.GE1077680@redhat.com> (raw)
In-Reply-To: <CADxL6wUGWZO0U=G7UTAebG57m6tG58hoMf_-TCC+0qReUB0G6w@mail.gmail.com>

On Thu, Apr 23, 2020 at 07:33:37AM -0600, Dan Christian wrote:
> There was a note about BT support being deprecated.
> 
> Having it makes developing/testing Zephyr
> <https://github.com/zephyrproject-rtos/zephyr> bluetooth vastly easier.
> 
> I hope it will be retained.

Unfortunately it has already been deleted and so will be gone in the 5.0
release of QEMU for certain. In theory it could be brought back to life
in future releases, but it would require someone to step forward as an
active maintainer and fix the problems it had.

The big driving reason for deleting it was that it appeared to be largely
broken / crashing as explained in the commit removing it:

commit 1d4ffe8dc77cbc9aafe8bcf514ca0e43f85aaae3
Author: Thomas Huth <thuth@redhat.com>
Date:   Wed Nov 20 10:10:13 2019 +0100

    Remove the core bluetooth code
    
    It's been deprecated since QEMU v3.1. We've explicitly asked in the
    deprecation message that people should speak up on qemu-devel in case
    they are still actively using the bluetooth part of QEMU, but nobody
    ever replied that they are really still using it.
    
    I've tried it on my own to use this bluetooth subsystem for one of my
    guests, but I was also not able to get it running anymore: When I was
    trying to pass-through a real bluetooth device, either the guest did
    not see the device at all, or the guest crashed.
    
    Even worse for the emulated device: When running
    
     qemu-system-x86_64 -bt device:keyboard
    
    QEMU crashes once you hit a key.
    
    So it seems like the bluetooth stack is not only neglected, it is
    completely bitrotten, as far as I can tell. The only attention that
    this code got during the past years were some CVEs that have been
    spotted there. So this code is a burden for the developers, without
    any real benefit anymore. Time to remove it.
    
    Note: hw/bt/Kconfig only gets cleared but not removed here yet.
    Otherwise there is a problem with the *-softmmu/config-devices.mak.d
    dependency files - they still contain a reference to this file which
    gets evaluated first on some build hosts, before the file gets
    properly recreated. To avoid breaking these builders, we still need
    the file around for some time. It will get removed in a couple of
    weeks instead.
    
    Message-Id: <20191120091014.16883-4-thuth@redhat.com>
    Reviewed-by: Ján Tomko <jtomko@redhat.com>
    Acked-by: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Thomas Huth <thuth@redhat.com>


Can you give more details about what specific QEMU configuration you are
using with Bluetooth - eg what QEMU command line args are you passing
and how functional was the result? Also what QEMU versions have you
succesfully used BT with ?

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2020-04-23 14:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 13:33 Need BT support in qemu for Zephyr Dan Christian
2020-04-23 14:11 ` Daniel P. Berrangé [this message]
2020-04-23 14:40   ` Dan Christian
2020-04-23 14:44     ` Daniel P. Berrangé
2020-04-23 14:55     ` Peter Maydell
2020-04-23 20:44     ` Philippe Mathieu-Daudé

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=20200423141112.GE1077680@redhat.com \
    --to=berrange@redhat.com \
    --cc=dchristian@cardinalpeak.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.