On Tue, Jun 22, 2010 at 12:38:03PM -0700, Luis R. Rodriguez wrote:
On Tue, Jun 22, 2010 at 12:37 PM, Luis R. Rodriguez mcg...@gmail.com wrote:
On Tue, Jun 22, 2010 at 12:31 PM, Johannes Stezenbach j...@sig21.net
wrote:
Does CONFIG_PCIEASPM provide a way for the user to modifiy
On Wed, Jun 23, 2010 at 09:28:57AM -0700, Luis R. Rodriguez wrote:
On Wed, Jun 23, 2010 at 7:39 AM, Johannes Stezenbach j...@sig21.net wrote:
If enabling ASPM comes with a performance penalty (which is not unexpected,
there is usually a tradeoff between performance and power consumption
On Tue, Jun 22, 2010 at 07:44:26PM +0100, Matthew Garrett wrote:
On Tue, Jun 22, 2010 at 11:28:20AM -0700, Luis R. Rodriguez wrote:
Heh, this whole patch and thread was started because Jussi tested
ath5k with pcie_aspm=force (on a pre PCIE 1.1 device (?)) . I have
been trying to explain
On Sun, Aug 09, 2009 at 07:04:01PM +0200, Johannes Stezenbach wrote:
With the nl80211 driver everything works.
Although it might not be that important I though I should
report the following observations when using
wpa_supplicant with the nl80211 driver onn ath5k:
1. wpa_supplicant complains
On Fri, Aug 07, 2009 at 11:51:55PM +0200, Johannes Stezenbach wrote:
On my old Thinkpad T42p running linux-2.6.31-rc5-246-g90bc1a6,
after suspend-to-RAM ath5k cannot associate to an AP using WPA
anymore. It worked with kernel 2.6.29.1.
FWFI, it also works with 2.6.30. (I could
On Sun, Aug 09, 2009 at 12:06:03PM -0400, Bob Copeland wrote:
On Fri, Aug 7, 2009 at 5:51 PM, Johannes Stezenbachj...@sig21.net wrote:
If I use nl80211 the second ifup fails with
SIOCSIFFLAGS: Input/output error messages and the follwing
is in dmesg:
ath5k phy0: failed to wakeup the
Hi,
On my old Thinkpad T42p running linux-2.6.31-rc5-246-g90bc1a6,
after suspend-to-RAM ath5k cannot associate to an AP using WPA
anymore. It worked with kernel 2.6.29.1. I'm not using network
manager etc. but connect manually with ifup wlan0=foo with the
following in /etc/network/interfaces:
