From: pbrobinson@gmail.com (Peter Robinson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] bcm2835-dt-fixes-2017-10-06
Date: Tue, 21 Nov 2017 10:03:53 +0000 [thread overview]
Message-ID: <CALeDE9NpTQCSC7AJ1NhkNuA-FgMQSme8LUJtyizXirthCh6chA@mail.gmail.com> (raw)
In-Reply-To: <CAM9fo8MktM-WX-AGFCLeCrcoRDR4XjR09BGcbNb5X4G4yVaU2A@mail.gmail.com>
Hi Loic,
>> With 4.14 I get the following, the address doesn't look right, do you
>> have a link to the serdev patch headed to 4.15?
>>
>> # hciconfig
>> hci0: Type: Primary Bus: UART
>> BD Address: AA:AA:AA:AA:AA:AA ACL MTU: 1021:8 SCO MTU: 64:1
>> DOWN
>> RX bytes:542 acl:0 sco:0 events:11 errors:0
>> TX bytes:77 acl:0 sco:0 commands:17 errors:0
>
>
> HCI link seems ok since you have some events/commands in the stats.
> It could be a firmware issue, missing or at the wrong place (BCM43xxx.hcd).
> Does the hci_bcm request firmware call fail ? (dev_info message).
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
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)
Thanks,
Peter
next prev parent reply other threads:[~2017-11-21 10:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 22:05 [GIT PULL 1/2] bcm2835-dt-fixes-2017-10-06 Eric Anholt
2017-10-06 22:05 ` [GIT PULL 2/2] bcm2835-dt-next-2017-10-06 Eric Anholt
2017-10-06 22:21 ` Florian Fainelli
2017-10-06 22:14 ` [GIT PULL 1/2] bcm2835-dt-fixes-2017-10-06 Florian Fainelli
2017-10-31 17:00 ` Matt Hart
2017-11-01 9:37 ` Peter Robinson
2017-11-01 12:05 ` Stefan Wahren
2017-11-01 12:09 ` Peter Robinson
2017-11-01 12:16 ` Marcel Holtmann
2017-11-16 16:44 ` Peter Robinson
2017-11-16 20:21 ` Eric Anholt
2017-11-17 12:16 ` Peter Robinson
[not found] ` <CAM9fo8MktM-WX-AGFCLeCrcoRDR4XjR09BGcbNb5X4G4yVaU2A@mail.gmail.com>
2017-11-21 10:03 ` Peter Robinson [this message]
2017-11-22 8:07 ` Loic Poulain
2017-11-01 13:06 ` Matt Hart
2017-11-01 17:44 ` Stefan Wahren
2017-11-02 8:33 ` Matt Hart
2017-11-01 16:54 ` Eric Anholt
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=CALeDE9NpTQCSC7AJ1NhkNuA-FgMQSme8LUJtyizXirthCh6chA@mail.gmail.com \
--to=pbrobinson@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).