From: Ivo van Doorn <ivdoorn@gmail.com>
To: Bryan Batten <BryanBatten@sbcglobal.net>
Cc: linville@tuxdriver.com,
linux-wireless <linux-wireless@vger.kernel.org>,
rt2400-devel@lists.sourceforge.net
Subject: Re: [Rt2400-devel] [PATCH] rt2x00: Fix NULL pointer error in adhoc/master mode
Date: Sat, 5 Jul 2008 23:19:39 +0200 [thread overview]
Message-ID: <200807052319.40115.IvDoorn@gmail.com> (raw)
In-Reply-To: <486FD8AF.5050001@sbcglobal.net>
On Saturday 05 July 2008, Bryan Batten wrote:
> Ivo van Doorn wrote:
> ...
> > That is interesting, have you tried controlling CSR14 and more
> > specifically the TBCN or BeaconGen fields?
>
> No. It turns out that if I set the RT2500's CSR14 to zero (the default
> power on state according to the data sheet) at driver initialization,
> there are no beacon interrupts until enabled in AsicEnableIbssSync().
> I deem this a bug, the fix for which in now in CVS.
Heh, that will bring down the number of raised interrupts in the legacy driver. :)
You might want to add it to rt2400 as well, I expect the same behavior for that. ;)
I'll put the initialization into rt2x00 as well, since it doesn't set it to 0 by default either.
Ivo
next prev parent reply other threads:[~2008-07-05 21:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 13:11 [PATCH] rt2x00: Fix NULL pointer error in adhoc/master mode Ivo van Doorn
2008-07-05 18:33 ` [Rt2400-devel] " Bryan Batten
2008-07-05 18:42 ` Ivo van Doorn
2008-07-05 18:43 ` Johannes Berg
2008-07-05 19:26 ` Ivo van Doorn
2008-07-05 19:22 ` Johannes Berg
2008-07-05 19:37 ` Ivo van Doorn
2008-07-05 19:37 ` Johannes Berg
2008-07-05 21:17 ` Ivo van Doorn
2008-07-05 20:25 ` Bryan Batten
2008-07-05 21:19 ` Ivo van Doorn [this message]
2008-07-09 17:59 ` Bryan Batten
2008-07-09 18:29 ` Ivo van Doorn
2008-07-09 18:33 ` Bryan Batten
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=200807052319.40115.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=BryanBatten@sbcglobal.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rt2400-devel@lists.sourceforge.net \
/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.