[leaf-commits] src/bering-uclibc4/source/hostapd hostapd_fix_couldnt_set_DTIM.patch, NONE, 1.1 buildtool.cfg, 1.3, 1.4 buildtool.mk, 1.3, 1.4

Andrew <[email protected]>
Newsgroups gmane.linux.leaf.cvs
Message-ID <[email protected]>
Update of /cvsroot/leaf/src/bering-uclibc4/source/hostapd
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv16005

Modified Files:
	buildtool.cfg buildtool.mk 
Added Files:
	hostapd_fix_couldnt_set_DTIM.patch 
Log Message:
Fixed DTIM period setting for 0.6.10


Index: buildtool.cfg
===================================================================
RCS file: /cvsroot/leaf/src/bering-uclibc4/source/hostapd/buildtool.cfg,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** buildtool.cfg	6 Aug 2010 06:55:54 -0000	1.3
--- buildtool.cfg	6 Aug 2010 09:15:19 -0000	1.4
***************
*** 26,29 ****
--- 26,36 ----
  </File>
  
+ <File hostapd_fix_couldnt_set_DTIM.patch>
+ 	Server = cvs4-sourceforge
+ 	Directory = hostapd
+ 	revision = HEAD
+ 	EnvName = HOSTAPD_PATCH3
+ </File>
+ 
  <File .config>
  	Server = cvs4-sourceforge
***************
*** 46,51 ****
  <Package>
  	<hostapd>
! 		Version = 0.5.11
! 		Revision = 1
  		
  		Help <<EOF
--- 53,58 ----
  <Package>
  	<hostapd>
! 		Version = 0.6.10
! 		Revision = 2
  		
  		Help <<EOF

Index: buildtool.mk
===================================================================
RCS file: /cvsroot/leaf/src/bering-uclibc4/source/hostapd/buildtool.mk,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** buildtool.mk	6 Aug 2010 06:55:54 -0000	1.3
--- buildtool.mk	6 Aug 2010 09:15:19 -0000	1.4
***************
*** 16,19 ****
--- 16,20 ----
  	cat $(HOSTAPD_PATCH1) | patch -d $(HOSTAPD_DIR) -p1
  	cat $(HOSTAPD_PATCH2) | patch -d $(HOSTAPD_DIR) -p1
+ 	cat $(HOSTAPD_PATCH3) | patch -d $(HOSTAPD_DIR) -p2
  	touch $(HOSTAPD_DIR)/.source
  

--- NEW FILE: hostapd_fix_couldnt_set_DTIM.patch ---
From: Jouni Malinen <[email protected]>
Date: Thu, 12 Mar 2009 19:57:08 +0000 (+0200)
Subject: Move DTIM period configuration into Beacon set operation
X-Git-Tag: hostap_0_7_0~455
X-Git-Url: http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap-07.git;a=commitdiff_plain;h=eb1f7446b5b86cceb1508f060f5e66e5dd791a4d

Move DTIM period configuration into Beacon set operation

This is needed to make mac80211 work with multi-BSS configuration. The
previous design ended up setting DTIM period for secondary BSSes before
setting the Beacon and driver_nl80211.c was not really prepared for
that. Eventually, the Beacon configuration routines should be combined
into a single driver operation, but for now, just moving this call is
the simplest workaround.
---

diff --git a/hostapd/beacon.c b/hostapd/beacon.c
index b7eb86a..8ccfa12 100644
--- a/hostapd/beacon.c
+++ b/hostapd/beacon.c
@@ -434,6 +434,10 @@ void ieee802_11_set_beacon(struct hostapd_data *hapd)
 	os_free(tail);
 	os_free(head);
 
+	if (hostapd_set_dtim_period(hapd, hapd->conf->dtim_period))
+		wpa_printf(MSG_ERROR, "Could not set DTIM period for kernel "
+			   "driver");
+
 	if (hostapd_set_cts_protect(hapd, cts_protection))
 		wpa_printf(MSG_ERROR, "Failed to set CTS protect in kernel "
 			   "driver");
diff --git a/hostapd/hostapd.c b/hostapd/hostapd.c
index 308d816..8531d0a 100644
--- a/hostapd/hostapd.c
+++ b/hostapd/hostapd.c
@@ -1292,12 +1292,6 @@ static int hostapd_setup_bss(struct hostapd_data *hapd, int first)
 		return -1;
 	}
 
-	if (hostapd_set_dtim_period(hapd, hapd->conf->dtim_period)) {
-		wpa_printf(MSG_ERROR, "Could not set DTIM period for kernel "
-			   "driver");
-		return -1;
-	}
-
 	/* Set SSID for the kernel driver (to be used in beacon and probe
 	 * response frames) */
 	if (set_ssid && hostapd_set_ssid(hapd, (u8 *) conf->ssid.ssid,


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.