On Sun, Nov 27, 2011 at 11:23 PM, Jo-Philipp Wich wrote:
> this happens if you do not start with a fresh .config .
> The profiles actually just populate the CONFIG_DEFAULT_* variables. If
> everything is populated already they have no effect anymore.
Thanks Jow, I'll give a fresh .config a try.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
this happens if you do not start with a fresh .config .
The profiles actually just populate the CONFIG_DEFAULT_* variables. If
everything is populated already they have no effect anymore.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10
Hi guys,
Either I'm going something wrong, or this is intended behavior, or
there is a bug somewhere. When I select the:
Broadcom BCM43xx WiFi (wl, proprietary)
target profile in trunk, and build the image, I still get an image
that uses b43 (and b43-legacy). Is this because the wl driver does n