Re: Changing the way we handle region codes on Linux (public thread)

["John W. Linville" <linville@tuxdriver.com>]

On Fri, Nov 06, 2009 at 11:20:34AM -0800, Luis R. Rodriguez wrote:
> On Fri, Nov 6, 2009 at 10:38 AM, John W. Linville
> <linville@tuxdriver.com> wrote:
> > On Fri, Nov 06, 2009 at 09:45:29AM -0800, Luis R. Rodriguez wrote:
> >> On Fri, Nov 6, 2009 at 9:29 AM, Bob Copeland <me@bobcopeland.com> wrote:
> >> > On Fri, Nov 6, 2009 at 11:57 AM, Luis R. Rodriguez <mcgrof@gmail.com> 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.
> >
> > <snip>
> >
> >> 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.
> >
> > That's the thing about "legacy" stuff -- it doesn't go away just from
> > ignoring it!
> 
> True.
> 
> > FWIW, I think Bob's suggestion makes a lot of sense.
> 
> Patches welcomed then :)

Haha...OK, I'll put it on my list...  Lurkers are welcome to beat me to it!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.