lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1260710042.2442.340.camel@johannes.local>
Date:	Sun, 13 Dec 2009 14:14:02 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Alessandro Suardi <alessandro.suardi@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: 2.6.32-git5+, CONFIG_WEXT_PRIV and Broadcom's driver for
 BCM4322  Wireless chips

On Sat, 2009-12-12 at 16:40 +0100, Alessandro Suardi wrote:

> But: what is the best option here to make CONFIG_WEXT_PRIV visible at
>  kernel build time if only an external module should select it - but selection
>  is not actually happening at kernel build time ?
> Could CONFIG_WEXT_PRIV be made a separate user-selectable option ?

Your only option is selecting some other (ancient) driver that selects
WEXT_PRIV. We will not make that Kconfig symbol visible just because
Broadcom decided that they want to continue screwing their users :)

IOW -- there's no such option available to you at all. Select
PCMCIA_RAYCS or whatever.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ