All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Dirty Laundry List
Date: Thu, 20 Nov 2008 11:32:47 -0800	[thread overview]
Message-ID: <20081120193247.GC5899@tesla> (raw)
In-Reply-To: <18725.36541.901179.14716@gargle.gargle.HOWL>

Moving this discussion out to the public list. Guys this is our
latest TODO list. We welcome people from the community to take up items
here, but please let us know if you are going to work on something.

I'll be tackling the MacBook pro swiotlb issue, I think this should be
fixed now, but not sure, needs a MacBook Pro 3.1 tester. I also already
started working on the ath9k regulatory scrub. Essentially we'll be
relying on CRDA for 11d instead of the EEPROM so this is a huge major
cleanup. Also there is a lot of potential to share this work with ath5k
code. One option which Jouni suggested was a module we can share between
ath9k/ath5k, maybe some sort of ath_common.ko or the like and first
stash in there reg stuff. Maybe later add more shared stuff as we go.

On Thu, Nov 20, 2008 at 08:22:21AM -0800, Sujith Manoharan wrote:
> Hi,
> 
> So more dirty linen to be washed, and here it is.
> 
> Issues/Bugs:
> 
> * PCI/DMA suckage ( SWIOTLB issue on macbooks )

Taken, need a MacBook pro 3.1 tester.

> * Fix xmit ( there is still a difference between xmit and recv )
>   (I don't see the difference in UDP, only in TCP)
> * TX/RX Hang
>   (I run into TX/RX hang after running Iperf for some time, no idea as to what's happening)
> * Fix convoluted aggregation logic
>   (bf_lastbf, bf_lastfrm, bf_next, bf_rifslast, buf_q, tid_q, axq_acq ...)
> * Fix Channel setting mess
>   (Racy, calculation of HT parameters is buggy)
> * RC scaling
>   (More analysis/optimization needs to be done here)
> * Fix probe/auth timeout issues
> * Fix HT handling mess
>   (reassociation with HT40 is a problem, switching between legacy/HT APs fails occasionally too)
> * Fix locking
>   (Yeah, right, like we have locking to begin with)
> * Throughput with legacy APs suck, analyze this
>   (Compare with Minstrel for legacy mode ?)
> * AR5416 based cards show lower throughput numbers than AR9280 and above. Fix this.
> * Handle PCI suspend/resume callbacks properly
> * Check ANI
>   (Does it work ?)
> * WTF is Slow Antenna Diversity and why have we not done anything to enable it so far ?
> * Lots of code for chainmask handling is present ( timers etc.), what are we doing with all that ?
> * Lockdep warning on ath_tid_drain() when association is lost and we try to clean up
> 
> Cleanup love:
> 
> * http://wireless.kernel.org/en/users/Drivers/ath9k
> 
> Major Items ( I know, we keep listing these again and again ):
> * 11d (Regulatory Scrub)

Taken.

> * 11h
> * SoftAP
> * Power Save (legacy)
> * BT Coex
> 
> Sujith
> 
> 

       reply	other threads:[~2008-11-20 19:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18725.36541.901179.14716@gargle.gargle.HOWL>
2008-11-20 19:32 ` Luis R. Rodriguez [this message]
2008-11-20 23:23   ` [ath9k-devel] Dirty Laundry List Alistair John Strachan
2008-11-20 23:28     ` Luis R. Rodriguez
2008-11-21  0:33       ` Alistair John Strachan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081120193247.GC5899@tesla \
    --to=lrodriguez@atheros.com \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.