On Tue, Jan 24, 2012 at 9:45 AM, Peter Krystad <pkrystad@xxxxxxxxxxxxxx> wrote: >> On Jan 24, 2012, at 12:57 AM, Andrei Emeltchenko wrote: >> > On Tue, Jan 24, 2012 at 12:36:23AM -0800, Greg Hazel wrote: >> >> On Jan 24, 2012, at 12:27 AM, Andrei Emeltchenko wrote: >> >>> On Mon, Jan 23, 2012 at 08:15:16PM -0800, Greg Hazel wrote: >> >>>> >> >>>> I'm trying to set BT_AMP_POLICY on an RFCOMM socket to >> >>>> BT_AMP_POLICY_PREFER_AMP. In return I'm getting "Operation not supported >> >>> > >> >>> BTW: Why would you need to set this? Functionality is not supported yet so >> >>> nothing will change. >> >> >> >> Oh, I had not made it far enough into bluez to notice it had not been implemented. My >> question still stands I suppose, but is obviously predicated on support being added >> eventually. > > Since l2cap ertm is required for channels on AMP the rfcomm layer is unnecessary, it makes > more sense for obex profiles to be modified to use l2cap ertm sockets directly, which do/will > support AMP. I agree that rfcomm is no longer crucial in the presence of ertm. However, there are existing applications which use rfcomm directly, which could benefit from the AMP functionality with only a tiny setsockopt modification, instead of switching to l2cap instead. Mine is one such application. -Greg -- 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
