From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9220: how do I wake it up? :)
Date: Fri, 21 Jan 2011 12:53:36 -0500 [thread overview]
Message-ID: <4D39C820.7020603@gnu.org> (raw)
In-Reply-To: <AANLkTi=efj-kEW7o5-uGmMaMrkeupe=xcP9foCGTMqYa@mail.gmail.com>
On 01/21/2011 12:09 PM, Adrian Chadd wrote:
> For posterity, it turns out to be the AR_AN_TOP2 patch.
>
> Found here:
>
> https://patchwork.kernel.org/patch/90926/
>
> Would someone mind letting me know what this particular fix does and
> why it's needed?
There is a lot of data written to the chip. Most of it is the same for
the same chip revision, but some bits need to be different based on the
EEPROM contents or on whether the device is connected to PCIe or PCI bus.
I don't know much about the meaning of that bit. My patch only changes
the way the fixup is applied. Instead of modifying the common table
that is shares between all devices, the bit is changed when the data is
written to the register. This allows peaceful coexistence of the
devices with different EEPROM in the same system.
My patch also was a step towards declaring the init tables constant, but
there is another fixup for AR9160 that is harder to fix. I never had
time to do the later.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2011-01-21 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 16:53 [ath9k-devel] AR9220: how do I wake it up? :) Adrian Chadd
2011-01-21 17:09 ` Adrian Chadd
2011-01-21 17:14 ` Adrian Chadd
2011-01-21 17:53 ` Pavel Roskin [this message]
2011-01-22 12:28 ` Adrian Chadd
2011-01-23 1:05 ` Pavel Roskin
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=4D39C820.7020603@gnu.org \
--to=proski@gnu.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.