From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Tomas Winkler <tomasw@gmail.com>, Michael Buesch <mb@bu3sch.de>,
Larry Finger <Larry.Finger@lwfinger.net>, Chr <chunkeey@web.de>,
Ivo van Doorn <ivdoorn@gmail.com>, Pavel Roskin <proski@gnu.org>,
Herton Ronaldo Krzesinski <herton@mandriva.com.br>,
Nick Kossifidis <mickflemm@gmail.com>,
Kalle Valo <kalle.valo@nokia.com>,
Luis Carlos Cobo <luisca@cozybit.com>,
Javier Cardona <javier@cozybit.com>,
Ron Rindjunsky <ron.rindjunsky@intel.com>
Subject: Re: mac80211 driver API
Date: Tue, 7 Oct 2008 13:21:50 -0400 [thread overview]
Message-ID: <20081007172149.GA3287@tuxdriver.com> (raw)
In-Reply-To: <1223398885.7328.47.camel@johannes.berg>
On Tue, Oct 07, 2008 at 07:01:25PM +0200, Johannes Berg wrote:
> Another thing I noticed when looking at the short slot stuff is that a
> number of drivers do not use the use_short_preamble flag but also do not
> set IEEE80211_HW_2GHZ_SHORT_PREAMBLE_INCAPABLE; this seems like a bug
> affecting at least b43legacy, ath5k, at76_usb, rtl8180, rtl8187.
>
> You should review the mac80211 driver API for things you aren't using
> but should be using, this affects a number of drivers, for example
> adm8211, p54, stlc45xx, ath5k, ath9k, libertas_tf, rtl8180, rtl8187
> don't use radio_enabled; a number of drivers don't use power_level.
>
> There are also still drivers (ath5k, adm8211, rtl8180, iwlwifi,
> libertas_tf, zd1211rw, mac80211_hwsim, ...?) not using the
> IEEE80211_TX_CTL_ASSIGN_SEQ flag, I can fix those since I broke them,
> but help from the authors would be appreciated since I don't know the hw
> in all cases, I know that stlc45xx for example can use a corresponding
> firmware flag for it.
Should we recruit janitor's (or gregkh's army) to help with stuff
like the above?
> Do we need a document that indicates which parts of the API must be
> implemented? Or should we mark such things in mac80211.h? Would
> something like this help? I've thrown this together quickly so it
> probably isn't complete yet...
<snip>
Looks like a good start, and I would definitely value such a list.
Please continue to improve it, and we'll figure-out where it needs
to live in the long run.
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-10-07 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 17:01 mac80211 driver API Johannes Berg
2008-10-07 17:21 ` John W. Linville [this message]
2008-10-07 17:39 ` 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=20081007172149.GA3287@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chunkeey@web.de \
--cc=herton@mandriva.com.br \
--cc=ivdoorn@gmail.com \
--cc=javier@cozybit.com \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@nokia.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luisca@cozybit.com \
--cc=mb@bu3sch.de \
--cc=mickflemm@gmail.com \
--cc=proski@gnu.org \
--cc=ron.rindjunsky@intel.com \
--cc=tomasw@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).