DBus P2PDevice API

Johannes Berg johannes at sipsolutions.net
Tue Sep 20 13:53:15 EDT 2011


On Tue, 2011-09-20 at 10:12 -0700, Craig Dowell wrote:
> I looked at the “RequestedDeviceTypes” key
> handling, and its variant value is supposed to be an array of
> WPAS_DBUS_TYPE_BINARRAY.  WPAS_DBUS_TYPE_BINARRAY is defined as
> DBUS_NUMBER_OF_TYPES + 100 which turns out to be 116, which is ascii
> ‘t’.  This tells me I should send an array of uint64_t (“at”) in the
> variant value.  I don’t understand why this is not just defined to be
> ‘t’ instead of being based on the number of DBus types by the way (or
> ‘y’ which I would actually more expect to see there given what it
> apparently does).

No, this is actually supposed to be "aay". The binarray thing is just an
internal thing to make the code simpler.

> Also, from what I can make out from the README-P2P, I would expect Find
> to also take a “type” key with the variant value being a string value
> containing either “social” or “progressive”, but this seems to be
> hardcoded to P2P_FIND_ONLY_SOCIAL in the DBus method handler.  

There's a patch floating around to fix that.

johannes




More information about the HostAP mailing list