[PATCH 0/8] ath9k_htc patches

[PATCH 0/8] ath9k_htc patches

[Sujith]

Hi,

This series fixes a few issues with BSSID handling and removes
unused stuff in both the firmware and the host driver.

The required firmware version is now 1.3 and the new firmware will
be uploaded to http://wireless.kernel.org/download/htc_fw/ once Luis
comes out of his slumber.

For the record, the FW Changelog for v1.3 is:

* Remove unused PHY modes (TURBO etc.)
* Remove unused MIMO PS code.
* Cleanup node flags.
* Remove FastFrame code.
* Fix various bugs in management frame transmission.
* Fix duration calculation.
* Fix packet type calculation.
* Enable CAB queue for UB94/95.
* Fix sequence number assignment.
* Remove vendor-specific hacks.
* Add TX completion for multicast packets.
* Various code cleanups.
* Reduce credit size for UB94/95 to 45.

Sujith

Sujith Manoharan (8):
  ath9k_htc: Fix mode selection
  ath9k_htc: Fix station flags
  ath9k_htc: Recalculate the BSSID mask on interface removal
  ath9k_htc: Fix RX filter calculation
  ath9k_htc: Fix BSSID calculation
  ath9k_htc: Fix max subframe handling
  ath9k_htc: Change credit limit for UB94/95
  ath9k_htc: Fix packet timeout

 drivers/net/wireless/ath/ath9k/hif_usb.h      |    2 +-
 drivers/net/wireless/ath/ath9k/htc.h          |   23 ++------
 drivers/net/wireless/ath/ath9k/htc_drv_init.c |    7 +--
 drivers/net/wireless/ath/ath9k/htc_drv_main.c |   77 ++++++++++++++++---------
 drivers/net/wireless/ath/ath9k/htc_drv_txrx.c |    4 +
 5 files changed, 61 insertions(+), 52 deletions(-)

-- 
1.7.5.1

[ath9k-devel] [PATCH 0/8] ath9k_htc patches

[Sujith]

Hi,

This series fixes a few issues with BSSID handling and removes
unused stuff in both the firmware and the host driver.

The required firmware version is now 1.3 and the new firmware will
be uploaded to http://wireless.kernel.org/download/htc_fw/ once Luis
comes out of his slumber.

For the record, the FW Changelog for v1.3 is:

* Remove unused PHY modes (TURBO etc.)
* Remove unused MIMO PS code.
* Cleanup node flags.
* Remove FastFrame code.
* Fix various bugs in management frame transmission.
* Fix duration calculation.
* Fix packet type calculation.
* Enable CAB queue for UB94/95.
* Fix sequence number assignment.
* Remove vendor-specific hacks.
* Add TX completion for multicast packets.
* Various code cleanups.
* Reduce credit size for UB94/95 to 45.

Sujith

Sujith Manoharan (8):
  ath9k_htc: Fix mode selection
  ath9k_htc: Fix station flags
  ath9k_htc: Recalculate the BSSID mask on interface removal
  ath9k_htc: Fix RX filter calculation
  ath9k_htc: Fix BSSID calculation
  ath9k_htc: Fix max subframe handling
  ath9k_htc: Change credit limit for UB94/95
  ath9k_htc: Fix packet timeout

 drivers/net/wireless/ath/ath9k/hif_usb.h      |    2 +-
 drivers/net/wireless/ath/ath9k/htc.h          |   23 ++------
 drivers/net/wireless/ath/ath9k/htc_drv_init.c |    7 +--
 drivers/net/wireless/ath/ath9k/htc_drv_main.c |   77 ++++++++++++++++---------
 drivers/net/wireless/ath/ath9k/htc_drv_txrx.c |    4 +
 5 files changed, 61 insertions(+), 52 deletions(-)

-- 
1.7.5.1

Re: [PATCH 0/8] ath9k_htc patches

[Luis R. Rodriguez]

On Tue, May 17, 2011 at 12:10 AM, Sujith <m.sujith@gmail.com> wrote:
> The required firmware version is now 1.3 and the new firmware will
> be uploaded to http://wireless.kernel.org/download/htc_fw/ once Luis
> comes out of his slumber.

*Yawn*

OK its up.

 Luis

[ath9k-devel] [PATCH 0/8] ath9k_htc patches

[Luis R. Rodriguez]

On Tue, May 17, 2011 at 12:10 AM, Sujith <m.sujith@gmail.com> wrote:
> The required firmware version is now 1.3 and the new firmware will
> be uploaded to http://wireless.kernel.org/download/htc_fw/ once Luis
> comes out of his slumber.

*Yawn*

OK its up.

 Luis

Re: [PATCH 0/8] ath9k_htc patches

[Sujith]

Luis R. Rodriguez wrote:
> On Tue, May 17, 2011 at 12:10 AM, Sujith <m.sujith@gmail.com> wrote:
> > The required firmware version is now 1.3 and the new firmware will
> > be uploaded to http://wireless.kernel.org/download/htc_fw/ once Luis
> > comes out of his slumber.
> 
> *Yawn*
> 
> OK its up.

That was fast, thanks. :)

Sujith

[ath9k-devel] [PATCH 0/8] ath9k_htc patches

[Sujith]

Luis R. Rodriguez wrote:
> On Tue, May 17, 2011 at 12:10 AM, Sujith <m.sujith@gmail.com> wrote:
> > The required firmware version is now 1.3 and the new firmware will
> > be uploaded to http://wireless.kernel.org/download/htc_fw/ once Luis
> > comes out of his slumber.
> 
> *Yawn*
> 
> OK its up.

That was fast, thanks. :)

Sujith

[ath9k-devel] [PATCH 0/8] ath9k_htc patches

[Keith Berkoben]

Hi all,

I'm an Openwrt who has been monitoring this list for a while and I
frequently see patches like this below come through (My particular interest
is in HT for adhoc), but I have no idea how to tell when and if these
patches get integrated into the main driver source (compat-wireless
<date>).  For openwrt, I'm used to looking at the revision logs of
components I care about in the svn browser, but I can't find a similar tool
for the compat-wireless builds.  Could someone enlighten me as to how these
patches make their way into the main builds and where I could go to check
(preferably in a user-friendly way) if the thing I want is integrated into a
particular build?

~Keith


On Tue, May 17, 2011 at 3:10 AM, Sujith <m.sujith@gmail.com> wrote:

> Hi,
>
> This series fixes a few issues with BSSID handling and removes
> unused stuff in both the firmware and the host driver.
>
> The required firmware version is now 1.3 and the new firmware will
> be uploaded to http://wireless.kernel.org/download/htc_fw/ once Luis
> comes out of his slumber.
>
> For the record, the FW Changelog for v1.3 is:
>
> * Remove unused PHY modes (TURBO etc.)
> * Remove unused MIMO PS code.
> * Cleanup node flags.
> * Remove FastFrame code.
> * Fix various bugs in management frame transmission.
> * Fix duration calculation.
> * Fix packet type calculation.
> * Enable CAB queue for UB94/95.
> * Fix sequence number assignment.
> * Remove vendor-specific hacks.
> * Add TX completion for multicast packets.
> * Various code cleanups.
> * Reduce credit size for UB94/95 to 45.
>
> Sujith
>
> Sujith Manoharan (8):
>  ath9k_htc: Fix mode selection
>  ath9k_htc: Fix station flags
>  ath9k_htc: Recalculate the BSSID mask on interface removal
>  ath9k_htc: Fix RX filter calculation
>  ath9k_htc: Fix BSSID calculation
>  ath9k_htc: Fix max subframe handling
>  ath9k_htc: Change credit limit for UB94/95
>  ath9k_htc: Fix packet timeout
>
>  drivers/net/wireless/ath/ath9k/hif_usb.h      |    2 +-
>  drivers/net/wireless/ath/ath9k/htc.h          |   23 ++------
>  drivers/net/wireless/ath/ath9k/htc_drv_init.c |    7 +--
>  drivers/net/wireless/ath/ath9k/htc_drv_main.c |   77
> ++++++++++++++++---------
>  drivers/net/wireless/ath/ath9k/htc_drv_txrx.c |    4 +
>  5 files changed, 61 insertions(+), 52 deletions(-)
>
> --
> 1.7.5.1
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110517/325242bc/attachment-0001.htm 

Re: [ath9k-devel] [PATCH 0/8] ath9k_htc patches

[Sujith]

Keith Berkoben wrote:
> Hi all,
> 
> I'm an Openwrt who has been monitoring this list for a while and I frequently see patches like this below come through (My particular interest is in HT for adhoc),
> but I have no idea how to tell when and if these patches get integrated into the main driver source (compat-wireless <date>).  For openwrt, I'm used to looking at the
> revision logs of components I care about in the svn browser, but I can't find a similar tool for the compat-wireless builds.  Could someone enlighten me as to how
> these patches make their way into the main builds and where I could go to check (preferably in a user-friendly way) if the thing I want is integrated into a
> particular build?
> 

http://wireless.kernel.org/en/developers/process

It has colorful diagrams and everything. :)

Sujith

[ath9k-devel] [PATCH 0/8] ath9k_htc patches

[Sujith]

Keith Berkoben wrote:
> Hi all,
> 
> I'm an Openwrt who has been monitoring this list for a while and I frequently see patches like this below come through (My particular interest is in HT for adhoc),
> but I have no idea how to tell when and if these patches get integrated into the main driver source (compat-wireless <date>).? For openwrt, I'm used to looking at the
> revision logs of components I care about in the svn browser, but I can't find a similar tool for the compat-wireless builds.? Could someone enlighten me as to how
> these patches make their way into the main builds and where I could go to check (preferably in a user-friendly way) if the thing I want is integrated into a
> particular build?
> 

http://wireless.kernel.org/en/developers/process

It has colorful diagrams and everything. :)

Sujith

[ath9k-devel] [PATCH 0/8] ath9k_htc patches

[Keith Berkoben]

Thanks!

When following this process (it has a couple steps...), is it generally a
true statement that changes from
wireless-testing->wireless-next-->net-next-->etc. are usually pushed by
"Merges", or should I also be watching for changes filtering through in
other ways?

Stated another way, is the heuristic of:
1. look for patch in wireless-testing
2. look for subsequent Merge of that branch (or parent) in wireless-next
3. look for subsequent Merge of wireless-next branch in net-next
4. repeat all the way to the build I want
and effective way to ensure what I want is in a build without reading all of
the individual source files in each archive?

~Keith


On Tue, May 17, 2011 at 11:37 AM, Sujith <m.sujith@gmail.com> wrote:

> Keith Berkoben wrote:
> > Hi all,
> >
> > I'm an Openwrt who has been monitoring this list for a while and I
> frequently see patches like this below come through (My particular interest
> is in HT for adhoc),
> > but I have no idea how to tell when and if these patches get integrated
> into the main driver source (compat-wireless <date>).  For openwrt, I'm used
> to looking at the
> > revision logs of components I care about in the svn browser, but I can't
> find a similar tool for the compat-wireless builds.  Could someone enlighten
> me as to how
> > these patches make their way into the main builds and where I could go to
> check (preferably in a user-friendly way) if the thing I want is integrated
> into a
> > particular build?
> >
>
> http://wireless.kernel.org/en/developers/process
>
> It has colorful diagrams and everything. :)
>
> Sujith
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110517/c3daed5b/attachment.htm 

Re: [ath9k-devel] [PATCH 0/8] ath9k_htc patches

[Luis R. Rodriguez]

On Tue, May 17, 2011 at 8:58 AM, Keith Berkoben <berkoben@gmail.com> wrote:
> Thanks!
>
> When following this process (it has a couple steps...), is it generally a
> true statement that changes from
> wireless-testing->wireless-next-->net-next-->etc. are usually pushed by
> "Merges", or should I also be watching for changes filtering through in
> other ways?
>
> Stated another way, is the heuristic of:
> 1. look for patch in wireless-testing
> 2. look for subsequent Merge of that branch (or parent) in wireless-next
> 3. look for subsequent Merge of wireless-next branch in net-next
> 4. repeat all the way to the build I want
> and effective way to ensure what I want is in a build without reading all of
> the individual source files in each archive?

Patches go first into wireless-next, then stable stuff goes into
wirless-2.6 (current RC), and then both of these get pulled into
wireless-testing, which provides the RC fixes + the next bits, on a
stable kernel (RC).

Compat-wireless daily snapshots use linux-next so changes take a bit
to propagate there.

OpenWrt uses wireless-testing as the base tree, you can tell by
loading the compat module, it will tell you the base tree and git tree
tags that was used as source.

  Luis

[ath9k-devel] [PATCH 0/8] ath9k_htc patches

[Luis R. Rodriguez]

On Tue, May 17, 2011 at 8:58 AM, Keith Berkoben <berkoben@gmail.com> wrote:
> Thanks!
>
> When following this process (it has a couple steps...), is it generally a
> true statement that changes from
> wireless-testing->wireless-next-->net-next-->etc. are usually pushed by
> "Merges", or should I also be watching for changes filtering through in
> other ways?
>
> Stated another way, is the heuristic of:
> 1. look for patch in wireless-testing
> 2. look for subsequent Merge of that branch (or parent) in wireless-next
> 3. look for subsequent Merge of wireless-next branch in net-next
> 4. repeat all the way to the build I want
> and effective way to ensure what I want is in a build without reading all of
> the individual source files in each archive?

Patches go first into wireless-next, then stable stuff goes into
wirless-2.6 (current RC), and then both of these get pulled into
wireless-testing, which provides the RC fixes + the next bits, on a
stable kernel (RC).

Compat-wireless daily snapshots use linux-next so changes take a bit
to propagate there.

OpenWrt uses wireless-testing as the base tree, you can tell by
loading the compat module, it will tell you the base tree and git tree
tags that was used as source.

  Luis

Re: [ath9k-devel] [PATCH 0/8] ath9k_htc patches

[Adrian Chadd]

On 18 May 2011 04:46, Luis R. Rodriguez <mcgrof@gmail.com> wrote:

> Patches go first into wireless-next, then stable stuff goes into
> wirless-2.6 (current RC), and then both of these get pulled into
> wireless-testing, which provides the RC fixes + the next bits, on a
> stable kernel (RC).
>
> Compat-wireless daily snapshots use linux-next so changes take a bit
> to propagate there.
>
> OpenWrt uses wireless-testing as the base tree, you can tell by
> loading the compat module, it will tell you the base tree and git tree
> tags that was used as source.

And some (eg Felix) will merge in immediate bugfixes into openwrt that
hasn't yet made it into a baked compat-wireless release.


Adrian

[ath9k-devel] [PATCH 0/8] ath9k_htc patches

[Adrian Chadd]

On 18 May 2011 04:46, Luis R. Rodriguez <mcgrof@gmail.com> wrote:

> Patches go first into wireless-next, then stable stuff goes into
> wirless-2.6 (current RC), and then both of these get pulled into
> wireless-testing, which provides the RC fixes + the next bits, on a
> stable kernel (RC).
>
> Compat-wireless daily snapshots use linux-next so changes take a bit
> to propagate there.
>
> OpenWrt uses wireless-testing as the base tree, you can tell by
> loading the compat module, it will tell you the base tree and git tree
> tags that was used as source.

And some (eg Felix) will merge in immediate bugfixes into openwrt that
hasn't yet made it into a baked compat-wireless release.


Adrian