Hi Marcel, On Fri, Apr 15, 2011, Marcel Holtmann wrote: > > > + BDADDR_TYPE_LE_PUBLIC, > > > + BRADDR_TYPE_LE_RANDOM > > > +}; > > I am also not sure the we should have this BR/EDR differentiation since > the specification only talks about public and random addresses. And we > should follow the specification type value here. I am against > introducing our enum here. The HCI specification only has values for public and random because everywhere they are used it is already clear from the context (the HCI command or event in question) if we're talking about LE or BR/EDR. We on the other hand don't have this contextual information with the mgmt_pair_device command. Saying "public" there could mean both BR/EDR public or LE public, i.e. an enum with just two possible values is not going to be of much use to us. Because of this difference between our API and that of HCI I don't think it's fair to apply the HCI convention/restriction to us. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
