From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Problem with understanding DMA on some machines (known solution!), specs needed?
Date: Mon, 25 Jul 2011 20:07:48 -0500 [thread overview]
Message-ID: <4E2E1364.6070206@lwfinger.net> (raw)
In-Reply-To: <CACna6ryccJvwj6daQ=LkXyxDqZLmZCZOHmx-JCGMNwegBaHc=w@mail.gmail.com>
On 07/25/2011 05:40 PM, Rafa? Mi?ecki wrote:
> W dniu 25 lipca 2011 23:54 u?ytkownik Rafa? Mi?ecki<zajec5@gmail.com> napisa?:
>> Hey, I've finally came back to my 14e4:4329 with not working DMA. I
>> hoped disabling parity will make my DMA work, but this didn't do the
>> trick.
>>
>> The card is PCI one with following params:
>> SSB 2.4
>> BCM4321
>> SPROM: 4
>> PMU: ?
>> Core rev: 11
>> PHY: N / 1
>> Radio: 0x2055 / 4
>
> Some additional details. This is card taken out from Asus WL-500W and
> sent to me by Patryk, some Polish Asus owner.
>
> I've put this in my extremely old Acer based on x86_64 CPU, however
> running x86 compiled system.
The reference driver does what we do. It reads SSB_TMSHIGH to see if
SSB_TMSHIGH_DMA64 is set. In addition, I do not see any place for a fallback
mechanism such as we have in b43_dma_set_mask(). That might be a good place to
put in the quirk for 14e4:4329.
Larry
next prev parent reply other threads:[~2011-07-26 1:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 21:54 Problem with understanding DMA on some machines (known solution!), specs needed? Rafał Miłecki
2011-07-25 22:40 ` Rafał Miłecki
2011-07-26 1:07 ` Larry Finger [this message]
2011-07-26 0:35 ` Larry Finger
2011-07-26 7:20 ` Rafał Miłecki
2011-07-26 7:24 ` Rafał Miłecki
2011-07-26 8:24 ` Rafał Miłecki
2011-07-26 15:33 ` Larry Finger
2011-07-26 15:49 ` Michael Büsch
2011-07-26 16:30 ` Rafał Miłecki
2011-07-26 16:32 ` Rafał Miłecki
2011-07-26 17:10 ` Larry Finger
2011-07-26 18:55 ` Michael Büsch
2011-07-30 16:44 ` Michael Büsch
2011-07-30 23:48 ` Rafał Miłecki
2011-07-31 5:54 ` Michael Büsch
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=4E2E1364.6070206@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.