All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: low throughputs with 14e4:4353
Date: Wed, 07 Dec 2011 15:26:42 -0600	[thread overview]
Message-ID: <4EDFDA12.8080303@lwfinger.net> (raw)
In-Reply-To: <CACna6rwPEYiZCq+4Di_4xQBF-rQQNw5gVTMkunm2mqoUVBP1Tw@mail.gmail.com>

On 12/07/2011 06:01 AM, Rafa? Mi?ecki wrote:
> W dniu 5 grudnia 2011 21:39 u?ytkownik Rafa? Mi?ecki<zajec5@gmail.com>  napisa?:
>> W dniu 29 listopada 2011 22:36 u?ytkownik Rafa? Mi?ecki
>> <zajec5@gmail.com>  napisa?:
>>> I'll give it a rest and will try in next days again.
>>
>> It really seems it's something spur avoidance related (and so most
>> probably CC PLL related). After applying my patch implementing SPUR
>> avoidance, card stops receiving anything. I'll dig more around it.
>
> I've found bug in my implementation and fixed it. Today evening I'll
> test if my patch fixes performance anyhow (I need physical access).
>
> Larry: I've found two mistakes/lacks in the specs.
> 1) http://bcm-v4.sipsolutions.net/802.11/PmuSpurAvoid
> This routine ignores my BCM43224. However from wl MMIO dump I can see
> it should make some ops on my chip. Example log from wl:
> write32 0xfaaff660<- 0x00000000
> write32 0xfaaff664<- 0x11100010
> write32 0xfaaff660<- 0x00000001
> write32 0xfaaff664<- 0x000c0c06
> write32 0xfaaff660<- 0x00000002
> write32 0xfaaff664<- 0x03000a08
> write32 0xfaaff660<- 0x00000003
> write32 0xfaaff664<- 0x00000000
> write32 0xfaaff660<- 0x00000004
> write32 0xfaaff664<- 0x200005c0
> write32 0xfaaff660<- 0x00000005
> write32 0xfaaff664<- 0x88888815
>   read32 0xfaaff600 ->  0x00000381
> write32 0xfaaff600<- 0x00000781
>
> 2) http://bcm-v4.sipsolutions.net/802.11/PHY/N/ChanspecSetup
> There is condition: "If the chip is greater than 0x4349 and less then 0x4356".
> This should but applied "too"/"instead" for BCM43224 at least. wl
> executes that commands for my BCM43224:
> write16 0xfaafc62e<- 0x8889
> write16 0xfaafc630<- 0x0008

Both places should have used chip ID of 43224 and 43225 (at least). The second 
also needs 43222 and probably 43228 (I'm still checking that.) The first may 
also need 43222 and 43228.

Larry

  reply	other threads:[~2011-12-07 21:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 19:28 low throughputs with 14e4:4353 francesco.gringoli at ing.unibs.it
2011-11-29 20:08 ` Rafał Miłecki
2011-11-29 21:36   ` Rafał Miłecki
2011-11-30 15:05     ` francesco.gringoli at ing.unibs.it
2011-11-30 21:27       ` Larry Finger
2011-12-01 19:01         ` francesco.gringoli at ing.unibs.it
2011-12-02 18:14         ` francesco.gringoli at ing.unibs.it
2011-12-05 20:39     ` Rafał Miłecki
2011-12-06  8:23       ` francesco.gringoli at ing.unibs.it
2011-12-07 12:01       ` Rafał Miłecki
2011-12-07 21:26         ` Larry Finger [this message]
2011-12-08  9:21         ` francesco.gringoli at ing.unibs.it
2011-12-08  9:34           ` Rafał Miłecki
2011-12-08 11:06             ` francesco.gringoli at ing.unibs.it
2011-12-10 10:17             ` francesco.gringoli at ing.unibs.it
2011-12-14 17:02             ` francesco.gringoli at ing.unibs.it
2011-12-14 18:04               ` Rafał Miłecki
2011-12-15 18:11                 ` francesco.gringoli at ing.unibs.it

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=4EDFDA12.8080303@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.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.