Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp2645590rwb; Thu, 17 Nov 2022 13:59:37 -0800 (PST) X-Google-Smtp-Source: AA0mqf5Jg3eqOmU/MWIMi4+VUE1OGM8vb0Hs0AQwV/o0Ice1IacjgaXOxX5yHA7n+U2GjPpZWaPW X-Received: by 2002:a17:90b:2d90:b0:212:ca73:4d6b with SMTP id sj16-20020a17090b2d9000b00212ca734d6bmr10512709pjb.16.1668722376844; Thu, 17 Nov 2022 13:59:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668722376; cv=none; d=google.com; s=arc-20160816; b=yYvRpdK7i0bGX/YyuBiTbpFAskSDjWgYcKLtqc8gFe1BWI7w5Xg2ZkVTN76fyfVVmo XLK9uaqASBDT7XXDRth8U/arshjGXjk7rA/mWzjs1FEKFDFhgHuBy/7PEUzn64+O2Bmh tnYw3vjpwsn0mASA9xCAI5BZp+6BB619QDAj3EAKmQfBNOGLYM0WvVDNkV93OjNzUaZ2 /I3Hjm7C5b0oa09adnEep08DQszvMnVIRPFO0InXxPNEAlGRjuzQzTz4hk3oX+DgOxwQ SV7t4Ej5OB5MUbblrc37kDMTNJ7SkwrOZRpc7Vum4Vc1LLJVrvbzC/BltZJBjj41LmG8 +BiQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=9u5lD63lU5T0aCmu75vgamGZja15WrL8aVLwmrpGkL8=; b=jwNn9Ca2j8iZffTUcXjHinvjh1QFtTwZalG/BVOFjqyDtRASzY+BBWmE0STZy3Xcmd IzH5XP6KKlOnoQEMgHSGoBPMtpZFJMnVr+bOiK4InKx3gWxHLRqD9bRZ668cAGDSMmCF 8y7vTm1EFaT/HRnHi1pP60wn7fb4Ef68xBX312yaH0osqRwzwMTBs8HWnVLq8JzkrdO0 udXCUjgMIJUs1u+hz5MEDVk2lVloh+BEEMWDrZU7UlY9USXDbt0AtIEPpKCH3uZ4OeK0 e9kzoIoKyFIxQEpdEH5hPHrbzRBk2sA793Rp65ZZzyAW9VfKqYvGwwQBtE11Q9w02k17 SUgA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=N8Y0eTzG; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l14-20020a056a0016ce00b0056ec68563d6si2047003pfc.135.2022.11.17.13.58.25; Thu, 17 Nov 2022 13:59:36 -0800 (PST) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=N8Y0eTzG; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241083AbiKQV5q (ORCPT + 99 others); Thu, 17 Nov 2022 16:57:46 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36722 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241082AbiKQV5d (ORCPT ); Thu, 17 Nov 2022 16:57:33 -0500 Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0A2997993B for ; Thu, 17 Nov 2022 13:56:51 -0800 (PST) Received: by mail-lj1-x232.google.com with SMTP id t10so4566012ljj.0 for ; Thu, 17 Nov 2022 13:56:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9u5lD63lU5T0aCmu75vgamGZja15WrL8aVLwmrpGkL8=; b=N8Y0eTzGzRqfRExNYGU4ilC8RW/vxNNblPAGYShTWFPLRmmTn1SslHPsuKCMFG9Qho YDcqz85MMl+TaXdU2VGwMX1B9uQ8gOnmyuNFbJ/+ZIpk9/KY1VhiZOqst4YWsaBGpCOt EzPzSOvoGz/SXQ3Fy2f5M0nHPDbVqrNRXUCEZq3ifgQBCgFgqsdFGiuWwiCJyAYna67U 8DeWAKMzCoAQGspgNsX2PsLe6/f58dtJT4Stvc8v3zIEqsq/WM31pN6eQzwLeuSdQI8L sL/HqldziJmuAYiAyq8DzWW71ixZt3dQnD8JxyudyBZK9zyaugjTHVvYS+QITtNrVO+M wb2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9u5lD63lU5T0aCmu75vgamGZja15WrL8aVLwmrpGkL8=; b=Jw8zYQh1lzuaY0VUNmrQ/V865xy/Y85kMmGpCphm7YrHI9f2km51H3ZiX/PiyYmdve OOx5ObqHcc6rcI48N95e/xR7GpHqFKEOiB3mFxaMRqidKzYG2udqPo61PcYdSH71zE5m 5foSHLV2pT3ccHW1myktT04hQ1iAPke7MfPnhsTJ2+9bSdAiC6gGSOz9wTsZdqSKjtey hwSol8CJEPWu/PMHGyW9j47pKMeMHpR7Il8mRG4wU3tmzavrx5gRmv5WahOtgX1HgNOF /aAeySqNVnZi8CAk7ItiIo3JQ9hlbxKI5w/ezDPhdLPhKSAClbM6UhAgXgPCWntAGnIY 4v9w== X-Gm-Message-State: ANoB5pmGsAZzoCFF1HOPUltRjeTV4EiMps47KG/nMaDWbObWk4CJPbH9 GvPNtfGni72ZM3apKOWD44H0eFsSEojYGwHWQu+DfukG X-Received: by 2002:a05:651c:2221:b0:26f:bb12:2af5 with SMTP id y33-20020a05651c222100b0026fbb122af5mr1792013ljq.293.1668722209221; Thu, 17 Nov 2022 13:56:49 -0800 (PST) MIME-Version: 1.0 References: <92dfa5c7-90db-8100-b481-2bd4972a0ec1@voxel.at> In-Reply-To: <92dfa5c7-90db-8100-b481-2bd4972a0ec1@voxel.at> From: Luiz Augusto von Dentz Date: Thu, 17 Nov 2022 13:56:37 -0800 Message-ID: Subject: Re: Connecting to a BR/EDR+BLE device a via dbus? To: Simon Vogl Cc: linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Simon, On Thu, Nov 17, 2022 at 8:20 AM Simon Vogl wrote: > > Dear all, > > we are communicating with a headset-ish device that offers classic > bluetooth services and BLE characteristics in parallel. > > We have code to talk to the Bluetooth classic part via bluetoothd/dbus, > and we have code for talking to the BLE parts based on the C-library / > gatt-client code ; both run in parallel for some time but not > super-stable, so I'd like to move the code over to a dbus version. > > As the device starts advertising BLE characteristics only after a > classic connection has been established, it appears as a Bluetooth > classic device on the system bus, and I did not find a way to start GATT > discovery via the 'official' dbus-API. > > I don't fear to tweak bluetoothd nor ~ctl, but would like to know if > someone already some development going in that direction? Perhaps what is needed is to connect ATT over BREDR that way you don't need 2 bearers to be connected, bt_att already supports connecting over classic but we never took the step to connect ATT once we figured it supported the ATT PSM given is not very common to have a classic profile that uses GATT attributes. > Simon > > -- > > VoXel Interaction Design |www.voxel.at > DI Dr.techn. Simon Vogl |simon@voxel.at > Tomaschekweg 46 | +43 650 2323 555 > A-4040 Linz - Austria | > Office address: Industriezeile 35, 4020 Linz (2nd floor) > -- Luiz Augusto von Dentz