On 4/21/08, Tomas Winkler <tomasw@xxxxxxxxx> wrote: > On Mon, Apr 21, 2008 at 10:10 AM, SL Baur <steve@xxxxxxxxxx> 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 -- 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
