linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
	linville@tuxdriver.com, bruno@thinktube.com, jirislaby@gmail.com,
	mcgrof@gmail.com, johannes@sipsolutions.net
Subject: Re: [PATCH] ath5k: Port to new bitrate/channel API
Date: Wed, 30 Jan 2008 20:28:43 +0100	[thread overview]
Message-ID: <47A0CFEB.2080702@gmail.com> (raw)
In-Reply-To: <20080130183824.GA7676@makis.domain.invalid>

On 01/30/2008 07:38 PM, Nick Kossifidis wrote:
> Tested on 5211, 5213+5112, 5213A+2112A and it wors fine.
> 
> Also i figured out a way to process rate vallue found on status descriptors,
> it's still buggy but we are getting closer (i think it improved stability a little).
> 
> Changes-licensed-under: 3-clause-BSD
> Signed-off-by: Nick Kossifidis <mickflemm@gmail.com>
> 
> ---
> @@ -898,25 +879,26 @@ ath5k_copy_channels(struct ath5k_hw *ah,
>  	}
>  
>  	for (i = 0, count = 0; i < size && max > 0; i++) {
> -		ch = all ? i + 1 : chans[i].chan;
> -		f = ath5k_ieee2mhz(ch);
> -		/* Check if channel is supported by the chipset */
> -		if (!ath5k_channel_ok(ah, f, chfreq))
> -			continue;
> +		ch = i + 1 ;
> +		freq = ath5k_ieee2mhz(ch);
[...]
> -		if (!all && (chans[i].mode & map[mode].mask) != map[mode].mode)
> -			continue;
> +		/* Write channel info and increment counter */
> +		channels[count].center_freq = freq;
> +
> +		if((mode == AR5K_MODE_11A) ||
> +		(mode == AR5K_MODE_11G)){
> +			channels[count].hw_value = chfreq|CHANNEL_OFDM;
> +		} else if((mode == AR5K_MODE_11A_TURBO) ||
> +		(mode == AR5K_MODE_11G_TURBO)){
> +			channels[count].hw_value = chfreq|CHANNEL_OFDM|CHANNEL_TURBO;
> +		}if(mode == AR5K_MODE_11B) {
> +			channels[count].hw_value = CHANNEL_B;
> +		}

Please run with this patch through Lindent (use checkpatch), some parts are not 
much readable.

Otherwise seems pretty well.

  parent reply	other threads:[~2008-01-30 19:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 18:38 [PATCH] ath5k: Port to new bitrate/channel API Nick Kossifidis
2008-01-30 18:43 ` [ath5k-devel] " Nick Kossifidis
2008-01-30 19:28 ` Jiri Slaby [this message]
2008-01-31 15:07 ` Luis R. Rodriguez
2008-01-31 15:32   ` [ath5k-devel] " Nick Kossifidis
2008-01-31 15:50     ` Luis R. Rodriguez
2008-01-31 16:16       ` Nick Kossifidis
2008-01-31 16:41         ` Jiri Slaby
2008-02-12  9:51 ` bruno randolf
2008-02-12 10:06   ` Nick Kossifidis

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=47A0CFEB.2080702@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=bruno@thinktube.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    /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).