Stanislaw, On Mon, 2011-01-31 at 02:23 -0800, RafaÅ MiÅecki wrote: > 2011/1/31 Stanislaw Gruszka <sgruszka@xxxxxxxxxx>: > > On Fri, Jan 28, 2011 at 03:20:21PM -0800, wwguy wrote: > >> > What is easiest and less time consuming: > >> > > >> > this: > >> > > >> > $ mv /lib/firmware/iwlwifi-5000-exp.ucode /lib/firmware/iwlwifi-5000-exp.ucode.not_use > >> > > >> > or this: > >> > > >> > $ make menuconfig > >> > navigate to find option and edit it > >> > $ make modules > >> > $ make modules_install > >> > > >> > ? > >> > > >> > > Also put it in Kconfig file, so it is easy for user to see they are > >> > > using experimental option. Agree? > >> > > >> > Not really. I believe someone who download a tarball, unpack it and copy > >> > files to /lib/firmware is pretty much aware what he/she is doing. > >> > > >> Agree whoever download the tarball know what he/she is doing, but I am > >> not fully agree the driver always use experimental uCode if it is in the > >> firmware directory > > > > I do not understand what for you need that, but ok, I can live with it. > > > > John, please skip this patch. > > Maybe make it module parameter? Like use_experimental_fw, default to 0? > I think module parameter is better idea, if you agree, and I will ack Thanks Wey -- 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
