Eliad Peller <eliad@xxxxxxxxxx> writes: > If the wl18xx-conf.bin file is missing or invalid (e.g. due > to recent driver change), fallback to default configuration > instead of failing driver load. > > Reported-by: Marc Kleine-Budde <mkl@xxxxxxxxxxxxxx> > Signed-off-by: Eliad Peller <eliad@xxxxxxxxxx> This tells me that wl18xx is doing something wrong. The driver should still work normally even if user space is old (and vice versa). Should this configuration file (whatever that even is) have a version number in file name to handle incompatible changes in a backwards compatible manner? But I'm still planning to apply, just wanted to point out this. -- Kalle Valo -- 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