On Wed, Mar 27, 2013 at 7:04 PM, Peter Stuge pe...@stuge.se wrote:
Adrian Chadd wrote:
the quick fix is to re-reset the PCI slot or the PCI bus.
Read the quote from Daniel's email again. It explains how that caused
the problem.
In his bad case there was a reset at time 1 and another reset
Hi all,
thanks for all your replies. Let me tell my findings just in case
it helps.
* adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] wrote:
The general consensus at work is - BIOSes are buggy and don't
necessarily reset the PCI bus correctly.
So either you can do your own PCI bus
On 03/28/2013 04:04 PM, Steffen Dettmer wrote:
I talked with an expert of my unit about resetting PCI express
cards. The units have a special controller (I^2C) able to power
off and power on the card slots. I was told that this does not
handle the PCI reset line correctly (leaves it open),
Hi,
some time ago there was a thread Sparklan WPEA-121N AR9382 168c:abcd about
the issue that the mentioned device was erroneously reported as device ID
0xabcd. There were EEPROM issues assumed and BIOS issues reported that could
cause this effect (by resetting the PCI bus at system power on)
Hi,
The general consensus at work is - BIOSes are buggy and don't
necessarily reset the PCI bus correctly.
So either you can do your own PCI bus reset post-boot (and
re-enumerate all the PCI devices, including initialising their BARs)
or smack your vendor to fix their BIOSes. I can't really make
Adrian Chadd wrote:
The general consensus at work is - BIOSes are buggy
That is very true..
and don't necessarily reset the PCI bus correctly.
..but this doesn't make any sense at all.
So either you can do your own PCI bus reset post-boot
What *exactly* is meant by PCI bus reset here? I
Daniel Smith wrote:
as I understand the explanation it was that a typically
Root Bridge reset is not supposed to occur until later in the
initialization. In this case, the version of AMI that was on this
board did a reset at power-on and then the required one later. This
first reset
Sure, here's what's going on:
* There's a PCI bus reset. It's a pin. On the PCI bus.
* The BIOS can yank that down to reset all the devices.
* There's timing requirements for how long that pin can be pulled down
to reset and release.
* After the PCI bus is reset, the atheros MAC initialises the
Am 27.03.2013 23:33, schrieb Adrian Chadd:
Sure, here's what's going on:
* There's a PCI bus reset. It's a pin. On the PCI bus.
* The BIOS can yank that down to reset all the devices.
* There's timing requirements for how long that pin can be pulled down
to reset and release.
* After the
Adrian Chadd wrote:
the quick fix is to re-reset the PCI slot or the PCI bus.
Read the quote from Daniel's email again. It explains how that caused
the problem.
In his bad case there was a reset at time 1 and another reset at time 2.
Removing the reset at time 1 and keeping an unchanged reset
Michael Schwingen wrote:
If you do a PCI reset just at the time when the MAC is doing an I2C
read, the I2C EEPROM will hang in the middle of a bus cycle, with no
possibility to reset it when the MAC does the next read access, so at
least the first read will get corrupt data.
Yes, that makes
On 27 March 2013 16:04, Peter Stuge pe...@stuge.se wrote:
Adrian Chadd wrote:
If something (the reset at time 1) is able to screw up hardware so
badly that even a correct reset (time 2) does not *actually* reset
the hardware then I would consider that a very serious bus IP
problem in the
On Tue, Jan 10, 2012 at 4:54 PM, Adrian Chadd adr...@freebsd.org wrote:
On 10 January 2012 13:25, Daniel Smith viscous.liq...@gmail.com wrote:
We actually had the exact same problem with a board we were
prototyping on. Working with the manufacturer it turned out to be a
feature of the AMI
On 11 January 2012 04:57, Daniel Smith viscous.liq...@gmail.com wrote:
So how exactly did it interfere with it?
Adrian
IANAEE, but as I understand the explanation it was that a typically
Root Bridge reset is not supposed to occur until later in the
initialization. In this case, the version
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
On Tue, Jan 10, 2012 at 3:45 PM, Hasan Rashid
hras...@avionica.com wrote:
Adrian,
This is not an OS issue as I see similar results in Windows,
it is definitely a low-level hardware issue.
I am using a Portwell PQ7-C100XL carrier
Rashid
Cc: Daniel Smith; ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
Since bugzilla.kernel.org is again live, would you please create a bug
report there so we can attach all of this information to it?
That way future people can benefit from our
On 11 January 2012 09:39, Hasan Rashid hras...@avionica.com wrote:
Adrian,
If you don't mind can you take the lead on that? I will contribute to
testing and verification.
Hm, seems I can't find my bugzilla account and it won't let me recover
the password without knowing hte password.
Sigh.
...@gmail.com]
Sent: Tuesday, January 10, 2012 11:20 AM
To: Hasan Rashid
Cc: Mohammed Shafi; ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
Hi,
I am having the same problem with two devices. Sparklan WPA-127N
(AR9380) and WLE300NX 6B (AR9390).
I added
Sáez [mailto:manuelsa...@gmail.com]
Sent: Tuesday, January 10, 2012 11:20 AM
To: Hasan Rashid
Cc: Mohammed Shafi; ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
Hi,
I am having the same problem with two devices. Sparklan WPA-127N
(AR9380) and WLE300NX
:37 PM
To: Hasan Rashid
Cc: Manuel Sáez; ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
Hi,
The BIOS doesn't read the EEPROM on the NIC. The NIC is supposed to
read the EEPROM upon powerup (and on PCI bus reset?) and setup the
initial PCI/register
On 10 January 2012 10:17, Hasan Rashid hras...@avionica.com wrote:
Adrian,
I have only been able to narrow it down to the BIOS and unfortunately I do
not have a PCI bus analyzer at my disposal.
Right, so it's likely something like:
* what power states the BIOS tries to place the NIC into at
: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
On 10 January 2012 10:17, Hasan Rashid hras...@avionica.com wrote:
Adrian,
I have only been able to narrow it down to the BIOS and
unfortunately I do not have a PCI bus analyzer at my disposal.
Right, so it's likely something like:
* what power
On 10 January 2012 12:45, Hasan Rashid hras...@avionica.com wrote:
Adrian,
This is not an OS issue as I see similar results in Windows, it is definitely
a low-level hardware issue.
Right, but as I said, it could be something that is worked around in softwar.e
I am using a Portwell
...@gmail.com [mailto:adrian.ch...@gmail.com]
On Behalf Of Adrian Chadd
Sent: Tuesday, January 10, 2012 4:11 PM
To: Hasan Rashid
Cc: Manuel Sáez; ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
On 10 January 2012 12:45, Hasan Rashid hras...@avionica.com wrote
On Tue, Jan 10, 2012 at 3:45 PM, Hasan Rashid hras...@avionica.com wrote:
Adrian,
This is not an OS issue as I see similar results in Windows, it is definitely
a low-level hardware issue.
I am using a Portwell PQ7-C100XL carrier board with a Portwell PQ7-M105 Q7
module. The radio is
@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
On Tue, Jan 10, 2012 at 3:45 PM, Hasan Rashid
hras...@avionica.com wrote:
Adrian,
This is not an OS issue as I see similar results in Windows,
it is definitely a low-level hardware issue.
I am using a Portwell
On 10 January 2012 13:23, Hasan Rashid hras...@avionica.com wrote:
You would think so, but it actually performs really well. I have used the
radio in a 50+ client video streaming scenario and I didn't encounter any
performance related issues.
What is most annoying is that only Sparklan's
On 10 January 2012 13:25, Daniel Smith viscous.liq...@gmail.com wrote:
We actually had the exact same problem with a board we were
prototyping on. Working with the manufacturer it turned out to be a
feature of the AMI BIOS they were using on the card (sorry I don't
have the version right off
for all your help!
Hasan R.
-Original Message-
From: Mohammed Shafi [mailto:shafi.at...@gmail.com]
Sent: Tuesday, April 19, 2011 12:21 AM
To: Hasan Rashid
Cc: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
On Tue, Apr 12, 2011 at 10:02 PM
-devel] Sparklan WPEA-121N AR9382 168c:abcd
On Mon, Apr 11, 2011 at 11:24 PM, Hasan Rashid hras...@avionica.com wrote:
I have attached the driver load output in dmesg.
By the way why does AR9382 require Kernel 2.6.36 or higher? Can you list
the major requirements?
because the hardware code(HAL
Adrian Chadd wrote:
Is there an easy way to get an EEPROM/OTP contents dump in ath9k?
For AR93xx you can try to use the following script:
#!/usr/bin/perl -w
my $debugPath = '/debug/ath9k/phy0';
sub RegGet($)
{
open(F,$debugPath/regidx) or die(Unable to open $debugPath/regidx.);
printf(F
only.
Hasan R.
-Original Message-
From: ath9k-devel-boun...@lists.ath9k.org
[mailto:ath9k-devel-boun...@lists.ath9k.org] On Behalf Of Peter Stuge
Sent: Monday, April 11, 2011 12:20 PM
To: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
Kernel modules: ath9k
Hasan R.
-Original Message-
From: Mohammed Shafi [mailto:shafi.at...@gmail.com]
Sent: Tuesday, April 12, 2011 7:47 AM
To: Hasan Rashid
Cc: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
On Mon, Apr 11, 2011 at 11
[mailto:shafi.at...@gmail.com]
Sent: Tue 4/12/2011 7:46 AM
To: Hasan Rashid
Cc: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
On Mon, Apr 11, 2011 at 11:24 PM, Hasan Rashid hras...@avionica.com wrote:
I have attached the driver load output in dmesg
@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
On Mon, Apr 11, 2011 at 11:24 PM, Hasan Rashid hras...@avionica.com
wrote:
I have attached the driver load output in dmesg.
By the way why does AR9382 require Kernel 2.6.36 or higher? Can you
list the major
functionality.
#ieee80211n=1
Thank you!
Regards, Hasan R.
From: Mohammed Shafi [mailto:shafi.at...@gmail.com]
Sent: اتوار 10/04/2011 8:14 AM
To: Hasan Rashid
Cc: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
-boun...@lists.ath9k.org
[mailto:ath9k-devel-boun...@lists.ath9k.org] On Behalf Of Mohammed Shafi
Sent: Monday, April 11, 2011 10:13 AM
To: Hasan Rashid
Cc: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
2011/4/11 Hasan Rashid hras...@avionica.com:
That's
@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
2011/4/11 Hasan Rashid hras...@avionica.com:
That's exactly what I did, also, I had to add the vendor ID in the
hw_init function for the driver to fully load. I got it to work after
making these changes in the ath9k driver.
yes
...@lists.ath9k.org
[mailto:ath9k-devel-boun...@lists.ath9k.org] On Behalf Of Mohammed Shafi
Sent: Sunday, April 10, 2011 11:41 AM
To: Adrian Chadd
Cc: ath9k-devel@lists.ath9k.org; Peter Stuge
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
On Sun, Apr 10, 2011 at 9:04 PM, Adrian Chadd adr
...@gmail.com]
Sent: Monday, April 11, 2011 12:05 PM
To: Hasan Rashid
Cc: Adrian Chadd; ath9k-devel@lists.ath9k.org; Peter Stuge
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
On Mon, Apr 11, 2011 at 6:58 AM, Hasan Rashid hras...@avionica.com wrote:
I have contacted the manufacturer
@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
2011/4/11 Hasan Rashid hras...@avionica.com:
That's exactly what I did, also, I had to add the vendor ID in the
hw_init function for the driver to fully load. I got it to work after
making these changes in the ath9k driver
Adrian Chadd wrote:
Is there an easy way to get an EEPROM/OTP contents dump in ath9k?
No. I have some PCI problem, so no progress in the EEPROM direction
from me.
//Peter
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
Mohammed Shafi wrote:
to make sure that HT is configured in driver please do this
diff --git a/drivers/net/wireless/ath/ath9k/hw.c
b/drivers/net/wireless/ath/ath9k/hw.c
index 1b5bd13..720a866 100644
--- a/drivers/net/wireless/ath/ath9k/hw.c
+++ b/drivers/net/wireless/ath/ath9k/hw.c
@@
Sent: Monday, April 11, 2011 12:20 PM
To: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
Mohammed Shafi wrote:
to make sure that HT is configured in driver please do this
diff --git a/drivers/net/wireless/ath/ath9k/hw.c
b/drivers/net/wireless/ath
On Sat, Apr 9, 2011 at 2:00 AM, Hasan Rashid hras...@avionica.com wrote:
Hello All,
I recently purchased a Sparklan WPEA-121N, it uses the AR9382 chipset. It is
mentioned as supported on the device list, however, when I load that ath9k
modules nothing comes up.
Does ath9k support this
Mohammed Shafi wrote:
Is this a serious proposal from Atheros, or just your attempt at
a quick fix?
No! its purely a personal idea (am completely responsible for the
mistake),and I will take a look at it carefully to fix this.
Sorry, I didn't mean that you made a mistake, just that the
On Sun, Apr 10, 2011 at 8:41 PM, Peter Stuge pe...@stuge.se wrote:
Mohammed Shafi wrote:
Is this a serious proposal from Atheros, or just your attempt at
a quick fix?
No! its purely a personal idea (am completely responsible for the
mistake),and I will take a look at it carefully to fix
Incorrect or misplaced EEPROM/OTP data, perhaps?
From what I gather, the PCI ID on earlier devices is loaded out of EEPROM by
the silicon itself at power-on. 'abcd' sounds a bit too convenient to be
what's in EEPROM/OTP; so maybe it's a default value in the silicon?
(All just conjecture here at
On Sun, Apr 10, 2011 at 9:04 PM, Adrian Chadd adr...@freebsd.org wrote:
Incorrect or misplaced EEPROM/OTP data, perhaps?
From what I gather, the PCI ID on earlier devices is loaded out of EEPROM by
the silicon itself at power-on. 'abcd' sounds a bit too convenient to be
what's in EEPROM/OTP;
expect, a throughput of 70-80 Mbps.
Thank you!
Regards, Hasan R.
From: Mohammed Shafi [mailto:shafi.at...@gmail.com]
Sent: اتوار 10/04/2011 8:14 AM
To: Hasan Rashid
Cc: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
] Sparklan WPEA-121N AR9382 168c:abcd
On Sun, Apr 10, 2011 at 9:04 PM, Adrian Chadd adr...@freebsd.org wrote:
Incorrect or misplaced EEPROM/OTP data, perhaps?
From what I gather, the PCI ID on earlier devices is loaded out of
EEPROM by the silicon itself at power-on. 'abcd' sounds a bit too
Hasan Rashid wrote:
The only problem now is that the driver transmit at non-HT rates only.
I guess that is the best it can do with a bogus EEPROM.
//Peter
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
/2011 8:14 AM
*To:* Hasan Rashid
*Cc:* ath9k-devel@lists.ath9k.org
*Subject:* Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
On Sun, Apr 10, 2011 at 5:39 PM, Mohammed Shafi shafi.at...@gmail.com
wrote:
On Sat, Apr 9, 2011 at 2:00 AM, Hasan Rashid hras...@avionica.com
wrote:
Hello
Hello All,
I recently purchased a Sparklan WPEA-121N, it uses the AR9382 chipset.
It is mentioned as supported on the device list, however, when I load
that ath9k modules nothing comes up.
Does ath9k support this chipset? I compiled compat-wirless on Ubuntu
10.10 on an x86 Core2Duo machine.
54 matches
Mail list logo
