On Tue, Jan 25, 2011 at 9:47 PM, Pavan Savoy <pavan_savoy@xxxxxxxx> wrote: > On Tue, Jan 25, 2011 at 9:41 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: >> Hi Johan, >> >>> > >> 1. are there controllers there which even after doing hci0 down, >>> > >> allows other devices to be scanned? >>> > >> for those what do hci0 down mean ? radio not switched off ? >>> > > >>> > > Good point, perhaps this is driver dependent, so we do it just be safe guard. >>> > >>> > I hope all devices and drivers out there consider the hci0 down as the >>> > radio OFF, >>> > I don't think there is a reason for it to be otherwise.... >>> > so why the safe-guard ? >>> >>> IIRC Marcel added this due to paranoia with the non-connectable GAP test >>> case with the BITE tester. The test kept failing even though the device >>> was in DOWN state. >> >> we also had the case where we considered non-connectable as off when the >> HCI devdown was not working properly. However this is a long time ago >> and has been fixed properly. So we might can remove this now. > > Oo... > I want to send the patch, I want to send the patch .. > Can I please ..... i've posted the patch.. > >> Regards >> >> Marcel >> >> >> > -- 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
