All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: gregor kowski <gregor.kowski@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43 add harware tkip
Date: Mon, 8 Jun 2009 17:20:59 +0200	[thread overview]
Message-ID: <200906081720.59594.mb@bu3sch.de> (raw)
In-Reply-To: <83a869cd0906071450h24ed4119s44d00db0d97d59e2@mail.gmail.com>

Well, first thing is that I do think there is a reason Broadcom removed hw TKIP
support from their drivers. ;)

But well, let's look at the patch.

> +	/* FIXME this is the wrong offset : it goes in tkip rx phase1 shm */
> +#if 0
>  	b43_write_probe_resp_plcp(dev, 0x31A, size, &b43_b_ratetable[0]);
>  	b43_write_probe_resp_plcp(dev, 0x32C, size, &b43_b_ratetable[1]);
>  	b43_write_probe_resp_plcp(dev, 0x33E, size, &b43_b_ratetable[2]);
>  	b43_write_probe_resp_plcp(dev, 0x350, size, &b43_b_ratetable[3]);
> +#endif

This looks interesting. Care to find out the correct offsets and submit
this fix as a separate patch?

> +	if (algorithm == B43_SEC_ALGO_TKIP) {
> +		/*
> +		 * We should provide an initial iv32, phase1key pair.
> +		 * We could start with iv32=0 and compute the corresponding
> +		 * phase1key, but this mean calling ieee80211_get_tkip_key
> +		 * with a fake skb (or export other tkip function).
> +		 * Because we are lazy we hope iv32 won't start with
> +		 * 0xffff and let's b43_mac_update_tkip_key provide a
> +		 * correct pair.
> +		 */
> +		rx_tkip_phase1_write(dev, index, 0xffff, (u16*)buf);
> +	} else /* clear it */
> +		rx_tkip_phase1_write(dev, index, 0, (u16*)buf);

Why do you write phase1, if TKIP is not used?

> +	/* FIXME : for b43_new_kidx_api, there can be 54 key
> +	 * instead of 50 in RCMTA and TKIPTSCTTAK.
> +	 */

I don't understand this comment.

> -		if (algorithm == B43_SEC_ALGO_TKIP) {
> -			/* FIXME: No TKIP hardware encryption for now. */
> +		if (algorithm == B43_SEC_ALGO_TKIP &&
> +				(!(key->flags & IEEE80211_KEY_FLAG_PAIRWISE) ||
> +				   key->flags & IEEE80211_KEY_FLAG_WMM_STA )) {
> +			/* We support only one rx queue (no QOS) and pairwise key */

This comment doesn't really make sense to me, too.
What does QoS have to do with the RX queue?


Next time please inline the patch ;)

-- 
Greetings, Michael.

  parent reply	other threads:[~2009-06-08 15:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-07 21:50 [PATCH] b43 add harware tkip gregor kowski
2009-06-07 22:34 ` Gábor Stefanik
2009-06-08  6:24   ` Johannes Berg
2009-06-08 18:31     ` Gábor Stefanik
2009-06-08 15:20 ` Michael Buesch [this message]
2009-06-08 18:04   ` gregor kowski
2009-06-08 18:16     ` Michael Buesch
2009-06-09 18:01       ` gregor kowski
2009-06-22 20:58         ` gregor kowski

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=200906081720.59594.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=gregor.kowski@gmail.com \
    --cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.