Jes Sorensen <Jes.Sorensen@xxxxxxxxxx> writes: > Kalle Valo <kvalo@xxxxxxxxxxxxxx> writes: >> Jes.Sorensen@xxxxxxxxxx writes: >> >>> Per default only devices I have actually tested will be enabled. If >>> you are interested in trying it out with other 8188cu/8188ru/819[12]cu >>> dongles, you need to enable CONFIG_RTL8XXXU_UNTESTED. Please report >>> test results back to me. >>> >>> Note if you enable this driver, it may clash with CONFIG_RTL8192U, >>> CONFIG_R8723AU, and CONFIG_RTL8192CU (rtlwifi). Please pay attention >>> to which module you load and/or use modprobe blacklists. >> >> May clash? So how does this work in practise? Is the clash referring >> CONFIG_RTL8XXXU_UNTESTED enabled or disabled? >> >> I think we should only have one driver automatically supporting certain >> hardware, and not have a driver randomly chosen and forcing users to use >> a blacklist. > > We already have the clash, if you enable CONFIG_RTL8192U in staging it > clashes with rtlwifi's CONFIG_RTL8192CU. Ripping out the above two > drivers at this point isn't going to do users any good. > >> Also how do we make sure that distros don't enable >> CONFIG_RTL8XXXU_UNTESTED? They are notarious of enabling kconfig options >> without thinking. > > Some distros enable staging whether you ask them or not. I think > CONFIG_RTL8XXXYU_UNTESTED is pretty safe and will most likely just work > for the devices on that list, but the driver will spit out a warning > asking the person to report test results to me. Just one more note - we could put UNTESTED under EXPERIMENTAL Cheers, Jes -- 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
