On Thu, November 30, 2006 08:09, Adrian Bunk wrote:
>> > But if anyone wants to ever revive this driver, the code is still
>> > present in the older kernel releases.
>>
>> I'm unconvinced by that argument in the general case. People don't go
>> looking back through git history, do they? Drivers suc
On 11/30/06, Peter Stuge <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 30, 2006 at 09:46:25AM +0100, Fab G. wrote:
> I would assume it depends on the order in which drivers register with
> the core. My guess is that that depends on the order in which they
> are built by the kernel build system. That in
On Thu, Nov 30, 2006 at 09:46:25AM +0100, Fab G. wrote:
> Er..yes I meant hostap_cs, but when I load it manually through
> modprobe it does not do anything (when orinoco[_cs] is blacklisted).
Oh, ok. Then you could try removing the blacklisting and moving away
the orinoco_cs driver, then hostap_
On Thu Nov 30 00:48:37 EST 2006, Peter wrote:
>The module I think you want is named hostap_cs, not just hostap. The
>latter is a set of common code used by hostap_cs, hostap_pci and
>hostap_plx. If you load hostap_cs it will automatically pull in
>hostap, but without hostap_cs no driver will care a