On Fri, Nov 6, 2009 at 9:29 AM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote: > On Fri, Nov 6, 2009 at 11:57 AM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: > >> I think that sums it up. > > I personally still like the idea of pushing the vendor-specific > codes out to user space and having psuedo-country codes for > those (e.g. "ATH_37"). Then the driver doesn't need all of the > static rules loaded all the time and it would drop a lot of > policy code from the driver. CRDA could be enhanced to load > multiple databases, one for pure iso-3166 codes, one with > Atheros codes, one with Intel, etc. There is obviously an added complexity added to userspace for this, but it seems that having that complexity in userspace is better than in kernel space. Only reason for not doing this I think would be perhaps if we can really avoid such custom region codes. Ultimately what makes more sense to me is to see more trust on the user's location based on alternative inputs like geoclue but since this year the Google Summer of Code project failed miserly even by the midterm who knows when we'll be able to get proper feeds we can use in the kernel. But with that said -- I think the region-code scheme is overly complex and am not sure if aiding it is something we should focus energy and resources on. It would seem better to me to focus on more cleaner solutions and leave that old stuff as legacy solutions. Luis -- 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
