On Sat, Sep 13, 2008 at 06:51:13PM +0200, Marcel Holtmann wrote: > Hi Johannes, > > > > I am pretty happy that you caught it, because that was my whole point > > > from the discussion we had at OLS. The userspace part might not be in > > > place and we must ensure that everything still works as before :) > > > > I thought your point was that you wanted regulatory_hint_regdom(...) > > that the driver can use to tell us what the EEPROM regulatory is, which > > wouldn't have been affected by this bug :) But anyway, yeah, it's a bug. > > of course I want regulatory_hint_regdom :) > > I was just trying to make clear how important it is to make sure we work > with a broken userspace or without userspace support at all Which is, of course, why I asked Luis to implement the compatibility option, and why I decided to let it cook for a bit in wireless-testing before sending it to Dave for net-next-2.6... :-) John -- John W. Linville linville@xxxxxxxxxxxxx -- 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
