Message-Id: <6.1.1.1.2.20060813071741.02ae87e0@192.168.6.12>
Date: Sun, 13 Aug 2006 07:20:46 +0200
To: linux-kernel@vger.kernel.org
From: Roger While <simrw@sim-basis.de>
Subject: Re: debug prism wlan
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 870
Lines: 23

Alistair John wrote:
 > Daniel wrote:
 >> Hey, that did it! But now I am a liddle confused. It worked fine before.
 >> Why does it not work while interface is not up?

 > I'm not sure, but I think you've just been lucky.
 > I've had this problem even before prism54 was merged.
 > Some in-tree drivers won't upload the firmware until you ifconfig
 > up them, which obviously means they won't respond adequately
 > to the wireless extension requests. Maybe a bug?

Nope, no bug. It allows the driver to be built non-modular.
When non-modular, the resources are not available,
at boot time, to load the firmware.

Roger While


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/