From: Stefan Zwanenburg <stefanhetzwaantje@gmail.com>
To: 李朝明 <chaoming_li@realsil.com.cn>
Cc: 'Larry Finger' <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org
Subject: Re: 答复: 答复: 答复: 答复: RTL8192SE and 802.11n problem
Date: Fri, 30 Sep 2011 01:58:14 +0200 [thread overview]
Message-ID: <4E850616.3040003@gmail.com> (raw)
In-Reply-To: <4E84FBF6.2020609@gmail.com>
On 09/30/2011 01:15 AM, Stefan Zwanenburg wrote:
> On 09/29/2011 10:55 AM, 李朝明 wrote:
>> Dear Larry:
>>
>> I don't kown why this efuse is wrong, did Zwanenburg use the same
>> driver with yours ?
> Hi!
> I may be no Larry, but I just diffed the latest version of the
> drivers/net/wireless/rtlwifi directory (obtained from the github mirror
> of linus' repository) with the one from the kernel I'm currently
> running, and I don't notice a whole lot of changes (besides code
> cleanups and differences in the debugging macro "calls"), but there is
> something going on in efuse.c with no more "hoffset" variable in
> efuse_get_current size, but that shouldn't matter, as the variable was
> assigned but never used again.
> I also see there was a whole lot of work put into pci.c, as it looks
> it's had a revamp. I'm not sure it will fix my problems, but I'm going
> to try to run 3.1-rc4 and see if I can get an 802.11n link going.
>
> I'll get back to you on how that went later!
>
> Stefan Zwanenburg
Well, I just compiled 3.0-rc4, and I'm now running it, but alas, still
no 802.11n link to my AP, and (perhaps unsurprisingly) the EEPROM that
gets dumped upon detecting the PCI NIC is exactly the same as it was
before, so there couldn't be some problem with the EFUSE reading code.
I guess that leaves us with the possibility my AP is not sending some
packets (see Larry's message about that) during the association, which
makes the driver not work as it should...
Is there anything else I can try to help you guys figure out what may be
wrong?
Stefan Zwanenburg
PS: I'll keep running this kernel for a few days to see if I get the
same problem as in mentioned in the discussion "3.1-rc6 + rtl8192se
issue", even though I apparently don't have the very latest kernel source.
prev parent reply other threads:[~2011-09-29 23:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E77AECF.7090001@gmail.com>
[not found] ` <4E820130.7080801@gmail.com>
2011-09-27 21:00 ` 答复: 答复: 答复: RTL8192SE and 802.11n problem Larry Finger
2011-09-27 22:25 ` Stefan Zwanenburg
2011-09-28 4:56 ` Larry Finger
2011-09-28 23:28 ` Stefan Zwanenburg
2011-09-29 2:32 ` Stefan Zwanenburg
2011-09-29 3:28 ` Larry Finger
[not found] ` <0EF5E594196F41B48B0B4D168B714838@realsil.com.cn>
2011-09-29 23:15 ` 答复: " Stefan Zwanenburg
2011-09-29 23:58 ` Stefan Zwanenburg [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=4E850616.3040003@gmail.com \
--to=stefanhetzwaantje@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--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).