From: Marcel Holtmann <marcel@holtmann.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Francisco Alecrim <francisco.alecrim@openbossa.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Emit Adapter.PropertyChanged when UUIDs change
Date: Mon, 29 Mar 2010 18:21:10 -0700 [thread overview]
Message-ID: <1269912070.11714.222.camel@localhost.localdomain> (raw)
In-Reply-To: <20100329225643.GA5460@jh-x301>
Hi Johan,
> > >> IMO, it should be the same list as we export in extended inquiry
> > >> response, so perhaps we could use the data from
> > >> create_ext_inquiry_response which already filter those away. Perhaps
> > >> some refactoring could also be done since this code seems to be called
> > >> multiple times in case of new services because it also changes class
> > >> which then triggers create_ext_inquiry_response again.
> >
> > I'm not so sure about it but create_ext_inquiry_response list all
> > services to any adapters. Shouldn't it list just services per
> > adapter(access_db)?
>
> It should be per-adapter (or records registered to BDADDR_ANY) since EIR
> is also per-adapter, so looks like a possible bug in the current
> implementation.
>
> Btw, another restriction to note with the current EIR UUID list
> implementation is that it only supports 16-bit UUIDs. The EIR format
> itself would support also 32 and 128 bit formats but probably for
> simplicity these have been left out. The Adapter UUIDs list should
> however contain all UUIDs (with the exceptions that we already
> discussed).
it should also contain the UUID-128 ones (the UUID-32 are pointless and
with LE they are gone for good). The reason why these were left out is
because it is pretty hard to fit them into the limited space of EIR. If
you are up for fixing this, then I am more than happy to have this. I
think we need to introduce some priority mapping here to decide which
UUID list to cut in favor of others. Same as how we can shortcut the
device name etc.
So in general the DID information and at least a short device name
should be present. For the short name, we might need another config file
option or some plugin way of retrieving the short name. Also I want to
have the TX power information available if the chip supports it.
The rest of the space can be used for UUIDs in whatever way fits. The
more UUIDs are in the list the better actually.
Regards
Marcel
prev parent reply other threads:[~2010-03-30 1:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 22:54 [PATCH v2 1/2] Report local services(UUIDs) through DBus Francisco Alecrim
2010-03-26 22:54 ` [PATCH v2 2/2] Emit Adapter.PropertyChanged when UUIDs change Francisco Alecrim
2010-03-29 7:45 ` Johan Hedberg
2010-03-29 8:29 ` Marcel Holtmann
2010-03-29 18:48 ` Luiz Augusto von Dentz
2010-03-29 21:52 ` Johan Hedberg
2010-03-29 22:12 ` Francisco Alecrim
2010-03-29 22:56 ` Johan Hedberg
2010-03-30 1:21 ` Marcel Holtmann [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=1269912070.11714.222.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=francisco.alecrim@openbossa.org \
--cc=johan.hedberg@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).