linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Leonardo H. Souza Hamada" <leonardo.hamada@ufra.edu.br>
To: linux-wireless@vger.kernel.org
Subject: Re: zd1211rw on ppc (iBook G4) -- Solved, somewhat)
Date: Sat, 12 Sep 2009 19:43:26 -0300	[thread overview]
Message-ID: <4AAC240E.20104@ufra.edu.br> (raw)
In-Reply-To: <4A9D7DC0.6050701@ufra.edu.br>

Hi all,

At this moment, after tweaking the zd1211rw code in kernel
2.6.31-gentoo, finally I am able to use the WLI-U2-KG54L wireless usb
dongle on this old ibook.

Browsing the source with a cross referencing tool
(http://lxr.free-electrons.com) and making additional checking points, I
could trace the issue as follow.

The problem is that this device returns a regulatory region of 0x49,
which is not defined in the zd1211rw tables. So the call

r <http://lxr.free-electrons.com/ident?i=r> = zd_reg2alpha2 <http://lxr.free-electrons.com/ident?i=zd_reg2alpha2>(mac <http://lxr.free-electrons.com/ident?i=mac>->regdomain, alpha2);

will fail the initialization process.


Workaround:

----snip----
int zd_mac_init_hw(struct ieee80211_hw *hw)
{
...
        r = zd_read_regdomain(chip, &default_regdomain);
        /* A unknown regulatory of 0x49 will be set default to
ZD_REGDOMAIN_FCC. */
        if (0x49 == default_regdomain)
                default_regdomain = ZD_REGDOMAIN_FCC;
...
----snip----

The above code will force the default regulatry to be FCC code for this
case. I think that this was the case in previous zd1211rw driver. What
is the country code for 0x49 region? There is a better way?


Thanks all,

Phew!! Leonardo





  reply	other threads:[~2009-09-12 22:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31 16:39 zd1211rw on ppc (iBook G4) Leonardo H. Souza Hamada
2009-08-31 17:25 ` Hin-Tak Leung
     [not found]   ` <4A9C0ADC.6050607@ufra.edu.br>
2009-08-31 18:26     ` Hin-Tak Leung
2009-08-31 19:27       ` Michael Buesch
2009-08-31 19:35         ` Hin-Tak Leung
     [not found]           ` <69e28c910908311414s191aafa6ib0bdae8ed4ace27d@mail.gmail.com>
     [not found]             ` <3ace41890908311602g4a976ec5k4f1f5145662cf183@mail.gmail.com>
2009-08-31 23:11               ` Gábor Stefanik
2009-09-01 12:56           ` Michael Buesch
2009-09-01 20:02       ` Leonardo H. Souza Hamada
2009-09-12 22:43         ` Leonardo H. Souza Hamada [this message]
2009-09-13 10:13           ` zd1211rw on ppc (iBook G4) -- Solved, somewhat) Hin-Tak Leung
2009-09-14  3:41             ` Hin-Tak Leung
2009-09-14  4:09               ` Luis R. Rodriguez
2009-09-14 16:47                 ` Leonardo H. Souza Hamada
2009-09-14 21:11                   ` Hin-Tak Leung
     [not found]                     ` <8ea57b3c57061154c0d312925100c827.squirrel@webmail.ufra.edu.br>
2009-09-15  1:08                       ` Hin-Tak Leung
2009-09-23  0:50         ` zd1211rw on ppc (iBook G4) Hin-Tak Leung
2009-09-27 19:14           ` Leonardo H. Souza Hamada
2009-09-27 20:08             ` Hin-Tak Leung

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=4AAC240E.20104@ufra.edu.br \
    --to=leonardo.hamada@ufra.edu.br \
    --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).