Any more word on this?
Gabor posted a series as RFC that would fix this properly ->
http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2013-March/005837.html
Yeah, and that series looks good. Unfortunately, it is too intrusive to still apply for 3.9.
John L., could we get in a scheme where we apply John C.'s patch for 3.9 and then use Gabor's series for 3.10?
Don't know how that works with making sure that this patch is reverted for 3.10.
Can you coordinate, or should I help you with this?
Hi,
if we could apply my original 'dirty' patch as a temporary fix for 3.9,
that would be great. Its not an optimal solution but it at least makes
the code compile/work.
Gabor and myself have also accumulated a pile of other patches. In
addition to the 8 patch series that splits the pci/generic code, there
is a 20 patch series, that adds rt3662/rt3883 support, a 7 patch series
that adds rt5350 support and another 8 patches that add OF support.
I am planning to setup a git tree with all these after easter and then
send them to the list for review. Ideally these patches all make it into
3.10 as we will also be merging the remaining Ralink SoC patches via the
linux-mips tree for 3.10 (with the exception of the ethernet driver as
it will need a rewrite before I can send it upstream)
John
--
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
