linux-ath5k-devel mailing list

FromSubjectsort iconDate
Nick Kossifidis
Re: [ath5k-devel] [PATCH v6 8/9] ath5k: Add AHB bus support.
You probably mean if (unlikely((reg >= 0x4000) && (reg < 0x5000) && (ah->ah_mac_srev >= AR5K_SREV_AR2315_R6)) because it's very possible to just have a register outside this range (all other units eg PCU, QCU, PHY etc -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
Nov 26, 5:53 pm 2010
Nick Kossifidis
Re: [ath5k-devel] [PATCH v6 9/9] ath5k: Fix reset and in ...
I think it would be much cleaner if we had a different function to handle wisoc reset instead of putting both on nic_reset. How about having a ath5k_hw_wisoc_reset This is wrong... #define AR5K_RESET_CTL_MAC 0x00000004 /* MAC reset (PCU+Baseband ?) [5210] */ this bit was only available on earlier chips. To reset mac on later chips (WiSoC too) you need to use AR5K_RESET_CTL_PCU and we already do that below. This is something I have to clean up actually, bit 0 is reset mac (both PCU + DMA) ...
Nov 26, 5:29 pm 2010
Nick Kossifidis
Re: [ath5k-devel] [PATCH v6 6/9] ath5k: Add a function t ...
Why not naming that ath5k_hw_read_srev_pci and the other one ath5k_hw_read_srev_ahb and name both ath5k_bus_read_srev ? Also please at least follow the naming scheme, all hw related functions are ath5k_hw_*. -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
Nov 26, 5:38 pm 2010
Nick Kossifidis
Re: [ath5k-devel] [PATCH v6 6/9] ath5k: Add a function t ...
Or at least make them all ath5k_<bus type>_* eg ath5k_ahb_read_srev and ath5k_pci_read_srev, let's keep it clean... -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
Nov 26, 5:43 pm 2010
=?utf-8?q?Luk=C3=A1= ...
Re: [ath5k-devel] [PATCH 16/30] ath5k: Set all IFS inter ...
Although aPHY-RX-START-Delay is specified in the standard, it's not needed on Atheros hardware, probably the hardware starts the timeout countdown after it switches to RX mode (so aPHY-RX-START-Delay is added implicitly). See my discussion with Felix Fietkau a year ago, starting here: http://www.mail-archive.com/ath5k-devel@lists.ath5k.org/msg02810.html The calculation used in set_coverage_class is also the same as the one in Madwifi driver. When I wrote that code, I intentionally kept the ...
Nov 26, 6:57 pm 2010
Nick Kossifidis
Re: [ath5k-devel] [PATCH 16/30] ath5k: Set all IFS inter ...
Στις 26 Νοεμβρίου 2010 2:54 π.μ., ο χρήστης Jonathan Guerin When we convert to core clock units it's what we should do, all timings should change the same way. I don't know what this aPHY-RX-START-Delay is but if it changes that way we can use absolute values as we do for slot time and sifs. Maybe we can add a function ath5k_hw_get_default_ack_timeout that gets default sifs + default slot time + the needed aPHY-RX-START-Delay based on the standard (but what about turbo mode -40MHz-, do you think that ...
Nov 26, 6:31 pm 2010
Jonathan Guerin
Re: [ath5k-devel] [PATCH 16/30] ath5k: Set all IFS inter ...
I'm going to be ashamed to admit that this is going way beyond my understanding. You guys understand the hardware way more than I can. Once registers don't exactly map to an 802.11 value, I'm honestly out of my league. I hope I've helped find the correct values for parameters that are lifted straight out of the standard, but I'm don't want to make any comments when I don't know the full picture. Cheers, _______________________________________________ ath5k-devel mailing ...
Nov 27, 12:35 am 2010
previous daytodaynext day
November 26, 2010November 27, 2010November 29, 2010