linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: rt2400-devel@lists.sourceforge.net,
	Adam Baker <linux@baker-net.org.uk>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [Rt2400-devel] Mode selection in mac80211
Date: Tue, 9 Oct 2007 16:27:44 +0200	[thread overview]
Message-ID: <200710091627.44276.IvDoorn@gmail.com> (raw)
In-Reply-To: <1191921642.4013.13.camel@johannes.berg>

On Tuesday 09 October 2007, Johannes Berg wrote:
> On Mon, 2007-10-08 at 23:08 +0200, Ivo van Doorn wrote:
> 
> > The only difference currently in rt2x00 is for rt2500usb. The initialization
> > of the IFS and EIFS register is different.
> 
> Ok so that's something we have to do in G-mode-compatible-with-B as
> well.

Well it might not even be needed at all.
The IFS is also passed on as argument by mac80211 when it configures the
TX rings. The EIFS register is something different, all other Ralink devices
have only 1 value for the EIFS. I am not even sure how the device will react
when the same value is set for rt2500usb.

> > And is mac80211 doing that correctly at this time?
> 
> I'm not entirely sure. Are you setting the IFS/EIFS from any other
> place? :) I don't think it is doing that correctly.

Well in the drivers the following is done:
rt2500pci:
	- config_duration() sets EIFS in the register
	- write_tx_desc() sets IFS in the package descriptor
rt2500usb:
	- config_phymode() sets EIFS and IFS in the registers.
	- write_tx_desc() sets IFS in the package descriptor

Note that both config_duration() and config_phymode() are called by rt2x00lib
when mac80211 uses the config() callback function.

Note that the fact that the IFS is set twice for rt2500usb might suggest the
documentation for the register is incorrect and perhaps the purpose of the
register is completely different.

I guess it requires some experimentation to see if initializing those
2 registers differently has any effect. (And if it doesn't, then rt2500usb doesn't
require to know whether it is operating in B or G mode at all).

Ivo

  reply	other threads:[~2007-10-09 14:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 22:19 Mode selection in mac80211 Adam Baker
2007-10-08  9:55 ` Johannes Berg
2007-10-08 10:23   ` [PATCH] mac80211: fix set_channel regression Johannes Berg
2007-10-08 14:32   ` Mode selection in mac80211 Mike Kershaw
2007-10-09  9:21     ` Johannes Berg
2007-10-09 13:55       ` Mike Kershaw
2007-10-09 17:06         ` Johannes Berg
2007-10-08 21:08   ` [Rt2400-devel] " Ivo van Doorn
2007-10-09  9:20     ` Johannes Berg
2007-10-09 14:27       ` Ivo van Doorn [this message]
2007-10-09 17:05         ` Johannes Berg
2007-10-09 17:32           ` Ivo van Doorn
2007-10-09 17:29             ` Johannes Berg
2007-10-09 17:54               ` Ivo van Doorn
2007-10-09 17:40                 ` Johannes Berg
2007-10-09 18:18                   ` Ivo van Doorn
2007-10-09 18:05                     ` 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=200710091627.44276.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@baker-net.org.uk \
    --cc=mcgrof@gmail.com \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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).