2009/3/30 卞磊 <mykofzone@xxxxxxxxx>: > Hi All, > I made a mistake when writing the email, I have not complete my question. > > 2009/3/31 卞磊 <mykofzone@xxxxxxxxx>: >> Hi All, >> I have a stlc2500c which is a Bluetooth 1.2 chip. When debuging >> function 'hci_connect', i found the hci link type of the arguments was >> SCO_LINK, because i enabled 'lmp_esco_capable' in my kernel, it call >> 'hci_setup_sync' to setup eSCO link. > > But when i check connection by 'hcitool con', the hcitool show it was > a SCO link. So, is it a SCO link or eSCO link? Thanks. hcitool con will report eSCO if it is eSCO, so you have a SCO link. hci_setup_sync can be used for both SCO and eSCO, and the chipset and/or the host stack will fall back to SCO if eSCO parameters can not be negotiated. An LMP log will show why. Nick -- 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
