From: Szymon Janc <szymon.janc@codecoup.pl>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC] doc: Add DeviceClassic1 and DeviceSmart1 interfaces
Date: Fri, 11 Mar 2016 10:56:10 +0100 [thread overview]
Message-ID: <1953352.ZcJQUXlYx9@ix> (raw)
In-Reply-To: <CABBYNZKK6eCVouvsQMGfQdYA-6RY02O05q7yMsjtHfPL1kBu7A@mail.gmail.com>
Hi Marcel, Luiz,
On Sunday 06 March 2016 16:34:53 Luiz Augusto von Dentz wrote:
> Hi Marcel,
>
> On Fri, Mar 4, 2016 at 7:32 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
> > Hi Szymon,
> >
> >> This interfaces will provide per tranport capabilities of remote
> >> devices. Eventually leading to deprecation of Device1 interface.
> >
> > so I not like the naming DeviceClassic1 and DeviceSmart1 at all. Nobody
> > uses these terms widely that they are easily recognizable and can be
> > associated. I also do not want to follow Bluetooth SIG marketing and logo
> > terms. They might change and then we are stuck with it.
> IMO they are better than LE and BR/EDR, but perhaps you have something
> better in mind. Btw, this does bring the question if we should do
> something similar to the Adapter interface, although there are a
> little less conflicts because there more LE specific interfaces.
DeviceLE1 and DeviceBR{EDR}1 ?
Or maybe Device2 (that would be BREDR only) and DeviceLE1 ?
--
pozdrawiam
Szymon Janc
prev parent reply other threads:[~2016-03-11 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 15:53 [RFC] DeviceClassic1 and DeviceSmart1 interfaces Szymon Janc
2016-03-04 15:53 ` [RFC] doc: Add " Szymon Janc
2016-03-04 16:29 ` Luiz Augusto von Dentz
2016-03-04 17:32 ` Marcel Holtmann
2016-03-06 14:34 ` Luiz Augusto von Dentz
2016-03-11 9:56 ` Szymon Janc [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=1953352.ZcJQUXlYx9@ix \
--to=szymon.janc@codecoup.pl \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--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