On Mon, 16 Apr 2012 15:57:48 +0300
Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote:
> Hi Antonio,
>
> On Mon, Feb 13, 2012, Antonio Ospite wrote:
> > +int btd_device_set_trusted(const char *adapter_address,
> > + const char *device_address,
> > + char *name,
> > + uint16_t vendor_id_source,
> > + uint16_t vendor_id,
> > + uint16_t product_id,
> > + uint16_t version_id,
> > + const char *uuid)
> > +{
>
> If you have a function called set_trusted then that's *all* it should
> do. You have six other parameters there that have *nothing* to do with
> the function name.
Well that exposes my confusion/ignorance about what a "trusted device"
is, from what see, to make a device look fully trusted to BlueZ, it is
not enough to just call:
write_trust(adapter_address, device_address, "[all]", TRUE);
a bunch of other properties are needed (uuids, sdp records), maybe the
problem is about defining what I want, maybe I want a
_statically_trusted_ device? I don't know if that even makes sense in
bluetooth terminology.
The point here is that we are setting these parameters BEFORE the
devices connects via bluetooth, in fact they are set when the device is
connected via USB for the cable pairing step.
> Also, as I mentioned in my previous email the full
> use case for all of these should be understood (which also implies the
> code that uses them being available) before anything gets added to the
> bluetoothd exported API.
You are right, of course, I'll prepare a more detailed text which
explains WHAT I need to do and WHY, and hopefully you can guide me
about HOW to do that properly.
Thanks,
Antonio
--
Antonio Ospite
http://ao2.it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
Attachment:
pgpJYh85grwFx.pgp
Description: PGP signature
