From: Ivo van Doorn <ivdoorn@gmail.com>
To: Antonio Marques <froz@icix.org>
Cc: Andrey Yurovsky <andrey@cozybit.com>, linux-wireless@vger.kernel.org
Subject: Re: rt2x00 mesh support
Date: Tue, 17 Mar 2009 23:03:39 +0100 [thread overview]
Message-ID: <200903172303.40046.IvDoorn@gmail.com> (raw)
In-Reply-To: <58D3A916-8548-4DEC-BEC6-09AFE4CEBCBD@icix.org>
On Tuesday 17 March 2009, Antonio Marques wrote:
> On Mar 17, 2009, at 9:31 , Ivo van Doorn wrote:
> > On Monday 16 March 2009, Antonio Marques wrote:
> >> On Mar 16, 2009, at 14:58 , Ivo van Doorn wrote:
> >>> On Monday 16 March 2009, Ant=F3nio Marques wrote:
> >>>>
> >>>> As requested, I have attached the output of the script run befor=
e =20
> >>>> 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 d=
o
> >>>> change from
> >>>> one state to the next. Any further pointers to help debug this? =
=20
> >>>> 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
> >>> <rt2x00_regdump.sh>
> >>
> >> Fixed, new dumps are attached.
> >
> > Thanks for the dumps, the reason why the beaconing isn't working
> > is (fortunately) very obvious from the registers point of view.
> > The "generate beacons" bit is simply not enabled. However the reaso=
n
> > why this bit has not been set escapes me. Could you apply the attac=
hed
> > patch? This will add extra debug messages to the driver to see when=
=20
> > the
> > beacon generation bit is set.
> >
> > Thanks,
> >
> > Ivo
> > <rt73usb.beacon.diff>
>=20
> Here are the relevant portions of the dmesg with the aforementioned
> patch applied.
>=20
> After interface creation and before 'iwlist mesh scan':
<...snip...>
> Hope this is useful.
It absolutely is :)
Thanks,
Ivo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-03-17 22:03 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
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 [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=200903172303.40046.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).