Hi On Tue, Mar 29, 2011 at 08:59, John Crispin <j...@phrozen.org> wrote: > On 29/03/11 09:53, Luca Olivetti wrote: >> Al 29/03/2011 9:48, En/na Luca Olivetti ha escrit: >> >>> >>> I'll see what I can do for both issues (regdomain and generic), however >>> remember that I can only test with my router and wouldn't want to >>> mislead somebody else that it should also work with his. >> > > your current patch is misleading, a generic version wont be. > >> BTW, if you can merge everything else, please do, so I can synch to svn >> and work from there. > > check the timeline first next time, happened already > >> It will take a lot of time for me to fix those issues, I'm not really > > ok, so when the work is on your desk, its ok that it takes time, but > when it is on other peoples desks it is not ?! :) > >> interested in making wifi work (I'm not going to use it), besides, >> performance is atrociously bad.
Sorry for intruding here, but are you guys using the in-kernel ath9k, or the 'crap' vendor driver? AFAIS, the current in-kernel driver relies on regulatory domain for frequency restrictions. It could solve your current problem. But, as always, there may be hundreds of reasons why this approach may not be possible. > > i guess you did something wrong then > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > Luis Correia _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
