Received: by 10.223.164.202 with SMTP id h10csp6181754wrb; Wed, 22 Nov 2017 00:09:16 -0800 (PST) X-Google-Smtp-Source: AGs4zMbfUMB/HIrGtXDKnWBjMNS0nbPyyvKGMcFETGgdEaM0Ip2v7Kyf5Kl/+0LEnQzlY5R+EfcA X-Received: by 10.84.164.104 with SMTP id m37mr7238591plg.98.1511338156434; Wed, 22 Nov 2017 00:09:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1511338156; cv=none; d=google.com; s=arc-20160816; b=GLPdervheYnBIh4ivdDNlz//Kr8hWfiduINlXk1CGltWqpliIlSiCSYx0I28r+X+wW 9kZAYhc8rYbtYnQUjng+Vr5pmoP45aRq1tgdMrw5ZSwtR1N7EpoGjYZ/RHdKwCSdkaNF rh1Z6fPM6NDDt9kzyX5BY2PJN25+7YT4Xej/WbVPhNzDLMzbovIdjwrY4OKfpUL7WQJI lKjyr5X6ySFO3hcGh06RwraxgtllzoXnNlNNCFhozjfj+SP8IdKWPTalf25GPvoXfjW8 qVQ/B/82UuUg8PJgcPk4vGqSUlDSWhL0Llj0btWXPahgJSnWf/cKQTbEK6unXv/iE9n3 dl2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=p+H4dk0sCmS4N6TGv5dGqYskRQUoCbJg4+GQEi6ihPg=; b=zJa2Ea5qYJwzFmfx/F9z3oOtXqQ5/5oxxBnxpisdchkF4XUZoNNNpJHXORdVfZxOQc G13jbooqWzFwPhKcPTFWRzu+JYagZEjJsxV/pf1eAXKfK/2HtP0arme431gVm5fIkopT 49W+0knHOYu0cuPUrG1XPLop2TRdjArA3JJH6uZDuQSdqKH3i9ENTEFrAq5mu455ilSq QaI2GNBS3+U5B7q88PPvP08WRLZTSyDb0DnSZxoxPXk0cK+887sCmGvINPK6Swx3/6In HOd45P34DjlZnbSMwnSmhqqlpyIN1svAhZfq+oBJRYDHejwfk9FkaQXa8G8H9P+b1uBk v9Ng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Cq+UM1Ua; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m2si13374409plk.103.2017.11.22.00.09.05; Wed, 22 Nov 2017 00:09:16 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Cq+UM1Ua; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751631AbdKVII2 (ORCPT + 76 others); Wed, 22 Nov 2017 03:08:28 -0500 Received: from mail-ot0-f173.google.com ([74.125.82.173]:39055 "EHLO mail-ot0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751573AbdKVII1 (ORCPT ); Wed, 22 Nov 2017 03:08:27 -0500 Received: by mail-ot0-f173.google.com with SMTP id v15so12870208ote.6 for ; Wed, 22 Nov 2017 00:08:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=p+H4dk0sCmS4N6TGv5dGqYskRQUoCbJg4+GQEi6ihPg=; b=Cq+UM1UasVfsMy96wM51cbRcMWt85za6bkKCvY+Ff3O0eyFSZT8CFT+XRPpekrBEQF t/sLO6yvF3vdmMB65js1L6X30/ziprIkwhpWhlAgwe43F6/IZ38MuTaGrzC1sDh6wIQT xgaIELfWHVoyr08noyRHfSfiannYg5yQPR02HOuhKmQ06MSi2Q3V/19U7tHhmlGSpcah WZ6XHz5c39CdmuTy5z0F+ZjEVDGtiLg+j+/Xj8taLf6Wo72AJcWcCYfhN+oqcbHAl+dY umxlXSXHm/hMhiw6vxg5O2pHHY2wEqrJio1CpOHxaqjSNC5F/8/XwhQhC2z4KwmjDiNU oA6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=p+H4dk0sCmS4N6TGv5dGqYskRQUoCbJg4+GQEi6ihPg=; b=uf6RxnDo1C2T8FckOSb/08dScY5cOApdIw9QDncP5py0PdrAVLmfXh15njP3KOWSx3 97EaTFHm1dNWhFEIaRYyyFW3NEyuDIwxMd5hhI8B7GLDfx4H6qwSZvuZK88qo1EUhr13 O/TJEtpxDPKmPdvZsBggcLarUaw2OyJSsFM3V5PxAGnrMV+Ils25OP5UxlqPb3kLN6yX feergQNgFdf1MEfO0xBe0SixWjqUKWlz2XkueXGwTxULRH79huToHqE74TFWxXGvxtVU ryy3G2baMSI83+NXdJOPmaepwHPGG2wow1p13cV8tYbwRn+6Xd2tANUoCWe8KYbVwCxJ jk9g== X-Gm-Message-State: AJaThX4Q6Ol5d5KeHChJWO+DHewCOyeDssTTbtzdQhxYrNjgoutdAiog xkarycZjhPY2ZQymLWTLDczL7E9j7yGwoLGUfAs= X-Received: by 10.157.45.23 with SMTP id v23mr13786006ota.118.1511338106382; Wed, 22 Nov 2017 00:08:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.22.206 with HTTP; Wed, 22 Nov 2017 00:07:45 -0800 (PST) In-Reply-To: References: <20171006220504.7776-1-eric@anholt.net> <910a98ca-57f6-baca-73ac-f6c8c1ff04db@i2se.com> From: Loic Poulain Date: Wed, 22 Nov 2017 09:07:45 +0100 Message-ID: Subject: Re: [GIT PULL 1/2] bcm2835-dt-fixes-2017-10-06 To: Peter Robinson Cc: Marcel Holtmann , Stefan Wahren , Matt Hart , Linux Kernel Mailing List , bcm-kernel-feedback-list@broadcom.com, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel , Eric Anholt Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Peter, > So it seems it's actually working fine albeit the strange mac addr, no > idea what I was trying before, although there's an error about loading > firmware: > > [ 31.035291] Bluetooth: hci0: BCM: chip id 94 > [ 31.035801] Bluetooth: hci0: BCM: features 0x2e > [ 31.037483] Bluetooth: hci0: BCM43430A1 > [ 31.037498] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000 > [ 31.037694] bluetooth hci0: Direct firmware load for > brcm/BCM43430A1.hcd failed with error -2 > [ 31.037704] Bluetooth: hci0: BCM: Patch brcm/BCM43430A1.hcd not found Ok, think that's why you have this kind of 'default' address, you should be able to provision a valid address with btmgmt tool. The chip can work without applying patch file, original firmware is then executed, which is potentially more or less buggy. > By adding a firmware [1] to the location it actually now stops > working, although shows up with a hciconfig, and had the following > errors. > > [ 26.078038] Bluetooth: hci0: BCM: chip id 94 > [ 26.096797] Bluetooth: hci0: BCM: features 0x2e > [ 28.130753] Bluetooth: hci0 command 0x0c14 tx timeout > [ 36.322725] Bluetooth: hci0: BCM: Reading local name failed (-110) Really weird, because these steps are prior firmware loading, moreover on HCI command timeout, the HCI core is supposed to retry sending of the command, here nothing happened between [28.13] and [36.32].... Could you please try to load hci_uart.ko manually after boot to see if it could be related to some init timings/concurrency. Regards, Loic From 1584669594090601246@xxx Tue Nov 21 10:04:51 +0000 2017 X-GM-THRID: 1580547514768252392 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread