On Tue, 2012-12-11 at 10:35 +0000, Alberto Garau wrote:
> That's an *ancient* kernel. :( Any chance you can try it with a newer kernel?
>
> Unortunately not, that's our production kernel.
Even if you can't use it in real life, it could be worth trying a newer
kernel if you keep getting problems with that old one. You could also
try compat-wireless to get a newer wireless subsystem, at least.
> > Any other idea about why the scan command it's not properly working ?
>
> Another common problem is the clock settings. Are you sure the correct value for board_ref_clock in your board file?
>
> Are you talking about "wl->ref_clock = pdata->board_ref_clock;" in the probe ? Which value should I put for 38.4MHz due to the fact that it is an integer parameter ?
Yes, that's the value I'm talking about. You should put it in your
boardfile, something like this (from panda):
static struct wl12xx_platform_data omap_panda_wlan_data __initdata = {
.board_ref_clock = WL12XX_REFCLOCK_38, /* 38.4 MHz */
};
You can find these values in the include/linux/wl12xx.h file.
--
Luca.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
