Right. So the weight table for Kite/Kiwi: wait_beacon | qcu_priority | rx_clear | wlan level 0 | 0 | 0 | wlan_weight[0:1] 0 | 0 | 1 | wlan_weight[3:2] 0 | 1 | 0 | wlan_weight[5:4] 0 | 1 | 1 | wlan_weight[7:6] 1 | 0 | 0 | wlan_weight[9:8] 1 | 0 | 1 | wlan_weight[11:10] 1 | 1 | 0 | wlan_weight[13:12] 1 | 1 | 1 | wlan_weight[15:14] bt_priority | bt freq | bt_tx_rx | bt_level 0 | 0 | 0 | bt_weight[0:1] 0 | 0 | 1 | bt_weight[3:2] 0 | 1 | 0 | bt_weight[5:4] 0 | 1 | 1 | bt_weight[7:6] 1 | 0 | 0 | bt_weight[9:8] 1 | 0 | 1 | bt_weight[11:10] 1 | 1 | 0 | bt_weight[13:12] 1 | 1 | 1 | bt_weight[15:14] wait_beacon is whether we're waiting for a beacon in STA mode. No idea how this works in hostap mode, but see below. qcu_priority is whether it's a low or high queue priority. Any queue above the "queue threshold" value in one of the BT config registers (see the source) is a high priority queue and is 1 here. rx_clear is whether we're busy bt_priority - the bt priority line bt_freq - no idea bt_tx_rx - whether the BT module is transmitting (3 wire only I guess, irrelevant for 2 wire) I hope that's enough to get started on what you're trying to achieve. Please share your results! Adrian -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
