linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: jirislaby@gmail.com, mickflemm@gmail.com,
	mcgrof@do-not-panic.com, linux-wireless@vger.kernel.org,
	kvalo@codeaurora.org
Subject: ath5k filling logs (was Re: Low latency communication over wifi)
Date: Wed, 23 Sep 2015 13:27:24 +0200	[thread overview]
Message-ID: <20150923112724.GA22525@amd> (raw)
In-Reply-To: <20150923110343.GA19160@amd>

Hi!

> I hacked qcu.c to limit latencies:
> 
>   	  qi->tqi_cw_min = ath5k_cw_validate(0);
>           qi->tqi_cw_max = ath5k_cw_validate(20);
> 
> ...but I don't think it did what I wanted. What am I missing?
> 
> (I could use Intel 3945ABG-based card instead, but I figured out ath5k
> might be easier to hack?)

Speaking of ath5k... it fills logs with lots of messages:

[   53.486222] ath5k: ath5k_hw_get_isr: ISR: 0x00000400 IMR: 0x80081035
[   61.217713] ath5k: ath5k_hw_get_isr: ISR: 0x00000400 IMR: 0x80081035

Should I just delete the print from kernel, or is there something I
should debug?

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2015-09-23 11:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 11:03 Low latency communication over wifi Pavel Machek
2015-09-23 11:21 ` Johannes Berg
2015-09-26 10:24   ` Pavel Machek
2015-09-28  7:41     ` Johannes Berg
2015-09-28 12:15       ` Bastian Bittorf
2015-09-28 12:37         ` Johannes Berg
2015-09-28 12:52           ` Bastian Bittorf
2015-09-30 17:24       ` Pavel Machek
2015-09-30 17:33         ` Bastian Bittorf
2015-09-30 18:28         ` Johannes Berg
2015-09-23 11:27 ` Pavel Machek [this message]
2015-09-23 11:42 ` Bastian Bittorf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150923112724.GA22525@amd \
    --to=pavel@ucw.cz \
    --cc=jirislaby@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=mickflemm@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).