netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Daniel Drake <dsd@gentoo.org>, netdev@vger.kernel.org
Subject: Re: [PATCH] bcm43xx: enable shared key authentication
Date: Mon, 26 Jun 2006 21:06:40 +0200	[thread overview]
Message-ID: <200606262106.40278.mb@bu3sch.de> (raw)
In-Reply-To: <20060626183821.GB30706@tuxdriver.com>

On Monday 26 June 2006 20:38, John W. Linville wrote:
> On Fri, Jun 16, 2006 at 08:50:22PM +0100, Daniel Drake wrote:
> > I recently patched softmac to enable shared key authentication. This small patch
> > will enable crazy or unfortunate bcm43xx users to use this new capability.
> > 
> > Signed-off-by: Daniel Drake <dsd@gentoo.org>
> > 
> > Index: linux/drivers/net/wireless/bcm43xx/bcm43xx_main.c
> > ===================================================================
> > --- linux.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c
> > +++ linux/drivers/net/wireless/bcm43xx/bcm43xx_main.c
> > @@ -3599,6 +3599,10 @@ static void bcm43xx_ieee80211_set_securi
> >  		secinfo->encrypt = sec->encrypt;
> >  		dprintk(KERN_INFO PFX "   .encrypt = %d\n", sec->encrypt);
> >  	}
> > +	if (sec->flags & SEC_AUTH_MODE) {
> > +		secinfo->auth_mode = sec->auth_mode;
> > +		dprintk(KERN_INFO PFX "   .auth_mode = %d\n", sec->auth_mode);
> > +	}
> >  	if (bcm->initialized && !bcm->ieee->host_encrypt) {
> >  		if (secinfo->enabled) {
> >  			/* upload WEP keys to hardware */
> 
> I had problems applying this one.  I recall having a similar problem w/
> a patch in the last round of merging as well.
> 
> The version of bcm43xx_main.c in wireless-2.6 looks like this
> (post patch):
> 
> 
> 		secinfo->encrypt = sec->encrypt;
> 		dprintk(", .encrypt = %d", sec->encrypt);
> 	}
> 	if (sec->flags & SEC_AUTH_MODE) {
> 		secinfo->auth_mode = sec->auth_mode;
> 		dprintk(", .auth_mode = %d\n", sec->auth_mode);
> 	}
> 	dprintk("\n");
> 	if (bcm43xx_status(bcm) == BCM43xx_STAT_INITIALIZED &&
> 	    !bcm->ieee->host_encrypt) {
> 
> Am I missing a patch?
> 
> Please make sure I get any patches that are missing from wireless-2.6
> -- it is obviously better if we are all on the same page! :-)

Daniel's patch is diffed to an older tree.
wireless-2.6 recently removed bcm->initialized and friends
and added a more usable and more correct bcm43xx_status() flag.

So, basically the following just has to be added after
the other if(sec->flags & FOO), but before the if(bcm43xx_status...)

if (sec->flags & SEC_AUTH_MODE) {
	secinfo->auth_mode = sec->auth_mode;
	dprintk(KERN_INFO PFX "   .auth_mode = %d\n", sec->auth_mode);
}

-- 
Greetings Michael.

  reply	other threads:[~2006-06-26 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 19:50 [PATCH] bcm43xx: enable shared key authentication Daniel Drake
2006-06-16 20:18 ` Michael Buesch
2006-06-18  3:01 ` Dan Williams
2006-06-18  9:31   ` Michael Buesch
2006-06-26 18:38 ` John W. Linville
2006-06-26 19:06   ` Michael Buesch [this message]
2006-06-26 19:10     ` Michael Buesch

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=200606262106.40278.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=dsd@gentoo.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).