Hi Mikel, On Wed, Dec 12, 2012, Mikel Astiz wrote: > I'm a bit confused with these recent changes. I haven't been following > this closely so I guess I'm missing the Big Plan but let me start with > the basics: both bluetoothd and obexd repositories were merged but I > believe both daemons are still going to be separate daemons, is this > correct? > > If yes, it makes sense that obexd makes use of the "external profile" > infrastructure. > > But in that case, why would we add any obex-specific code into > bluetoothd? My understanding was that, if a profile is implemented as > an external profile, the bluetoothd core would not be aware of it. No, bluetoothd still takes care of SDP record registration, server/client socket handling, authorization, etc. Some external profiles (like HFP implemented through oFono) also take part in the Device.Connect connection procedure (this is particularly important for HFP since it needs to be the first of the audio profiles to be connected). >From the L2CAP/RFCOMM connection establishment onwards the external profile takes over though through the NewConnection method. 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
