From: Ivo van Doorn <ivdoorn@gmail.com>
To: "António Marques" <froz@icix.org>
Cc: Andrey Yurovsky <andrey@cozybit.com>, linux-wireless@vger.kernel.org
Subject: Re: rt2x00 mesh support
Date: Mon, 16 Mar 2009 15:58:00 +0100 [thread overview]
Message-ID: <200903161558.01070.IvDoorn@gmail.com> (raw)
In-Reply-To: <F3209A42-65EA-4F71-8443-67E2F8CAFA3F@icix.org>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On Monday 16 March 2009, António Marques wrote:
> On Mar 15, 2009, at 13:45 , Ivo van Doorn wrote:
> > On Sunday 15 March 2009, Antonio Marques wrote:
> >> Upon further investigation, beaconing does not work after configuring
> >> an interface in mesh point mode but running 'iwlist mesh scan'
> >> triggers something in the driver that enables beaconing.
> >> After executing this command beacons are generated and correctly
> >> received at other nodes.
> >
> > Thats odd, but very interesting :)
> > Could you enable debugfs and CONFIG_RT2X00_LIB_DEBUGFS and
> > use the script from http://kernel.org/pub/linux/kernel/people/ivd/tools/rt2x00_regdump.sh
> > to create a register dump before running 'iwlist mesh scan' and
> > afterwards.
> > (So basically when beaconing is broken and when it is working).
> >
> > Thanks,
> >
> > Ivo
>
>
> As requested, I have attached the output of the script run before and
> after
> running 'iwlist mesh scan'. Unfortunately there seems to be no change in
> the output. I have also included the queue statistics as these do
> change from
> one state to the next. Any further pointers to help debug this? I'll
> gladly test
> any patches that try to address this issue.
The dumps aren't correct, I had forgotten to update the script on the website
after some API for the rt2x00 debugfs interface changes recently.
Attached is the correct patch.
Ivo
[-- Attachment #2: rt2x00_regdump.sh --]
[-- Type: application/x-shellscript, Size: 2260 bytes --]
next prev parent reply other threads:[~2009-03-16 14:58 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 [this message]
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
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=200903161558.01070.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=andrey@cozybit.com \
--cc=froz@icix.org \
--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 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).