On 11/21/2011 01:34 PM, Thomas Langås wrote:
On Mon, Nov 21, 2011 at 10:13 PM, Thomas Langås
<thomas.langas@xxxxxxxxxxx> wrote:
Hmm, doing that, and loading this as a module instead of compiling it into the
kernel seemed to work.
Is there a reason for this not working when being compiled into the kernel? Is
it possible that I need to change the order of some of the units
being initialized
in my machine-description / init?\
Usually we compile it as module instead of built-in. But I just tried it
with built-in and it can intialize and scan. Some issue did happen
during joining an AP. So I would suggest use module for your
development for now.
Ok, so I get the device listed as a wlan0-device, and I see the driver
being able to communicate
with the chip, sort of (it can read registers at least), but then I
start seeing errors like this (from
the previously attached log):
It's possible that the firmware carshed. Are you using the
firmware/nvram from Linux repository? You should use the nvram that fits
your platform.
Franky
--
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
