From: Larry Finger <Larry.Finger@lwfinger.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Xi Ruoyao <xry111@outlook.com>,
"Gustavo F. Padovan" <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Drake <drake@endlessm.com>
Subject: Re: [PATCH] Bluetooth: btusb: Add Realtek devices into module device table
Date: Mon, 22 Jun 2015 09:23:52 -0500 [thread overview]
Message-ID: <55881A78.7060203@lwfinger.net> (raw)
In-Reply-To: <B0BB2A08-47CF-405D-9ACE-528550DF8337@holtmann.org>
On 06/22/2015 05:33 AM, Marcel Holtmann wrote:
Marcel,
> these Realtek devices are causing the most messy setup in a generic driver. And Bluetooth USB support has been really clean and simple for the last 10 years. I really wonder how many ways this gets done wrong before someone gets a clue and gets this right. At the end of the day this USB transport is 15 years old.
>
> Anyway, for obvious reasons the content of /sys/kernel/debug/usb/devices should be included here so that someone can actually look at how the USB endpoints are configured.
I cannot disagree about the messiness of the Realtek setup.
I hope that Xi's posting of the /sys file will help. Unfortunately, I do not
have ready access to one of these devices, but I'm making arrangements to gain
ssh access tomorrow so that I can test any suggested patches.
Larry
next prev parent reply other threads:[~2015-06-22 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 21:53 [PATCH] Bluetooth: btusb: Add Realtek devices into module device table Xi Ruoyao
2015-06-20 21:58 ` Marcel Holtmann
2015-06-21 1:12 ` Larry Finger
2015-06-21 4:11 ` Xi Ruoyao
2015-06-21 4:23 ` Xi Ruoyao
2015-06-22 10:33 ` Marcel Holtmann
2015-06-22 12:01 ` Xi Ruoyao
2015-06-22 14:23 ` Larry Finger [this message]
2015-06-22 15:01 ` Xi Ruoyao
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=55881A78.7060203@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=drake@endlessm.com \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=xry111@outlook.com \
/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