From: Johannes Berg <johannes@sipsolutions.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Antonio Marques <froz@icix.org>,
Andrey Yurovsky <andrey@cozybit.com>,
linux-wireless@vger.kernel.org
Subject: Re: rt2x00 mesh support
Date: Wed, 18 Mar 2009 00:04:22 +0100 [thread overview]
Message-ID: <1237331062.5100.9.camel@johannes.local> (raw)
In-Reply-To: <200903180001.07723.IvDoorn@gmail.com> (sfid-20090318_000140_630826_AF91C22B)
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On Wed, 2009-03-18 at 00:01 +0100, Ivo van Doorn wrote:
> > > This command means that mac80211 uses the start() callback function. This triggers rt2x00 to initialize
> > > the registers which resets the beacon generation.
> >
> > Strange, that doesn't seem right. If you look at net/mac80211/iface.c,
> > you'll see it call ->start(), then ->add_interface(), and later
> > ieee80211_start_mesh(), which calls _if_config() and sets
> > beacon/beacon_enabled.
>
> ok, I gone through the rt2x00 code a couple of times now to see how this bug can be triggered by rt2x00,
> But the only other scenario I could find, is when the open() callback for the netdevice structure doesn't end
> with a call to the config() callback function. But as far as I see it that is happening correctly.
Maybe log (+dump_stack()) all the relevant calls from mac80211 to the
driver? That might give us a better idea of what's going on. Also,
Antonio, make sure you're using the very latest code. I for one need
sleep now :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-17 23:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 18:58 rt2x00 mesh support Antonio Marques
2009-01-23 19:02 ` Andrey Yurovsky
2009-01-24 11:40 ` António Marques
2009-03-15 11:54 ` Antonio Marques
2009-03-15 13:45 ` Ivo van Doorn
2009-03-16 1:58 ` Pat Erley
2009-03-16 13:29 ` Antonio Marques
2009-03-16 13:22 ` António Marques
2009-03-16 14:58 ` Ivo van Doorn
2009-03-16 19:12 ` Antonio Marques
2009-03-17 9:31 ` Ivo van Doorn
2009-03-17 14:11 ` Johannes Berg
2009-03-17 20:10 ` Johannes Berg
2009-03-17 21:50 ` Ivo van Doorn
2009-03-17 21:53 ` Johannes Berg
2009-03-17 22:04 ` Ivo van Doorn
2009-03-17 22:35 ` Johannes Berg
2009-03-17 23:01 ` Ivo van Doorn
2009-03-17 23:04 ` Johannes Berg [this message]
2009-03-18 10:02 ` Ivo van Doorn
2009-03-18 12:26 ` Antonio Marques
2009-03-18 12:48 ` Ivo van Doorn
2009-03-18 13:12 ` Johannes Berg
2009-03-18 13:31 ` Ivo van Doorn
2009-03-18 13:36 ` Johannes Berg
2009-03-19 21:55 ` Antonio Marques
2009-03-17 19:38 ` Antonio Marques
2009-03-17 22:03 ` Ivo van Doorn
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=1237331062.5100.9.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=andrey@cozybit.com \
--cc=froz@icix.org \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.