On Sun, 2011-01-23 at 15:31 +0530, Sujith wrote:
> * The host driver has no way of knowing if the FW failed to send out a frame,
> so keeping track of pending frames is impossible. Am not sure if
> ATH9K_TXERR_FILT
> is similar to TX_STATUS_FAIL_DEST_PS in iwlagn (I think not), so that can't
Johannes Berg wrote:
> On Sat, 2011-01-22 at 09:02 +0530, Sujith wrote:
>
> > It does make it a bit neat to have such a mechanism. And for AP mode, I
> > would think
> > that it's kinda essential unless someone comes with an ingenious way of
> > solving
> > the PS race for drivers that don't set
On Sat, 2011-01-22 at 09:02 +0530, Sujith wrote:
> It does make it a bit neat to have such a mechanism. And for AP mode, I would
> think
> that it's kinda essential unless someone comes with an ingenious way of
> solving
> the PS race for drivers that don't set IEEE80211_HW_REPORTS_TX_ACK_STATUS
Christian Lamparter wrote:
> You only have to have a sane tx status if the IEEE80211_TX_CTL_REQ_TX_STATUS
> flag is set. In all other cases, the IEEE80211_TX_STAT_ACK handling is
> *optional*. In fact if you don't set the TX_STAT_ACK flag, mac80211 will
> automatically do the right thing when it se
On Saturday 22 January 2011 04:32:02 Sujith wrote:
> Sujith wrote:
> > Sujith wrote:
> > > What about hardware that doesn't report any kind of TX status information
> > > at all ?
> > > Currently, there is no way to determine whether the frame has actually
> > > gone out,
> > > all that can be kn
Sujith wrote:
> Sujith wrote:
> > What about hardware that doesn't report any kind of TX status information
> > at all ?
> > Currently, there is no way to determine whether the frame has actually gone
> > out,
> > all that can be known is that it was pushed to the target.
>
> Am curious how carl
Sujith wrote:
> What about hardware that doesn't report any kind of TX status information at
> all ?
> Currently, there is no way to determine whether the frame has actually gone
> out,
> all that can be known is that it was pushed to the target.
Am curious how carl9170 gets the TX status ?
Is t
Christian Lamparter wrote:
> But what seems to be strange is the tx feedback...
> Because it looks like ath9k_htc just sets IEEE80211_TX_STAT_ACK
> for every frame, which obviously can't be "true", right? ;)
>
> This might also break mac80211's *unicast buffering*.
>
> Because the code in ieee802
On Friday 21 January 2011 03:55:51 Sujith wrote:
> This series is the preliminary work for enabling AP mode for ath9k_htc.
>
> A firmware update is needed, place look at:
> http://wireless.kernel.org/en/users/Drivers/ath9k_htc#AP_Mode
>
> Known issues:
>
> * Beacon misses under heavy TX load
>
Sujith wrote:
> This series is the preliminary work for enabling AP mode for ath9k_htc.
>
A unified patchset can be obtained here:
http://wireless.kernel.org/en/users/Drivers/ath9k_htc#AP_Mode
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k
This series is the preliminary work for enabling AP mode for ath9k_htc.
A firmware update is needed, place look at:
http://wireless.kernel.org/en/users/Drivers/ath9k_htc#AP_Mode
Known issues:
* Beacon misses under heavy TX load
( hopefully, a fix would be sent out soon).
This has not been tes
11 matches
Mail list logo
