Hi.
Glenn Saberton wrote:
> Why is #ath9k invite only?
It's not particularly on-topic here, so just a short note: #ath9k should
not be invite-only (but I will check again). It forwards to #madwifi,
which is used for discussion about MadWifi, ath5k and ath9k.
Bye, Mike
___
On Sun, Sep 28, 2008 at 08:28:53PM -0700, Brian Prodoehl wrote:
> I have a patch set which adds pretty nice support to ath5k for the
> 900MHz cards out there, but right now the regulatory support I have
> for them is a hack. CRDA devs, are you open to adding the 900MHz ISM
> band to your database?
I have a patch set which adds pretty nice support to ath5k for the
900MHz cards out there, but right now the regulatory support I have
for them is a hack. CRDA devs, are you open to adding the 900MHz ISM
band to your database? Have you thought about how you might want to
support the 3.65GHz licen
* Update registers
* Update SREV values and add some PHY srevs
* Prepare ath5k.h for newer radios etc
Thanks to Atheros 's HAL source we now know for sure how many parts we have
and what their SREV values are. We also have some updates on registers. Prepare
ath5k for some major updates ;-)
* Add support for AR2417 (include pci id) since my previous patch doesn't sit
on top of base.c/ath5k.h anymore.
* Update module version to 0.6.0
Changes-Licensed-under: ISC
Signed-Off-by: Nick Kossifidis <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath5k/base.c |5 +++--
1 files changed
* Fix srev reporting during attach
Changes-Licensed-under: ISC
Signed-Off-by: Nick Kossifidis <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath5k/base.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath5k/base.c
b/drivers/net/wireless/ath5k
* Use QUIET mechanism to drain tx buffer on PCU for newer chips
* Make sure that INTPEND is really 1 and not 0x while checking for
pending interrupts
Changes-Licensed-under: ISC
Signed-Off-by: Nick Kossifidis <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath5k/dma.c | 49 ++
* Use new SREV values and PHY srevs to identify radio type durring attach
Changes-Licensed-under: ISC
Signed-Off-by: Nick Kossifidis <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath5k/attach.c | 182 ++-
1 files changed, 113 insertions(+), 69 deletions(-)
dif
Luis,
On Fri, 26 Sep 2008, Luis R. Rodriguez wrote:
> As part of our commitment to help support all of our Atheros devices
> under Linux we'd like to announce the release of our Atheros HAL for
> our 802.11abg chipsets under the ISC license.
>
> You can find it here:
>
> http://www.kernel.org/pub/
On 09/28/2008 01:06 PM, Gregory Nietsky wrote:
>
> Quick Observation ...
>
> it appears IEEE80211 types have been replaced with NL80211 types in
> kernel ... so would the following not be more correct and is opmode not
> defined as
>
> struct ath5k_softc {
>
>enum nl80211_iftype
According to the newly-released Atheros HAL code, asserting the
TSF reset bit will toggle a hardware internal state, resulting in a
spurious reset on the next chip reset. Whenever we force a TSF bit,
write the bit twice to clear the internal signal.
Signed-off-by: Bob Copeland <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luis R. Rodriguez wrote:
> As part of our commitment to help support all of our Atheros devices
> under Linux we'd like to announce the release of our Atheros HAL for
> our 802.11abg chipsets under the ISC license.
>
> You can find it here:
>
> http:
Quick Observation ...
it appears IEEE80211 types have been replaced with NL80211 types in
kernel ... so would the following not be more correct and is opmode not
defined as
struct ath5k_softc {
enum nl80211_iftype opmode;
.
@@ -2130,14 +2129,15 @@ ath5k_beacon_config(str
Gents it is great to see this happen one snippet more and you will be
able to set the interface into AP mode from userspace hostapd and friends.
diff --git a/drivers/net/wireless/ath5k/base.c
b/drivers/net/wireless/ath5k/base.c
index e09ed2c..69aad6e 100644
--- a/drivers/net/wireless/ath5k/base
John W. Linville wrote:
> On Fri, Sep 26, 2008 at 02:57:01PM -0700, Luis R. Rodriguez wrote:
>> As part of our commitment to help support all of our Atheros devices
>> under Linux we'd like to announce the release of our Atheros HAL for
>> our 802.11abg chipsets under the ISC license.
>>
>> You can
Sam Leffler wrote:
>>
>> MadWifi is based on a proprietary HAL which is slightly different
>> than this one, so no, its still non-free. The "free" drivers where
>> I think focus should be put in is ath5k and ath9k as they are now both
>> merged as part of the Linux kernel.
>>
>
> The hal is not
Luis R. Rodriguez wrote:
> As part of our commitment to help support all of our Atheros devices
> under Linux we'd like to announce the release of our Atheros HAL for
> our 802.11abg chipsets under the ISC license.
>
> You can find it here:
>
> http://www.kernel.org/pub/linux/kernel/people/mcgrof
Luis R. Rodriguez wrote:
> On Fri, Sep 26, 2008 at 03:55:58PM -0700, Maxim Levitsky wrote:
>
>> If I understand this correctly, madwifi is no longer a non-free driver?
>>
>
> MadWifi is based on a proprietary HAL which is slightly different
> than this one, so no, its still non-free. The "f
Hi,
Brian Prodoehl wrote:
> I'm running the 20080925 snapshot of compat-wireless-old, and I'm
> seeing disconnects during large file transfers with the AR2425. I say
> "disconnects" because I'm set up promiscuously in IBSS mode, so it
> isn't just a simple disassociation. When it dies, I see thi
19 matches
Mail list logo
