a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Uli Kunitz
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
pObj->SetReg(reg, ZD_CR129, 0x12);
pObj->SetReg(reg, ZD_CR130, 0x10);
pObj->SetReg(reg, ZD_CR47, 0x1E);
}
}
The patch from Holden would set ZD_CR128 to 0x12 for the highest channel,
which would not reflect the logic of the vendor driver.
Kind regards,
Uli
--
U
. This patching might be US-specific and we
cannot simply apply the setting for top channel of another domain
instead of channel 11. One option would be to set the value only under
the US regulatory domain.
Kind regards,
Uli
--
Uli Kunitz ([EMAIL PROTECTED])
-
To unsubscribe from this list
o check all channels because your
ESSID could be on anyone of the channels.
Uli
--
Uli Kunitz - [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Larry Finger wrote:
> Uli Kunitz wrote:
> > Larry Finger wrote:
> >
> > > * A new routine (ieee80211_init_geo ?) will be written to be called by the
> > > driver to load the geo structure into the kernel. Information passed to
> > > the
> > > d
Would it be possible to support the regulatory domain codes as
used in the outdated table 105 in Corrigendum 1 for 802.11b? The
ZD1211 EEPROM contains only this code. An easy translation
function would be sufficient. Maybe the group codes could be
misused for it.
Uli
--
Uli Kunitz ([EMAIL PROT
