From: Larry Finger <Larry.Finger@lwfinger.net>
To: Daniel Drake <drake@endlessm.com>
Cc: "Marcel Holtmann" <marcel@holtmann.org>,
"Gustavo F. Padovan" <gustavo@padovan.org>,
"Johan Hedberg" <johan.hedberg@gmail.com>,
"Linux Bluetooth mailing list" <linux-bluetooth@vger.kernel.org>,
陈艳萍 <champion_chen@realsil.com.cn>
Subject: Re: [PATCH v4] Bluetooth: btusb: Add Realtek 8723A/8723B/8761A/8821A support
Date: Fri, 13 Feb 2015 12:49:18 -0600 [thread overview]
Message-ID: <54DE472E.7070207@lwfinger.net> (raw)
In-Reply-To: <CAD8Lp46wqiiK0h=6kCKh8mVFAUqVEwojo1DKja2h_3ugJZ6vGg@mail.gmail.com>
On 02/12/2015 06:31 PM, Daniel Drake wrote:
> On Thu, Feb 12, 2015 at 6:27 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>>> +#define RTL_EPATCH_SIGNATURE "Realtech"
>>
>>
>> Typo here. It should be Realtek.
>
> If it is a typo, it is a typo from Realtek :)
> The firmware includes this signature and it is what the vendor code checks for.
>
> const uint8_t RTK_EPATCH_SIGNATURE[8] = {0x52, 0x65, 0x61, 0x6C, 0x74,
> 0x65, 0x63, 0x68};
Sorry, I should have decoded that string.
>
>>> +#define RTL_ROM_LMP_3499 0x3499
>>> +#define RTL_ROM_LMP_8723A 0x1200
>>> +#define RTL_ROM_LMP_8723B 0x8723
>>> +#define RTL_ROM_LMP_8821A 0x8821
>>> +#define RTL_ROM_LMP_8761A 0x8761
>>
>>
>> I just got a report for an lmp_subversion of 0x4ce1 on an RTL8723BE. The
>> above list and the table below may need expanding. We are still testing.
>
> Keep in mind, it is normal for the lmp_subversion to change once the
> firmware has been uploaded.
> That list is only a list of firmware versions that must be replaced.
I think the report was for a device for which firmware was not loaded as the
lmp_subversion was not recognized. I will be rechecking the full dmesg output.
I have a few minor comments. My log shows the following:
[ 4262.901871] Bluetooth: hci0: hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
[ 4262.901874] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b
lmp_ver=06 lmp_subver=8723
Those two show the same information. The one in btusb_setup_realtek() should be
removed.
I would prefer to see a logging of the file name of the firmware that was loaded
in btusb_setup_rtl8723b(). That will make it easier to interpret any "rtl:
assuming no firmware upload needed." messages in btusb_setup_realtek().
When bringing my laptop out of sleep, the firmware was reloaded, but Bluetooth
did not work until the driver was unloaded and reloaded. If you have any
thoughts please let me know.
Larry
next prev parent reply other threads:[~2015-02-13 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 0:08 [PATCH v4] Bluetooth: btusb: Add Realtek 8723A/8723B/8761A/8821A support Daniel Drake
2015-02-13 0:27 ` Larry Finger
2015-02-13 0:31 ` Daniel Drake
2015-02-13 18:49 ` Larry Finger [this message]
2015-02-13 18:54 ` Daniel Drake
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=54DE472E.7070207@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=champion_chen@realsil.com.cn \
--cc=drake@endlessm.com \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.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