linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH v3 1/9] doc/media-api: Enable MediaEndpoint to expose remote SEP
Date: Mon, 8 Apr 2019 11:53:11 +0200	[thread overview]
Message-ID: <20190408095311.5pbc4gk62uu4fmmv@pali> (raw)
In-Reply-To: <CABBYNZJCOnudwGi6Km=m2SWSvV8v_zz3_Pd-+-ek9H785J4BkQ@mail.gmail.com>

On Monday 08 April 2019 12:47:40 Luiz Augusto von Dentz wrote:
> Hi Pali,
> 
> On Mon, Apr 8, 2019 at 12:41 PM Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> wrote:
> > > $ qdbus --system org.bluez /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/sep1 org.bluez.MediaEndpoint1.UUID
> > > 0000110a-0000-1000-8000-00805f9b34fb
> > >
> > > $ qdbus --system org.bluez /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/sep2 org.bluez.MediaEndpoint1.UUID
> > > 0000110a-0000-1000-8000-00805f9b34fb
> 
> Btw, 110a is a remote source I wonder if why you were saying they were
> sinks? Or you were referring to the local role?

Main problem is that these two UUIDs are same. There should be one for
remote source and one remote sink. Remote source is local sink role.

> > > So this is a clear bug.
> >
> > I will send a fix shortly.
> >
> > --
> > Luiz Augusto von Dentz

-- 
Pali Rohár
pali.rohar@gmail.com

  reply	other threads:[~2019-04-08  9:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22 13:45 [PATCH v3 1/9] doc/media-api: Enable MediaEndpoint to expose remote SEP Luiz Augusto von Dentz
2019-01-22 13:45 ` [PATCH v3 2/9] a2dp: Expose " Luiz Augusto von Dentz
2019-01-22 13:45 ` [PATCH v3 3/9] doc/media-api: Add Endpoint property to MediaTransport Luiz Augusto von Dentz
2019-01-22 13:45 ` [PATCH v3 4/9] a2dp: Implement MediaTransport.Endpoint Luiz Augusto von Dentz
2019-01-22 13:45 ` [PATCH v3 5/9] doc/settings-storage: Add Endpoint group to cache Luiz Augusto von Dentz
2019-01-22 13:45 ` [PATCH v3 6/9] a2dp: Cache remote endpoints Luiz Augusto von Dentz
2019-01-22 13:45 ` [PATCH v3 7/9] doc/media-api: Add Device property to MediaEndpoint Luiz Augusto von Dentz
2019-01-22 13:45 ` [PATCH v3 8/9] a2dp: Add implementation of MediaEndpoint.Device Luiz Augusto von Dentz
2019-01-22 13:45 ` [PATCH v3 9/9] a2dp: Add reverse discovery Luiz Augusto von Dentz
2019-01-22 14:20 ` [PATCH v3 1/9] doc/media-api: Enable MediaEndpoint to expose remote SEP Luiz Augusto von Dentz
2019-01-22 17:56   ` Pali Rohár
2019-01-23 11:24     ` Luiz Augusto von Dentz
2019-01-27  2:00       ` Pali Rohár
2019-03-27 11:14         ` Pali Rohár
2019-04-19  8:03           ` Pali Rohár
2019-04-19 10:04             ` Luiz Augusto von Dentz
2019-04-19 11:01               ` Pali Rohár
2019-04-19 11:48                 ` Luiz Augusto von Dentz
2019-04-19 12:04                   ` Pali Rohár
2019-04-20  6:43                     ` Luiz Augusto von Dentz
2019-04-20  7:00                       ` Pali Rohár
2019-04-20  7:31                         ` Luiz Augusto von Dentz
2019-04-05 16:47       ` Pali Rohár
2019-04-08  9:41         ` Luiz Augusto von Dentz
2019-04-08  9:47           ` Luiz Augusto von Dentz
2019-04-08  9:53             ` Pali Rohár [this message]
2019-04-19  8:03           ` Pali Rohár
2019-05-03  6:17       ` Pali Rohár

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=20190408095311.5pbc4gk62uu4fmmv@pali \
    --to=pali.rohar@gmail.com \
    --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).