On Sun, 28 Oct 2007 02:09:54 +0200 Evgeni Golov wrote:
> chiisai# ./ath_info 03:00.00
> Mmap of device at 0x0003 for 0x1 bytes failed - Invalid argument
Erm, got it.
chiisai# ./ath_info 0xc400
-==Device Information==-
MAC Version: 5212 (0x50)
MAC Revision: 5213 (0x56)
PHY Revis
On Sun, 28 Oct 2007 03:01:58 +0300 Nick Kossifidis wrote:
> Can you run ath_info tool (found in
> madwifi/tools) and post the output ???
How exactly should I run it? At the moment I get:
chiisai# ./ath_info 03:00.00
Mmap of device at 0x0003 for 0x1 bytes failed - Invalid argument
(it
2007/10/28, Evgeni Golov <[EMAIL PROTECTED]>:
> On Sun, 28 Oct 2007 01:39:53 +0200 Evgeni Golov wrote:
>
> > On Sun, 28 Oct 2007 00:47:18 +0300 Nick Kossifidis wrote:
> >
> > > That seems realy weird, i have the same mac/phy revision as you
> > > (5.6/4.1) and it works ok. Can you try to reload ath
On Sun, 28 Oct 2007 01:39:53 +0200 Evgeni Golov wrote:
> On Sun, 28 Oct 2007 00:47:18 +0300 Nick Kossifidis wrote:
>
> > That seems realy weird, i have the same mac/phy revision as you
> > (5.6/4.1) and it works ok. Can you try to reload ath5k module and see
> > if it wakes up ?
>
> rmmod + modp
fill_tx_desc is used for fast frames operation, since
we don't support fast frames (and since fill_tx_desc
had a bug -thanx to Ulrich Meis for finding that out-)
these functions are not needed (+ they are misleading
because they don't "fill" any tx descriptor).
I couldn't test this patch much so p
*Warn on partially supported chips (eg. 5414/5424)
These chips need work on PHY part, recently Reyk posted
a workaround so that they can work on 2GHz but i believe
that the problem is related to PHY initialization. Plz
we need help with these...
I did some tests on a 5414 at 5GHz and it seemed t
On Sun, 28 Oct 2007 00:47:18 +0300 Nick Kossifidis wrote:
> That seems realy weird, i have the same mac/phy revision as you
> (5.6/4.1) and it works ok. Can you try to reload ath5k module and see
> if it wakes up ?
rmmod + modprobe give me:
ACPI: PCI interrupt for device :03:00.0 disabled
ACP
*Add PCI IDs for 5416/5418.
*Print a message during attach that
these chips are not yet supported.
for base.c
Changes-licensed-under: 3-clause-BSD
for ath5k.h
Changes-licensed-under: ISC
Signed-Off-by: Nick Kossifidis <[EMAIL PROTECTED]>
---
diff --git a/drivers/net/wireless/ath5k/ath5k.h
Use SREV instead of pci id to identify single chip solutions.
Srev is more accurate info to identify the chip + this makes
it possible to identify some 5424 chips found on thinkpads with
faulty 5212 pci id.
Changes-licensed-under: ISC
Signed-Off-by: Nick Kossifidis <[EMAIL PROTECTED]>
---
diff
* Add new Silicon Revision values (hex values written on chip) to be able to
identify them.
* Give more infos about mac/phy/radio revision during attach.
Changes-licensed-under: 3-clause-BSD
Signed-Off-by: Nick Kossifidis <[EMAIL PROTECTED]>
---
diff --git a/drivers/net/wireless/ath5k/ath5k.h
Remove sysctl tables.
We shouldn't use /proc to configure things.
Changes-licensed-under: 3-clause-BSD
Signed-Off-by: Nick Kossifidis <[EMAIL PROTECTED]>
---
diff --git a/drivers/net/wireless/ath5k/base.c
b/drivers/net/wireless/ath5k/base.c
index 73c0a38..382bb23 100644
--- a/drivers/net/wirele
I've renamed some functions for better maintainability...
ath5k_mode_init -> ath5k_mode_setup
ath5k_rxbuf_init -> ath5k_rxbuf_setup
Because it's not just initialization + we use
"setup" on the rest of the code (eg. beacon_setup).
ath5k_tx_bf -> ath5k_txbuf_setup
Obvious
ath5k_cleanup_txbuf -> at
2007/10/19, Dan Williams <[EMAIL PROTECTED]>:
> Anyone working on this part or is there just not enough bandwidth? It's
> completely unrecognized with fairly recent wireless-everything. I've
> got a machine with one here, would be happy to test stuff if there's
> anything to test.
>
> Dan
>
I go
2007/10/27, Evgeni Golov <[EMAIL PROTECTED]>:
> Hi guys,
>
> first of all, thanks for developing a free driver for Atheros devices :)
>
> I have a Netgear WG511T PCMCIA card, which is shown in lspci as:
> 03:00.0 Ethernet controller [0200]: Atheros Communications, Inc. AR5212
> 802.11abg NIC [168c:
Hi guys,
first of all, thanks for developing a free driver for Atheros devices :)
I have a Netgear WG511T PCMCIA card, which is shown in lspci as:
03:00.0 Ethernet controller [0200]: Atheros Communications, Inc. AR5212
802.11abg NIC [168c:0013] (rev 01).
According to [1], this card should work (h
On Sat, Oct 27, 2007 at 02:58:58AM +0300, Nick Kossifidis wrote:
> Do you mind if i also send the rest of them on the same series (not
> only cleanups but code changes also) ?
That seems fine to me.
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED]
This patch fixes the setup of transmit descriptors. tx_control_1 is set
in ath5k_hw_setup_{2,4}word_tx_desc but was subsequently overriden by
ath5k_hw_fill_{2,4}word_tx_desc. The victims were FRAME_TYPE and NO_ACK.
The missing no_ack in broadcast frames caused them to be retried up to
the retry_lim
17 matches
Mail list logo