Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain;
        charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Subject: Re: [PATCH RESEND] Bluetooth: btbcm: Add default address for
 BCM2076B1
From:   Marcel Holtmann <marcel@holtmann.org>
In-Reply-To: <20190501071820.6404-1-stephan@gerhold.net>
Date:   Sun, 5 May 2019 19:29:49 +0200
Cc:     Johan Hedberg <johan.hedberg@gmail.com>,
        linux-bluetooth@vger.kernel.org
Content-Transfer-Encoding: 7bit
Message-Id: <33CCCE49-ADC6-4A24-9EAC-07D11671F67E@holtmann.org>
References: <863F9BB0-25C7-4A9B-8D91-2A2D2690D13D@holtmann.org>
 <20190501071820.6404-1-stephan@gerhold.net>
To:     Stephan Gerhold <stephan@gerhold.net>
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Stephan,

> BCM2076B1 appears to use 20:76:A0:00:56:79 as default address.
> This address is used by at least 5 devices with the AMPAK AP6476
> module and is also suspicious because it starts with the chip name
> 2076 (followed by a different revision A0 for some reason).
> 
> Add it to the list of default addresses and leave it up to the
> user to configure a valid one.
> 
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
> (rebased on latest bluetooth-next)
> 
> drivers/bluetooth/btbcm.c | 5 +++++
> 1 file changed, 5 insertions(+)

patch has been applied to bluetooth-next tree.

Regards

Marcel