Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: linville@tuxdriver.com, yi.zhu@intel.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] mac80211: fix beacon interval value
Date: Thu, 12 Jun 2008 22:53:56 +0200	[thread overview]
Message-ID: <1213304036.3730.51.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240806121347x211af015w51a9ca3cabaac96c@mail.gmail.com> (sfid-20080612_224749_666575_3A188782)

[-- Attachment #1: Type: text/plain, Size: 990 bytes --]


> > I don't see how the beacon interval has any relation to "what is best
> > for the hardware/driver".
> 
> Usually this affect power management if implemented.

Hmm, yeah, but wouldn't that have to deal with all values?

>  And doing this just creates hard to debug
> > differences between drivers. All differences between different drivers
> > are causing problems at some point.
> 
> Get assimilated :)

Heh.

> > Wrt. configurability, yes, we should maybe allow this. Although it's
> > only used for IBSS (in BSS it is configurable already)
> You mean probably AP

Yes.

> What should be the proper interface  sysfs or iw(nl) ?

nl80211, I'd think, yeah, for BSS (AP) you can set it along with the
beacon.

> >so I'm not
> > entirely sure... users are probably not able to make an informed
> > decision anyway.
> 
> Are you talking about Linux users ? :). Usually vendors take such decisions.

Well I mean if it's userspace-configurable.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2008-06-12 20:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 19:38 [PATCH 1/1] mac80211: fix beacon interval value Tomas Winkler
2008-06-12 19:41 ` Johannes Berg
2008-06-12 20:05   ` Tomas Winkler
2008-06-12 20:08     ` Johannes Berg
2008-06-12 20:47       ` Tomas Winkler
2008-06-12 20:53         ` Johannes Berg [this message]

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=1213304036.3730.51.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=tomasw@gmail.com \
    --cc=yi.zhu@intel.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