From: Bryan Batten <BryanBatten@sbcglobal.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
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, 05 Jul 2008 11:33:25 -0700 [thread overview]
Message-ID: <486FBE75.5040100@sbcglobal.net> (raw)
In-Reply-To: <200807051511.57995.IvDoorn@gmail.com>
Ivo van Doorn wrote:
...
> Note that the "raise beacondone interrupts without a beacon" is
> also a bug, and will be addressed later.
...
FWIW, I've never been able to figure out a way to shut it off in the
legacy drivers. Unless there's some mechanism I've missed, I would
consider this a bug, but its a hardware bug because - in the rt2500
driver at least - even disabling it in the interrupt mask register has
no effect.
I think it would be more accurately termed a target beacon
transmission time interrupt. The rt61 driver's ISR simply does not
test for the condition. The rt2400 and rt2500 drivers do nothing if
not in adhoc mode. If in adhoc mode, they both assume a beacon frame
is ready to go and send it. This relies on a canned frame that is set
up during initialization.
Hope this is helpful,
--
Bryan
-
"Beyond the point of no return, there's no going back."
Narration to "Mars Rising" on the Science Channel
next prev parent reply other threads:[~2008-07-05 18:40 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 ` Bryan Batten [this message]
2008-07-05 18:42 ` [Rt2400-devel] " 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
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=486FBE75.5040100@sbcglobal.net \
--to=bryanbatten@sbcglobal.net \
--cc=ivdoorn@gmail.com \
--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.