Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp761432pxb; Fri, 28 Jan 2022 09:23:26 -0800 (PST) X-Google-Smtp-Source: ABdhPJxz4/TTZRcfnkEguIEDwF9fJQDYfwX4uqNpfMOQrz/X4M0lO/aAhdPogOGlzrrwjyVtgkAp X-Received: by 2002:a17:90a:f001:: with SMTP id bt1mr20591920pjb.109.1643390605690; Fri, 28 Jan 2022 09:23:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643390605; cv=none; d=google.com; s=arc-20160816; b=FdOqxLM3mUp2cRII6s6MSzQ/DpJZ4QdowPUSC8r4Ht2J8pc+m/OGdYWUCnAsdgeKol OVTedX97/3yq20pqhgcFaPfjqvDvJ/XOTi0UtyQxTwC1SYIOH9acwBLFJ7zhWuv0aTnE Y2LbrgIq4iVsbJicdp0LQxvXBzKMaQzurSvXkpv0MstjB7DuxkuJSOtBjI+PkX/U/ehH qYr7l25u9Y+/H3oJqduA4bnvHXOIeWniBJcx+7J3TfxAf6KCQn0iSoYRMUW0bXdJy/hm hZXM7D6OdbrMZk+RSBUYGNQcvN+kahRp8Y++uTgDbmhHN1OeZiLaQO/qBlZL1CjXcVB+ 9EGA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:reply-to:from:date:dkim-signature; bh=8GZdtU+EMcSJ2qJdFVVlKuN6nr0kW1V4mta5rpcDr/0=; b=W9xyI1tQEjZorqEy1BO4k3vLs8wh/PdO+exe5AAa9iGHjuGjrU63/GsnmCBbpuedM9 VaZdu3CD7pfPnytWZF4/RH0bi/gNyogEvjaSXd/95RgBso8JNM5qfnVfnRBYecDoTmrM 7Q56NhgH/DViQn5E4PBtSbCAy6IwOkiS59OdoZuk8+tZ3HhgDkPuTaeUmAKvVEHfb8tP Txz2rC5QwRAiX//Ho00Cd+KzHJleAizeuePgU3idBv+lBjZ3G3R/zgJ+LGewSQJSxObR lPmKRtFPRxgKWDaf/l8zud6IJCaGL2TGPNkOUoTTb53ol+pxRSAglXorJv+RuzQDG8FB QyJw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@panix.com header.s=panix header.b=n+rEiPhW; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 27si3112042pjd.93.2022.01.28.09.23.11; Fri, 28 Jan 2022 09:23:25 -0800 (PST) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=fail header.i=@panix.com header.s=panix header.b=n+rEiPhW; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230341AbiA0U6Z (ORCPT + 99 others); Thu, 27 Jan 2022 15:58:25 -0500 Received: from mailbackend.panix.com ([166.84.1.89]:60867 "EHLO mailbackend.panix.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229692AbiA0U6X (ORCPT ); Thu, 27 Jan 2022 15:58:23 -0500 Received: from [192.168.55.37] (ip68-111-137-238.sd.sd.cox.net [68.111.137.238]) by mailbackend.panix.com (Postfix) with ESMTPSA id 4JlCbx5S9BzLgq; Thu, 27 Jan 2022 15:58:21 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=panix.com; s=panix; t=1643317102; bh=Hvghr7JE4BHuqPhI3bxyFplZcVnjczKkxw/4tAV9RV0=; h=Date:From:Reply-To:To:cc:Subject:In-Reply-To:References; b=n+rEiPhWKHJuAYUiIIHNCfYgt5DgPZjzkfMNeTfGZVKqtTxnZQDIMQm9X/mv5vnPT zAFxP6qdPnHnSvCsnvKsG8I2/gr5PZiJG1gEAeSb4BpbXys2OReA4rz6NHuIqCOUku Bxdtbz5pebyb8c5cHRt6YjJ8sbK8vXU2CFNKSq1c= Date: Thu, 27 Jan 2022 12:58:20 -0800 (PST) From: "Kenneth R. Crudup" Reply-To: "Kenneth R. Crudup" To: Luiz Augusto von Dentz cc: Luiz Augusto Von Dentz , "linux-bluetooth@vger.kernel.org" , "Kenneth R. Crudup" Subject: Re: Commit ad383c2c6 ("Bluetooth: hci_sync: Enable advertising when LL privacy is enabled") breaks my MS ArcTouch mouse In-Reply-To: <76f65c9-e031-3870-9dfb-49f8969534ae@panix.com> Message-ID: <6f3b9dbb-6ecf-cfea-2127-cb3360d78431@panix.com> References: <4124ccb8-11f-21e9-982e-7fb07f23225@panix.com> <91c1e9ef-4786-b9f5-8bb8-b93c84c0874b@panix.com> <76f65c9-e031-3870-9dfb-49f8969534ae@panix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Anything else I can do to help you diagnose this regression? One thing I do (vaguely) remember when building a custom kernel some time ago is that this device does some sort of "GATT encryption" (I'm sure I'm misremembering this, it's been a few years) and I couldn't connect to it either unless the appropriate config setup was used when building the kernel. Thanks, -Kenny -- Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA