From: Gabor Juhos <juhosg@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] eeprom txGainType overridden if minor version < 19
Date: Tue, 02 Aug 2011 18:11:26 +0200 [thread overview]
Message-ID: <4E3821AE.7050902@openwrt.org> (raw)
In-Reply-To: <CAD2nsn2NgU=JbkMj3dtXGEkVqPwMJoB+T1LzMSLSORbPRVExtQ@mail.gmail.com>
2011.08.02. 17:37 keltez?ssel, Mohammed Shafi ?rta:
> On Tue, Aug 2, 2011 at 8:36 PM, Mohammed Shafi <shafi.wireless@gmail.com> wrote:
>> On Tue, Aug 2, 2011 at 8:07 PM, Marek Lindner <lindner_marek@yahoo.de> wrote:
>>> On Tuesday, August 02, 2011 13:13:27 Adrian Chadd wrote:
>>>> Right, so it's an embedded board inside a wireless router? Which router? :)
>>>
>>> The OM2P but how is this going to help ? I have the feeling we are not getting
>>> closer to answer my question: Why does ath9k_hw_4k_get_eeprom() requires the
>>> minor version 19 or above before even considering to read the eeprom value ?
>>> Can I propose a patch that removes that check ? I already have that patch
>>> working for me - just wanted to be sure it does no harm.
>>
>> hi,
>>
>> yes, looks like the check should not be there for common, but I don't
>> know for what reason the developer made it as a common check. let me
>> check it out. please wait. does any one has any comments. can you
>> please share what is the issue you are issuing
>
>
> adding the people who made those changes, I am also unable to
> understand. verified with the internal code base, the check was not
> there.
I had no access to the internal code base when I have added that code, so i was
unable to verify that the version check is required or not for the 4K EEPROMs.
To be on the safe side, I have used the same check which was present in the
generic eeprom code.
-Gabor
next prev parent reply other threads:[~2011-08-02 16:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 8:28 [ath9k-devel] eeprom txGainType overridden if minor version < 19 Marek Lindner
2011-08-02 8:59 ` Adrian Chadd
2011-08-02 9:03 ` Marek Lindner
2011-08-02 10:38 ` Adrian Chadd
2011-08-02 10:48 ` Marek Lindner
2011-08-02 11:13 ` Adrian Chadd
2011-08-02 14:37 ` Marek Lindner
2011-08-02 15:06 ` Mohammed Shafi
2011-08-02 15:37 ` Mohammed Shafi
2011-08-02 16:11 ` Gabor Juhos [this message]
2011-08-03 4:59 ` Mohammed Shafi
2011-08-03 6:48 ` Adrian Chadd
2011-08-03 7:03 ` Marek Lindner
2011-08-03 7:10 ` Mohammed Shafi
2011-08-02 16:29 ` Adrian Chadd
2011-08-02 10:09 ` Mohammed Shafi
2011-08-02 10:15 ` Marek Lindner
2011-08-02 10:36 ` Mohammed Shafi
2011-08-02 10:49 ` Marek Lindner
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=4E3821AE.7050902@openwrt.org \
--to=juhosg@openwrt.org \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.