linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	Stefano Brivio <stefano.brivio@polimi.it>
Subject: Re: [PATCH RFT/RFC] b43: Add QOS support
Date: Tue, 12 Feb 2008 22:12:03 +0100	[thread overview]
Message-ID: <200802122212.03325.mb@bu3sch.de> (raw)
In-Reply-To: <200802122205.42799.mb@bu3sch.de>

On Tuesday 12 February 2008 22:05:42 Michael Buesch wrote:
> This patch adds QOS support for b43.
> Please comment on this and test this.
> This patch depends on Johannes' "burst time -> txop patch" being _not_ applied.
> One can trivially fix that, though.
> +	for (i = 0; i < ARRAY_SIZE(wl->qos_params); i++) {
> +		params = &(wl->qos_params[i]);
> +		if (params->need_hw_update) {
> +			b43_qos_params_upload(dev, &(params->p),
> +					      qos_shm_offsets[i]);
> +			params->need_hw_update = 1;

Whoopsy, needs to be:
			params->need_hw_update = 0;

> +		}
> +	}
> +
> +	spin_unlock_irqrestore(&wl->irq_lock, flags);
> +	b43_mac_enable(dev);
> +}

> +/* Initialize the core's QOS capabilities */
> +static void b43_qos_init(struct b43_wldev *dev)
> +{
> +	/* Upload the current QOS parameters. */

And here we need a loop setting all "need_hw_update" to 1.

> +	b43_qos_update(dev);
> +	/* Enable QOS support. */
> +	b43_hf_write(dev, b43_hf_read(dev) | B43_HF_EDCF);
> +	b43_write16(dev, B43_MMIO_IFSCTL,
> +		    b43_read16(dev, B43_MMIO_IFSCTL)
> +		    | B43_MMIO_IFSCTL_USE_EDCF);
> +}

-- 
Greetings Michael.

  reply	other threads:[~2008-02-12 21:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 21:05 [PATCH RFT/RFC] b43: Add QOS support Michael Buesch
2008-02-12 21:12 ` Michael Buesch [this message]
2008-02-12 22:56 ` Michael Buesch
2008-02-13 12:08   ` Johannes Berg
2008-02-13 13:30   ` Johannes Berg
2008-02-13 12:07 ` Johannes Berg
2008-02-13 12:14   ` Michael Buesch
2008-02-13 12:19     ` Johannes Berg

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=200802122212.03325.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stefano.brivio@polimi.it \
    /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).