Linux bluetooth development
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "Ben-melech, Shiran" <shiran.ben-melech@intel.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: "complex" Bluetooth handling
Date: Wed, 15 Jun 2016 09:59:29 +0200	[thread overview]
Message-ID: <dc7e087d-59ed-f9cf-381a-05c0e8b8ca3f@gmail.com> (raw)
In-Reply-To: <CABBYNZL-BYpN=fuHfv4vdjeWPGAicn+hveXPFPCngxAwVR8LdA@mail.gmail.com>

Il 15/06/2016 09:53, Luiz Augusto von Dentz ha scritto:
>
> I guess you don't want a mixed topology with both LE/BR, in that case
> you will probably need to work in support GATT over BR/EDR properly
> since the focus was on LE link. For audio, and media in general, that
> have been a lot of work around car IVI systems, so provided you use
> the same components (e.g. PulseAudio, oFono) this should work out of
> the box.

Yes, PulseAudio and oFono "work out of the box" after fixing a looooot 
of issues :)
But I still need a library to handle them for example to enable them or 
manage connections, pairing, trusting, etc.. from my application.

About LE it's the only topology I need to exchange data, i.e. no need 
for "old" RFCOMM.
But still I need to have both a GATT server and an ANCS consumer (which 
should be a GATT client acting as a Central as far as I understand) 
working at the same time.

Thanks
Marco


      reply	other threads:[~2016-06-15  7:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15  5:10 "complex" Bluetooth handling Marco Trapanese
2016-06-15  6:54 ` Ben-melech, Shiran
2016-06-15  7:20   ` Marco Trapanese
2016-06-15  7:53     ` Luiz Augusto von Dentz
2016-06-15  7:59       ` Marco Trapanese [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=dc7e087d-59ed-f9cf-381a-05c0e8b8ca3f@gmail.com \
    --to=marcotrapanese@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=shiran.ben-melech@intel.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