linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Zwanenburg <stefanhetzwaantje@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: 'Chaoming_Li' <chaoming_li@realsil.com.cn>,
	linux-wireless@vger.kernel.org
Subject: Re: 答复: 答复: 答复: RTL8192SE and 802.11n problem
Date: Thu, 29 Sep 2011 04:32:17 +0200	[thread overview]
Message-ID: <4E83D8B1.1080002@gmail.com> (raw)
In-Reply-To: <4E83AD85.8050005@gmail.com>

On 09/29/2011 01:28 AM, Stefan Zwanenburg wrote:
> I had some time on my hands, so I tried to figure out how to dump the
> EEPROM data myself, and have done so using the following patch (based on
> linux-3.0.4):
>
> --- drivers/net/wireless/rtlwifi/rtl8192se/hw.c    2011-07-22
> 04:17:23.000000000 +0200
> +++ /home/psychotic/Desktop/rtl8192se_hw.c    2011-09-29
> 01:16:09.361978051 +0200
> @@ -1645,6 +1645,13 @@
>      RT_PRINT_DATA(rtlpriv, COMP_INIT, DBG_DMESG, ("MAP\n"),
>                hwinfo, HWSET_MAX_SIZE_92S);
>  
> +    printk("RTL8192SE - got EEPROM data:");
> +    for (i = 0; i < HWSET_MAX_SIZE_92S; i++) {
> +        if (i % 6 == 0)
> +            printk("\n  ");
> +        printk("%02X ", hwinfo[i]);
> +    }
> +
>      eeprom_id = *((u16 *)&hwinfo[0]);
>      if (eeprom_id != RTL8190_EEPROM_ID) {
>          RT_TRACE(rtlpriv, COMP_ERR, DBG_WARNING,
For posterity's sake, there was a slightly smaller workaround here, and
it would be as in the following patch:

--- drivers/net/wireless/rtlwifi/rtl8192se/hw.c    2011-09-29
04:20:14.660831861 +0200
+++ drivers/net/wireless/rtlwifi/rtl8192se/hw.c    2011-09-29
04:20:05.303831474 +0200
@@ -1642,7 +1642,7 @@
             HWSET_MAX_SIZE_92S);
     }
 
-    RT_PRINT_DATA(rtlpriv, COMP_INIT, DBG_DMESG, ("MAP\n"),
+    RT_PRINT_DATA(rtlpriv, COMP_INIT, DBG_EMERG, ("MAP\n"),
               hwinfo, HWSET_MAX_SIZE_92S);
 
     eeprom_id = *((u16 *)&hwinfo[0]);

It's rather nasty though, as it pretends that dumping the EEPROM data is
happening right before a fatal error has occurred. But there's really no
other way, as using sysfs to set the "global_debuglevel" is not good
enough because the EEPROM data is read right after the module is loaded
(making it hard to set the debuglevel in time).

If this info is useless to you, disregard it!

Stefan Zwanenburg

PS: the EEPROM data I mentioned in my previous message is still the same
though, so I won't bother to repost it.

  reply	other threads:[~2011-09-29  2:33 UTC|newest]

Thread overview: 9+ 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 [this message]
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
     [not found] <4E67CE3F.8090405@gmail.com>
     [not found] ` <4E67CEA3.7020709@gmail.com>
2011-09-08  2:23   ` Larry Finger
2011-09-08  2:50     ` Larry Finger
2011-09-08  3:23       ` Stefan Zwanenburg
2011-09-08  3:42         ` Larry Finger
     [not found]           ` <8117B559D4E64A83837479A8C342A5CA@realsil.com.cn>
     [not found]             ` <4E6E537D.5060404@gmail.com>
     [not found]               ` <24C6797004D84406B7564679CAE21531@realsil.com.cn>
     [not found]                 ` <4E74946A.3080206@gmail.com>
     [not found]                   ` <1903155944F64F00AC0C401593C20923@realsil.com.cn>
2011-09-19 20:04                     ` 答复: 答复: 答复: " Stefan Zwanenburg

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=4E83D8B1.1080002@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).