On 7/25/2013 2:34 PM, Nathan Goings wrote:
On 7/25/2013 3:31 AM, Mark Kettenis wrote:
New diff. Please give this one a shot.
Thanks! I'll get to it as soon as possible! (~3 hours) I need to
figure out how to apply a diff first...
Couple notes on my testing.
- Having severe laten
On 7/25/2013 3:31 AM, Mark Kettenis wrote:
New diff. Please give this one a shot.
Thanks! I'll get to it as soon as possible! (~3 hours) I need to
figure out how to apply a diff first...
Couple notes on my testing.
- Having severe latency or packetloss issues with some games on a
Windows
On 7/24/2013 6:11 PM, Artturi Alm wrote:
Hi,
No //-comments, { on the same line as if/else, and else after }, but
since both have only one statement, no braces needed.
Same goes for the for-loops, I suggest reading style(9).
- Artturi
Whoops, completely forgot. This should be correct:
--- /
On 7/24/2013 5:26 AM, Mark Kettenis wrote:
Well, that will certainly break existing support for the RT3090 chips.
So a bit more work will be needed. First step would be to provide a
proper diff, and show us your dmesg!
I made a few debugging changes, I've rolled all that back and made the
bar
Well, I'm a moron. I spent several weeks working on the Ralink driver,
profiling linux vendor provided code; looking at changes between 2860,
35xx, and 3090; and nagging various people. I made a single change and
the ral(4) driver is working on the Ralink 35xx series in both client
and hostap
ll the vendor code between 2860 and 35xx. Now I'm going
to profile between 35xx and 3090. In the meantime, I was hoping to get
in contact with someone who knew more about the ral(4) driver, or
wireless drivers in particular.
Thanks!
Nathan Goings
