From: Adam Baker <linux@baker-net.org.uk>
To: linux-wireless@vger.kernel.org
Cc: rt2400-devel@lists.sourceforge.net
Subject: Mode selection in mac80211
Date: Fri, 5 Oct 2007 23:19:10 +0100 [thread overview]
Message-ID: <200710052319.10600.linux@baker-net.org.uk> (raw)
I've observed an undesirable change in behaviour of rt2x00 as a result of
Johannes Berg's patch 3d4803379613c763f5a7863e8249b63d190af5e6
(remove all prism2 ioctls).
It used to consistently default to 802.11g mode on g capable hardware. Because
that patch removed the lines
- /* Use next_mode as the mode preference to
- * resolve non-unique channel numbers. */
- if (set && mode->mode != local->next_mode)
- continue;
in ieee80211_set_channel it now defaults to 11b unless I change the code that
calls ieee80211_register_hwmode. (I realise that the next_mode test is no
longer "right").
This is because ieee80211_set_channel will now prefer to select whichever was
the last mode for which the driver called ieee80211_register_hwmode whereas
the previous behaviour preferred the first registered mode. It seems as
though if there was a way to avoid calling Iieee80211_set_channel then the
setting of oper_hw_mode in ieee80211_register_hwmode would still prefer the
first registered mode.
Is it intended that the order of calling ieee80211_register_hwmode should
determine which mode should be preferred when multiple modes exist on the
same channel or is there either already or planned a better option for driver
writers? If calling order should determine preference should it be first or
last registered?
Adam Baker
next reply other threads:[~2007-10-05 22:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 22:19 Adam Baker [this message]
2007-10-08 9:55 ` Mode selection in mac80211 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
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=200710052319.10600.linux@baker-net.org.uk \
--to=linux@baker-net.org.uk \
--cc=linux-wireless@vger.kernel.org \
--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).