linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 9 Jul 2008 20:29:09 +0200	[thread overview]
Message-ID: <200807092029.10007.IvDoorn@gmail.com> (raw)
In-Reply-To: <4874FC95.3050904@sbcglobal.net>

On Wednesday 09 July 2008, Bryan Batten wrote:
> Ivo van Doorn wrote:
> > On Saturday 05 July 2008, Bryan Batten wrote:
> >> 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.
> 
> Looking thru the RT2400 and RT2500 datasheets, I notice that on pp. 12
> of the 2400 datasheet, CSR8 bits 0 and 1 are described. On the same
> page of the RT2500 datasheet, CSR8 bits 0 and 1 are not described. If
> that is not a typo, that means to me that on the RT2400 you can
> mask off beacon timer and wakeup timer interrupts with CSR8, but on
> the RT2500 you cannot.

Yes, but if you look again you see that the legacy driver does define it,
and even includes the description of bits 9 -> 19
And the legacy driver source code has always been more reliable then
the datasheet, so I would put my money on the code. ;)

> Would it be possible to verify with Ralink that this is not a typo in
> the RT2500 datasheet?

I'll see what I can find out.

Ivo

  reply	other threads:[~2008-07-09 18:20 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
2008-07-09 17:59     ` Bryan Batten
2008-07-09 18:29       ` Ivo van Doorn [this message]
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=200807092029.10007.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 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).