From: Robert Schneider <Robert.Schneider@aramar.de>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: KORG nanoKONTROL Studio ... again
Date: Sun, 20 May 2018 15:46:00 +0200 [thread overview]
Message-ID: <f557429f-e61b-1ac6-c894-bc84db45c65c@aramar.de> (raw)
In-Reply-To: <CABBYNZ+HQ2CeuHLrx1w5k6BK-AV8SYbdE_-TOej522cwf-BtUg@mail.gmail.com>
On 20.05.2018 14:14, Luiz Augusto von Dentz wrote:
[...]
> The info says:
>> [bluetooth]# info 60:F1:89:28:DA:1F
>> Device 60:F1:89:28:DA:1F (public)
>> Name: nanoKONTROL Studio
>> Alias: nanoKONTROL Studio
>> Appearance: 0x0080
>> Icon: computer
>> Paired: no
>> Trusted: yes
>> Blocked: no
>> Connected: no
>> LegacyPairing: no
>> UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
>> UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
>> UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
>> UUID: Vendor specific (03b80e5a-ede8-4b33-a751-6ce34ec4c700)
>> UUID: Vendor specific (d0611e78-bbb4-4591-a5f8-487910ae4366)
> From the looks of it seems the device is not using the standard MIDI
> service but vendor specific ones which don't have support.
Hm, 03b80e5a-ede8-4b33-a751-6ce34ec4c700 seems to be the MIDI service, doesn't
it? It is listed up there, as a Vendor specific code, though.
[...]
next prev parent reply other threads:[~2018-05-20 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 13:41 KORG nanoKONTROL Studio ... again Robert Schneider
2018-05-20 12:14 ` Luiz Augusto von Dentz
2018-05-20 13:46 ` Robert Schneider [this message]
2018-05-20 14:29 ` Luiz Augusto von Dentz
2018-05-20 14:35 ` Robert Schneider
2018-05-23 17:23 ` Robert Schneider
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=f557429f-e61b-1ac6-c894-bc84db45c65c@aramar.de \
--to=robert.schneider@aramar.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).