2009/2/4 Nick Kossifidis :
> 2009/2/4 Bob Copeland :
>> On Tue, Feb 03, 2009 at 06:28:47PM +0200, Nick Kossifidis wrote:
>>> Nice catch ;-)
>>>
>>> Another difference i remembered is that we now don't set the TPC
>>> register to 3f (until we fix the whole tx power stuff). I'll try to
>>> reproduce
2009/2/4 Bob Copeland :
> On Tue, Feb 03, 2009 at 06:28:47PM +0200, Nick Kossifidis wrote:
>> Nice catch ;-)
>>
>> Another difference i remembered is that we now don't set the TPC
>> register to 3f (until we fix the whole tx power stuff). I'll try to
>> reproduce this with my ar2425 as it turns it
On Tue, Feb 03, 2009 at 06:28:47PM +0200, Nick Kossifidis wrote:
> Nice catch ;-)
>
> Another difference i remembered is that we now don't set the TPC
> register to 3f (until we fix the whole tx power stuff). I'll try to
> reproduce this with my ar2425 as it turns it also has problems.
And the wi
2009/2/4 Tulio Magno Quites Machado Filho :
> Suppression of unused ah_regdomain_hw and correction of ah_regdomain
>
> Signed-off-by: Tulio Magno Quites Machado Filho
> ---
> drivers/net/wireless/ath5k/ath5k.h |3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/drivers
2009/2/4 Tulio Magno Quites Machado Filho :
> Separate both calibrations and call noise floor calibrations only when
> necessary.
>
> Signed-off-by: Tulio Magno Quites Machado Filho
> ---
> drivers/net/wireless/ath5k/base.c |4
> drivers/net/wireless/ath5k/phy.c |8
> driv
I forgot to say that everything is "Changes-licensed-under: 3-Clause-BSD"
Sorry,
--
Tulio Magno
On Wed, Feb 4, 2009 at 1:30 AM, Tulio Magno Quites Machado Filho
wrote:
> Hello all,
>
> I've made a small patch today to change the way noise floor
> calibration is called.
> As I've read in the c
Hello all,
I've made a small patch today to change the way noise floor
calibration is called.
As I've read in the code, it was necessary to separate noise floor
calibration from I/Q calibration and create a way to call noise floor
calibration less times.
I've made the changes based on legacy hal,
Separate both calibrations and call noise floor calibrations only when
necessary.
Signed-off-by: Tulio Magno Quites Machado Filho
---
drivers/net/wireless/ath5k/base.c |4
drivers/net/wireless/ath5k/phy.c |8
drivers/net/wireless/ath5k/reg.h |1 +
3 files changed, 5
Suppression of unused ah_regdomain_hw and correction of ah_regdomain
Signed-off-by: Tulio Magno Quites Machado Filho
---
drivers/net/wireless/ath5k/ath5k.h |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath5k/ath5k.h
b/drivers/net/wireless/ath5k/
On Tue, 2009-02-03 at 20:06 +0200, Nick Kossifidis wrote:
> 2009/2/3 Maxim Levitsky :
> > On Tue, 2009-02-03 at 18:24 +0200, Nick Kossifidis wrote:
> >> 2009/2/3 Nick Kossifidis :
> >> > 2009/2/3 Maxim Levitsky :
> >> >> I just tried your 5 patches, as they could fix hangs in the device,
> >> >> th
2009/2/3 Maxim Levitsky :
> On Tue, 2009-02-03 at 18:24 +0200, Nick Kossifidis wrote:
>> 2009/2/3 Nick Kossifidis :
>> > 2009/2/3 Maxim Levitsky :
>> >> I just tried your 5 patches, as they could fix hangs in the device,
>> >> that I experience occasionally, when resuming my aspire one from
>> ram.
On Tue, 2009-02-03 at 18:24 +0200, Nick Kossifidis wrote:
> 2009/2/3 Nick Kossifidis :
> > 2009/2/3 Maxim Levitsky :
> >> I just tried your 5 patches, as they could fix hangs in the device,
> >> that I experience occasionally, when resuming my aspire one from
> ram.
> >>
> >> I applied the patches,
2009/2/3 Bob Copeland :
> On Sat, 31 Jan 2009 04:31:47 +0200, Nick Kossifidis wrote
>> int ath5k_hw_reset(struct ath5k_hw *ah, enum nl80211_iftype op_mode,
>> struct ieee80211_channel *channel, bool change_channel)
>
> Here's another thing I just noticed:
>
>> {
>> + u32 s_seq[10], s_an
2009/2/3 Nick Kossifidis :
> 2009/2/3 Maxim Levitsky :
>> I just tried your 5 patches, as they could fix hangs in the device,
>> that I experience occasionally, when resuming my aspire one from ram.
>>
>> I applied the patches, and I got very unstable system, that tended to
>> hang even before X.
>
On Sat, 31 Jan 2009 04:31:47 +0200, Nick Kossifidis wrote
> int ath5k_hw_reset(struct ath5k_hw *ah, enum nl80211_iftype op_mode,
> struct ieee80211_channel *channel, bool change_channel)
Here's another thing I just noticed:
> {
> + u32 s_seq[10], s_ant, s_led[3], staid1_flags, tsf_up,
2009/2/3 Maxim Levitsky :
> I just tried your 5 patches, as they could fix hangs in the device,
> that I experience occasionally, when resuming my aspire one from ram.
>
> I applied the patches, and I got very unstable system, that tended to
> hang even before X.
>
> When it didn't hang, I tried su
I'm first time using mailing lists... I triying to reply correctly,
sorry if something wrong :)
Please, look at my post "frequencies above 5.7 GHz is not
available"... I need at least all legal frequencies (not license)...
Is somewhere documentation on Atheros chipsets available?
Documentation on
On Tue, Feb 3, 2009 at 9:08 AM, Maxim Levitsky wrote:
> I just tried your 5 patches, as they could fix hangs in the device,
> that I experience occasionally, when resuming my aspire one from ram.
>
> I applied the patches, and I got very unstable system, that tended to
> hang even before X.
>
> Wh
Just to note, the dmesg when device went off the bus:
> [ 5110.354898] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 5110.355039] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
> doesn't support DPO or FUA
> [ 5110.464144] usb 5-5: reset high speed USB device using ehci_hcd and
>
So, driver sometimes hangs,... we think that this is reset related,
maybe...
I today did some research on that.
First of all it happens very rarely, so hard to reproduce,
but as old saying goes, this always happens, when you don't want it
to happen.
I managed to find out that there are 2 unrelate
I just tried your 5 patches, as they could fix hangs in the device,
that I experience occasionally, when resuming my aspire one from ram.
I applied the patches, and I got very unstable system, that tended to
hang even before X.
When it didn't hang, I tried suspend to ram cycle, but it hanged then
Interesting. However, I never noticed madwifi taking up so much CPU
power. Even the first scan did take about as much time as I reported (I
know this is unscientific reasoning, but It's all I can bring up atm)
the ath5k process goes idle after scan is done. More importantly, it
makes my musicpla
Okay, I booted into my old 2.6.27. (Sorry, forgot the reply to all)
I loaded ath_pci, and did:
time iwlist ath0 scan > /dev/null
real 0m0.361
user0m000s
sys 0m108s
Unload ath_pci, load ath5k:
time iwlist ath0 scan > /dev/null
real 0m4.462s
user 0m0.004s
sys 0m0.004s
(note, the system was other
Hi.
Alex Williams wrote:
> "Also I noted that iwlist scan now takes quite some time to
> complete (Usually 3-5 seconds). On Madwifi-ng the scan results came
> almost instantly."
>
> Scan can not be completed instantly:
True. Still the quoted author may be right: MadWifi supports background
scanni
"Also I noted that iwlist scan now takes quite some time to
complete (Usually 3-5 seconds). On Madwifi-ng the scan results came
almost instantly."
Scan can not be completed instantly: we need to wait and then catch
beacons if any. Then repeat for another frequency... Beacon intervals
could be many
25 matches
Mail list logo
