From: Balamurugan Mahalingam <mbalamurugan@atheros.com>
To: Suraj Sumangala <Suraj.Sumangala@Atheros.com>
Cc: Mahalingam Balamurugan <Mahalingam.Balamurugan@Atheros.com>,
"marcel@holtmann.org" <marcel@holtmann.org>,
"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"charubala@charubala.com" <charubala@charubala.com>
Subject: Re: [PATCH] Fix hidd showing different names for same device
Date: Wed, 20 Oct 2010 15:45:36 +0530 [thread overview]
Message-ID: <4CBEC148.1000606@atheros.com> (raw)
In-Reply-To: <4CBEBA32.3040806@Atheros.com>
Suraj Sumangala wrote:
> Hi Bala,
>
> On 10/20/2010 2:42 PM, Balamurugan Mahalingam wrote:
>
>> hidd shows different names for a same device when
>> connected from GUI and CLI
>>
>> Blueman and other GUIs use the string from ServiceName attribute as
>> device name in the SDP response, but hidd tool uses strings from
>> Service Description and Provider Name atrribute.
>>
>> SDP response from Microsoft Bluetooth device has extended ASCII
>> character 174(registered symbol) in its ServiceDescription attribute.
>> Android platform expects the device name to have only printable
>> characters and therefore GUI Crashes while connecting Microsoft
>> Bluetooth Mouse using hidd
>>
>> Using the ServiceName attribute from the SDP response
>> instead of ProviderName+ServiceDescription for device name in the
>> hidd tool solves both the issues.
>> ---
>>
>
> may be you can shorten the commit message. May be have something like this
>
> This patch lets hidd use ServiceName attribute from the SDP response
> instead of ProviderName+ServiceDescription for device name.
> SDP response from Microsoft Bluetooth device has extended ASCII
> character 174(registered symbol) in its ServiceDescription attribute.
> This causes some Bluetooth application which expects only printable
> characters as device name to crash.
>
> Regards
> Suraj
> .
>
>
Ok Suraj. I will send the patch once again
Thanks & Regards
Balamurugan Mahalingam
prev parent reply other threads:[~2010-10-20 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 9:12 [PATCH] Fix hidd showing different names for same device Balamurugan Mahalingam
2010-10-20 9:45 ` Suraj Sumangala
2010-10-20 10:15 ` Balamurugan Mahalingam [this message]
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=4CBEC148.1000606@atheros.com \
--to=mbalamurugan@atheros.com \
--cc=Mahalingam.Balamurugan@Atheros.com \
--cc=Suraj.Sumangala@Atheros.com \
--cc=charubala@charubala.com \
--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;
as well as URLs for NNTP newsgroup(s).