From: "SL Baur" <steve@xemacs.org>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: yi.zhu@intel.com, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iwlwifi 3945 debug parameter should be writable via sysfs
Date: Mon, 21 Apr 2008 21:30:09 -0700 [thread overview]
Message-ID: <ed10ee420804212130r59833142lc031afe49107123d@mail.gmail.com> (raw)
In-Reply-To: <1ba2fa240804211451o1c7eb062q3ae292c06ed11406@mail.gmail.com>
On 4/21/08, Tomas Winkler <tomasw@gmail.com> wrote:
> On Mon, Apr 21, 2008 at 10:10 AM, SL Baur <steve@xemacs.org> wrote:
> > Is there any reason why the debug parameter in the iwlwifi driver
> > should be read-only?
> it doesn't have any affect on debug output though. This variable is
> copied to to another one in pci proble
> so unless you have 2 cards there is no use for it.
> Run time debug output can be handled through debug_level sysfs entry
> /sys/bus/pci/drivers/iwl4965/debug_level
> Yet this will be changed as well to be per device instead of per driver
O.K. The driver help recommended turning on debug for first time usage
and I was surprised when I didn't get any debug output. And I see now
that /proc/bus/pci/drivers/iwl3945/debug_level *is* writable. I'm lost in a
twisty maze of /sys directories, all subtlely different.
The driver itself works fine, but I'm having trouble getting decent speed out
of it, similar to the horrible performance I had under another operating
system, not quite as bad but still worse than a MacBook Pro. Any clues on what
I can look for to see why it so relatively slow? I'm going to put it to the WoW
test as soon as I can get a modern userland & Wine on the machine, it's running
RHEL 4 now. The machine is a Lenovo T60.
-sb
prev parent reply other threads:[~2008-04-22 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 7:10 SL Baur
2008-04-21 21:51 ` Tomas Winkler
2008-04-22 4:30 ` SL Baur [this message]
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=ed10ee420804212130r59833142lc031afe49107123d@mail.gmail.com \
--to=steve@xemacs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.com \
--cc=yi.zhu@intel.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
all inboxes | Powered by JetHome®