linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Batten <BryanBatten@sbcglobal.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	linville@tuxdriver.com, rt2400-devel@lists.sourceforge.net
Subject: Re: [Rt2400-devel] [PATCH] rt2x00: Fix NULL pointer error in	adhoc/master mode
Date: Wed, 09 Jul 2008 11:33:56 -0700	[thread overview]
Message-ID: <48750494.8010802@sbcglobal.net> (raw)
In-Reply-To: <200807092029.10007.IvDoorn@gmail.com>

Ivo van Doorn wrote:
...
> 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. ;)

I know. But I suspect that in this case, the datasheet just *may* be 
correct.

>> 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.
> 

Thanks,
-- 
Bryan
-
"Beyond the point of no return, there's no going back."

Narration to "Mars Rising" on the Science Channel

      reply	other threads:[~2008-07-09 18:34 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
2008-07-09 18:33         ` Bryan Batten [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=48750494.8010802@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 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).