public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. e71475c13afeef652ae94a545978e354e21eb03e
Date: Sun, 07 Dec 2014 11:05:17 +0100	[thread overview]
Message-ID: <20141207100517.2402B21214@argus.ipfire.org> (raw)

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

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, master has been updated
       via  e71475c13afeef652ae94a545978e354e21eb03e (commit)
      from  32787fb0dff053a4a31f9785ddb3f40e1d6a6063 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit e71475c13afeef652ae94a545978e354e21eb03e
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sun Dec 7 11:04:46 2014 +0100

    kernel: rt5572 patches part2.

-----------------------------------------------------------------------

Summary of changes:
 src/patches/linux-3.14.25-rt5592_no_special_txop_init.patch | 13 +++++++++++++
 src/patches/linux-3.14.25_rt2x00_fix_bss_bcn_num.patch      | 12 ++++++++++++
 2 files changed, 25 insertions(+)
 create mode 100644 src/patches/linux-3.14.25-rt5592_no_special_txop_init.patch
 create mode 100644 src/patches/linux-3.14.25_rt2x00_fix_bss_bcn_num.patch

Difference in files:
diff --git a/src/patches/linux-3.14.25-rt5592_no_special_txop_init.patch b/src/patches/linux-3.14.25-rt5592_no_special_txop_init.patch
new file mode 100644
index 0000000..fe30c9e
--- /dev/null
+++ b/src/patches/linux-3.14.25-rt5592_no_special_txop_init.patch
@@ -0,0 +1,13 @@
+diff -Naur linux-3.14.25.org/drivers/net/wireless/rt2x00/rt2800lib.c linux-3.14.25/drivers/net/wireless/rt2x00/rt2800lib.c
+--- linux-3.14.25.org/drivers/net/wireless/rt2x00/rt2800lib.c	2014-11-21 18:23:44.000000000 +0100
++++ linux-3.14.25/drivers/net/wireless/rt2x00/rt2800lib.c	2014-12-03 11:30:58.813355413 +0100
+@@ -4847,7 +4847,8 @@
+ 	rt2x00_set_field32(&reg, TXOP_CTRL_CFG_EXT_CWMIN, 0);
+ 	rt2800_register_write(rt2x00dev, TXOP_CTRL_CFG, reg);
+ 
+-	reg = rt2x00_rt(rt2x00dev, RT5592) ? 0x00000082 : 0x00000002;
++//	reg = rt2x00_rt(rt2x00dev, RT5592) ? 0x00000082 : 0x00000002;
++	reg = 0x00000002;
+ 	rt2800_register_write(rt2x00dev, TXOP_HLDR_ET, reg);
+ 
+ 	rt2800_register_read(rt2x00dev, TX_RTS_CFG, &reg);
diff --git a/src/patches/linux-3.14.25_rt2x00_fix_bss_bcn_num.patch b/src/patches/linux-3.14.25_rt2x00_fix_bss_bcn_num.patch
new file mode 100644
index 0000000..87ea39a
--- /dev/null
+++ b/src/patches/linux-3.14.25_rt2x00_fix_bss_bcn_num.patch
@@ -0,0 +1,12 @@
+diff -Naur linux-3.14.25.org/drivers/net/wireless/rt2x00/rt2800lib.c linux-3.14.25/drivers/net/wireless/rt2x00/rt2800lib.c
+--- linux-3.14.25.org/drivers/net/wireless/rt2x00/rt2800lib.c	2014-12-03 11:30:58.000000000 +0100
++++ linux-3.14.25/drivers/net/wireless/rt2x00/rt2800lib.c	2014-12-03 12:15:45.743454351 +0100
+@@ -1557,7 +1557,7 @@
+ 		if (!is_zero_ether_addr((const u8 *)conf->bssid)) {
+ 			reg = le32_to_cpu(conf->bssid[1]);
+ 			rt2x00_set_field32(&reg, MAC_BSSID_DW1_BSS_ID_MASK, 3);
+-			rt2x00_set_field32(&reg, MAC_BSSID_DW1_BSS_BCN_NUM, 7);
++			rt2x00_set_field32(&reg, MAC_BSSID_DW1_BSS_BCN_NUM, 0);
+ 			conf->bssid[1] = cpu_to_le32(reg);
+ 		}
+ 


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2014-12-07 10:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20141207100517.2402B21214@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox