Ben Greear <greearb@xxxxxxxxxxxxxxx> writes: > As for being confusing, the current code is nasty and it is very hard > to have any idea why things do or do not work, especially if you do not > have ability to add printk all over the place to figure out what the > code is actually doing. Heh, this is exatly what I do when I debug regulatory issues :) > I think some more effort should go into printing out a lot more > information about the regulator domain decisions, through printk > or related call if nothing better is found... IMHO the regulatory code is the most fragile part of Linux wireless stack and needs a rewrite. It needs to be simple and easy to understand. -- 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
