From: Chris Mason <clm@fb.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] I have no idea what I'm doing
Date: Tue, 14 Jul 2015 17:01:07 -0400 [thread overview]
Message-ID: <20150714210107.GF27622@ret.masoncoding.com> (raw)
In-Reply-To: <2C969CCF-92B3-4835-B9F5-550A9DEC4FF2@holtmann.org>
On Tue, Jul 14, 2015 at 10:58:50PM +0200, Marcel Holtmann wrote:
> Hi Chris,
>
> >>>> Actually can you run something like "hciconfig hci0 version" and see
> >>>> if it really is a Broadcom chip in there or if Apple switched vendors
> >>>> and we are accidentally assuming it is Broadcom while in reality it is
> >>>> not. If it is not then the quirk might actually not apply either
> >>>> anymore.
> >>>
> >>> mason@ret ~> hciconfig hci0 version
> >>> hci0: Type: BR/EDR Bus: USB
> >>> BD Address: 60:03:08:8D:0D:A9 ACL MTU: 1021:8 SCO MTU: 64:1
> >>> HCI Version: 4.0 (0x6) Revision: 0x21ae
> >>> LMP Version: 4.0 (0x6) Subversion: 0x414e
> >>> Manufacturer: Broadcom Corporation (15)
> >>
> >> so it is a Broadcom. What MacBook is this anyway?
> >
> > macbookpro 13" from 2013 (newer model in '13)
>
> besides having that Bluetooth module for testing, I also have that actual Macbook. And I did test this. It worked fine for me. Maybe some OS X update messed with the firmware. Worth while checking.
This only runs linux, I don't dual boot.
-chris
next prev parent reply other threads:[~2015-07-14 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 19:16 [PATCH] I have no idea what I'm doing Chris Mason
2015-07-14 19:49 ` Marcel Holtmann
2015-07-14 19:59 ` Chris Mason
2015-07-14 20:49 ` Marcel Holtmann
2015-07-14 20:53 ` Chris Mason
2015-07-14 20:58 ` Marcel Holtmann
2015-07-14 21:01 ` Chris Mason [this message]
2015-07-14 21:11 ` Marcel Holtmann
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=20150714210107.GF27622@ret.masoncoding.com \
--to=clm@fb.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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