Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	ath9k-devel@lists.ath9k.org,
	Senthil Balasubramanian <senthilkumar@atheros.com>,
	Felix Fietkau <nbd@openwrt.org>, Christoph Hellwig <hch@lst.de>,
	Jack Howarth <howarth@bromo.msbb.uc.edu>,
	Jouni Malinen <jouni.malinen@atheros.com>,
	Sujith Manoharan <Sujith.Manoharan@atheros.com>,
	Pavel Roskin <proski@gnu.org>,
	Vasanthakumar Thiagarajan <vasanth@atheros.com>
Subject: Re: [PATCH 4/4] ath9k: Add new Atheros IEEE 802.11n driver [reference to URL]
Date: Mon, 04 Aug 2008 11:34:23 +0200	[thread overview]
Message-ID: <1217842463.4721.28.camel@johannes.berg> (raw)
In-Reply-To: <1217835007-15173-1-git-send-email-lrodriguez@atheros.com> (sfid-20080804_093022_372695_B212066D)

[-- Attachment #1: Type: text/plain, Size: 1734 bytes --]

On Mon, 2008-08-04 at 00:30 -0700, Luis R. Rodriguez wrote:
> This adds the new mac80211 11n ath9k Atheros driver. Only STA support
> is currently enabled and tested.

Couple of comments:

ath_softc is _huge_, and the spinlocks in it are at the worst possible
place. Placing them together with the data they protect should be
better.


There's talk about sysctls that do not exist.


+/* Until mac80211 includes these fields */

please just post a patch doing so.


You haven't explained ath_scan_end et al. yet.


+               /* For HT capable stations, we save tidno for later use.
+                * We also override seqno set by upper layer with the
one
+                * in tx aggregation state.
+                *
+                * First, the fragmentation stat is determined.
+                * If fragmentation is on, the sequence number is
+                * not overridden, since it has been
+                * incremented by the fragmentation routine.

do you really still need to override the seqno? Did I make a mistake? Or
is this just older code? Or is it necessary because the aggregation
callback wants the seqno? In that case I can preassign it there to the
right thing...


+        * Calculate duration.  This logically belongs in the 802.11
+        * layer but it lacks sufficient information to calculate it.

what information does it lack? It _does_ in fact calculate the duration.
Something wrong there with aggregation? Please realise that you can, in
fact, change the upper layer.


+#ifdef USE_LEGACY_HAL

eh?


I'd appreciate somebody else reviewing the driver from a stack
perspective too, I don't have all that much time right now.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2008-08-04 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04  7:30 [PATCH 4/4] ath9k: Add new Atheros IEEE 802.11n driver [reference to URL] Luis R. Rodriguez
2008-08-04  9:34 ` Johannes Berg [this message]

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=1217842463.4721.28.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=Sujith.Manoharan@atheros.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=hch@lst.de \
    --cc=howarth@bromo.msbb.uc.edu \
    --cc=jouni.malinen@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=nbd@openwrt.org \
    --cc=proski@gnu.org \
    --cc=senthilkumar@atheros.com \
    --cc=vasanth@atheros.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox