From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Michael Buesch <mb@bu3sch.de>, Nathan Schulte <reklipz@gmail.com>,
bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!
Date: Wed, 03 Mar 2010 19:32:38 -0600 [thread overview]
Message-ID: <4B8F0DB6.5090209@lwfinger.net> (raw)
In-Reply-To: <69e28c911003031647o23cf5638xb0d29fb1b73aee64@mail.gmail.com>
On 03/03/2010 06:47 PM, Gábor Stefanik wrote:
> On Thu, Mar 4, 2010 at 1:30 AM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>> On 03/02/2010 03:57 PM, Michael Buesch wrote:
>>
>>> A bug in the PCI-E core code is able to show such behavior, because all memory
>>> transfers (MMIO and DMA) from the PCI device to the wireless core are translated
>>> by the PCI-E core.
>>> I think the whole PCI-E core code has to be audited (also the specs, probably).
>>
>> I have nearly finished the update on the code section of the specs page at
>> http://bcm-v4.sipsolutions.net/PCI-E. The part that is not done involves the
>> sections that read an address from the SPROM and perform operations on that address.
>>
>> I found that the chip common registers
>
> Do you mean the ChipCommon registers or the Backplane common registers?
Definitely, it is the chipcommon registers.
prev parent reply other threads:[~2010-03-04 1:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <69e28c911002260708g45d3c0f7u6abf13b1babe549f@mail.gmail.com>
[not found] ` <201002271620.31410.mb@bu3sch.de>
[not found] ` <201002271708.29817.mb@bu3sch.de>
[not found] ` <4B894A61.1070302@lwfinger.net>
[not found] ` <69e28c911002271145s590df31en9d2f8b2c47932451@mail.gmail.com>
[not found] ` <4B899DA3.4030100@lwfinger.net>
[not found] ` <69e28c911002271534o8cab111vf7fcc1b93b6c4b47@mail.gmail.com>
[not found] ` <a221c0101002271542o5d928e56n8a22602860aeb761@mail.gmail.com>
[not found] ` <69e28c911002271544y62c93255k8a6dbb0adb2b5928@mail.gmail.com>
[not found] ` <20100228001655.4c9fd9ce@boulder.homenet>
[not found] ` <4B8AAF42.8000602@polymtl.ca>
2010-02-28 18:42 ` LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??! Gábor Stefanik
2010-02-28 18:47 ` Rafał Miłecki
2010-02-28 18:52 ` Gábor Stefanik
2010-02-28 18:58 ` Michael Buesch
2010-02-28 20:30 ` Chris Vine
2010-02-28 20:33 ` Michael Buesch
2010-02-28 20:51 ` William Bourque
2010-02-28 20:54 ` Chris Vine
2010-02-28 19:44 ` William Bourque
2010-02-28 20:03 ` Chris Vine
[not found] ` <a221c0101002271703p3f344ec4t78d5c8b77c6d1290@mail.gmail.com>
[not found] ` <a221c0101002271828ye265d72y774320c08a4a15da@mail.gmail.com>
[not found] ` <69e28c911002280814v56f2f553x847c8bae94e6aaab@mail.gmail.com>
2010-02-28 22:19 ` Nathan Schulte
2010-02-28 23:03 ` Gábor Stefanik
2010-02-28 23:38 ` Nathan Schulte
2010-03-01 0:22 ` Michael Buesch
2010-03-02 21:57 ` Michael Buesch
2010-03-02 22:11 ` Larry Finger
2010-03-02 22:25 ` William Bourque
2010-03-02 22:29 ` Michael Buesch
2010-03-02 22:50 ` William Bourque
2010-03-04 0:30 ` Larry Finger
2010-03-04 0:47 ` Gábor Stefanik
2010-03-04 1:32 ` Larry Finger [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=4B8F0DB6.5090209@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netrolller.3d@gmail.com \
--cc=reklipz@gmail.com \
--cc=torvalds@linux-foundation.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.