From: Bob Copeland <me@bobcopeland.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: Felix Fietkau <nbd@openwrt.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] ath5k: Clean up eeprom parsing and add missing calibration data
Date: Fri, 21 Nov 2008 09:05:08 -0500 [thread overview]
Message-ID: <20081121140508.GA26731@hash.localnet> (raw)
In-Reply-To: <40f31dec0811202121i7d0b5931g9b416a9122f9e0e5@mail.gmail.com>
On Fri, Nov 21, 2008 at 07:21:07AM +0200, Nick Kossifidis wrote:
> 2008/11/21 Bob Copeland <me@bobcopeland.com>:
> > Can we add the rest here?
> >
> > + AR5K_EEPROM_READ_HDR(AR5K_EEPROM_MISC2, ee_misc2);
>
> Problem is that legacy-hal doesn't make use of these infos (along with
> many other infos stored in eeprom !), so i don't know what eeprom
> versions have them. Go on and use them but for now assume that they
> are only available for eeprom versions 5 and above and i'll check out
> my eeprom dumps etc to find out.
Ok, no rush on this - we can add the patch for these later when we know
which versions specify misc5.
The legacy-hal uses this bit, but does so by directly reading that
offset in attach for some reason. It's the same address as
AR5K_EEPROM_MISC5, offset 0xc9. From the HAL:
> HAL_BOOL
> ar5212FillCapabilityInfo(struct ath_hal *ah)
> {
[...]
> HAL_CAPABILITIES *pCap = &ahpriv->ah_caps;
> u_int16_t capField;
> u_int16_t regcap;
>
> /* Read the capability EEPROM location */
> capField = 0;
> if (ahp->ah_eeversion >= AR_EEPROM_VER5_1 &&
> !ath_hal_eepromRead(ah, AR_EEPROM_CAPABILITIES_OFFSET, &capField)) {
> HDPRINTF(ah, HAL_DBG_EEPROM, "%s: unable to read caps from eeprom\n", __func__);
> return AH_FALSE;
> }
Ok, so it only works for eeprom 5.1 and better...
[...]
> pCap->halCipherAesCcmSupport =
> (!(capField & AR_EEPROM_EEPCAP_AES_DIS) &&
> ((AH_PRIVATE(ah)->ah_macVersion > AR_SREV_VERSION_VENICE) ||
> ((AH_PRIVATE(ah)->ah_macVersion == AR_SREV_VERSION_VENICE) &&
> (AH_PRIVATE(ah)->ah_macRev >= AR_SREV_VERSION_OAHU))));
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2008-11-21 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 14:16 [PATCH] ath5k: Clean up eeprom parsing and add missing calibration data Felix Fietkau
2008-11-21 3:00 ` Bob Copeland
2008-11-21 5:21 ` Nick Kossifidis
2008-11-21 14:05 ` Bob Copeland [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081121140508.GA26731@hash.localnet \
--to=me@bobcopeland.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mickflemm@gmail.com \
--cc=nbd@openwrt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).