From mboxrd@z Thu Jan  1 00:00:00 1970
From: M. Braun <michael-dev@fami-braun.de>
Date: Wed, 26 Nov 2014 08:46:33 +0100
Subject: [ath9k-devel] queue priority mapping
In-Reply-To: <CAFfN3gVtvw4o38PSD-4CMrkpsqaYC=9xSjGfWDa8BM3t+v3-gw@mail.gmail.com>
References: <CAFfN3gX-Jtk2hh8tpBgvXkDgxbEjucOPevhJdYYXzt-0m-q9Dg@mail.gmail.com>	<5472F604.3020404@fami-braun.de>
	<CAFfN3gVtvw4o38PSD-4CMrkpsqaYC=9xSjGfWDa8BM3t+v3-gw@mail.gmail.com>
Message-ID: <54758559.6030901@fami-braun.de>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

Hi,

Am 25.11.2014 um 22:14 schrieb Hubert Feurstein:
> [...]
> Well, in fact it does. To understand my post you have to know the
> behaviour of ath_txq_setup. The point here is that on the first call
> of ath_txq_setup(..ATH9K_TX_QUEUE_DATA..), hw-queue 0 is returned. On
> the second call hw-queue 1 is returned, ... . And IEEE80211_AC_VO = 0,
> so hw-queue 0 is assigned, which is wrong in my opinion. But the right
> place to fix this would be ath_txq_setup itself.

sorry, I looked at the ATH_TXQ_SETUP macro in ath9k.h instead of the
ath_txq_setup function in xmit.c.

Regards,
 M. Braun