Hi David, > > The block-based flow control is a missing piece, but the AMP type > > extension has been merged upstream. We can create HCI_BREDR and > > HCI_80211 controllers now. The AMP controllers are for now forced to be > > raw devices, but that can be changed easily once we have the controller > > init for AMP up and ready. > > Why HCI_80211 and not HCI_AMP? The stack shouldn't care what the AMP's > radio actually is and with some devices (e.g., standard SDIO ones) it's > not even possible to tell what the radio is. we will be adding a HCI_UWB once that specification gets ratified. And the controller type is an official piece of information inside the AMP manager. That part needs to know which type of AMP it is. Also the driver actually should know what type of AMP it is. I see your point that for fully generic HCI transports they might not know the type upfront and we need to handle that. We will cross that bridge when we come to it. Right now we just got started. 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
