From: Chris Vine <chris@cvine.freeserve.co.uk>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: b43-dev <b43-dev@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: [RFT] BCM4312 users with DMA errors, please test!
Date: Mon, 16 Aug 2010 20:41:54 +0100 [thread overview]
Message-ID: <20100816204154.5100b604@boulder.homenet> (raw)
In-Reply-To: <AANLkTimMhW7OX3DT7A3EDNaOnr577KmTv5w9C_mz19TG@mail.gmail.com>
On Mon, 16 Aug 2010 19:59:36 +0200
G?bor Stefanik <netrolller.3d@gmail.com> wrote:
> Hello Everyone!
>
> If you are experiencing DMA errors on a BCM4312, please test the
> attached patch. It implements the PCI-E SERDES workaround, which the
> hybrid driver is applying during early init to LP-PHY cards, and which
> is a good candidate for the cause of the DMA error.
> Note that this is not a final patch & it may cause collateral damage
> for non-4312 cards; if it helps the 4312 problem, I will submit a
> cleaned-up version.
This applies to 2.6.35.2, but does not compile:
drivers/ssb/driver_pcicore.c: In function 'ssb_pcie_mdio_set_block':
drivers/ssb/driver_pcicore.c:457: error: 'i' undeclared (first use in
this function) drivers/ssb/driver_pcicore.c:457: error: (Each
undeclared identifier is reported only once
drivers/ssb/driver_pcicore.c:457: error: for each function it appears
in.) drivers/ssb/driver_pcicore.c: In function 'ssb_pcie_mdio_read':
drivers/ssb/driver_pcicore.c:503: error: expected ';' before
'pcicore_write32'
With the obvious fixes (providing a variable 'i' of int type as the
count variable and terminating the line which had no terminating
semi-colon), it compiled OK and the first time I booted up, booted up
OK but didn't fix the DMA error. Subsequent attempts to boot up gave me
a slew of errors on boot up so I am not sure what is going on there.
You might want to check that the obvious fixes to the patch are
complete.
Chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Vine <chris@cvine.freeserve.co.uk>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: b43-dev <b43-dev@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFT] BCM4312 users with DMA errors, please test!
Date: Mon, 16 Aug 2010 20:41:54 +0100 [thread overview]
Message-ID: <20100816204154.5100b604@boulder.homenet> (raw)
In-Reply-To: <AANLkTimMhW7OX3DT7A3EDNaOnr577KmTv5w9C_mz19TG@mail.gmail.com>
On Mon, 16 Aug 2010 19:59:36 +0200
Gábor Stefanik <netrolller.3d@gmail.com> wrote:
> Hello Everyone!
>
> If you are experiencing DMA errors on a BCM4312, please test the
> attached patch. It implements the PCI-E SERDES workaround, which the
> hybrid driver is applying during early init to LP-PHY cards, and which
> is a good candidate for the cause of the DMA error.
> Note that this is not a final patch & it may cause collateral damage
> for non-4312 cards; if it helps the 4312 problem, I will submit a
> cleaned-up version.
This applies to 2.6.35.2, but does not compile:
drivers/ssb/driver_pcicore.c: In function 'ssb_pcie_mdio_set_block':
drivers/ssb/driver_pcicore.c:457: error: 'i' undeclared (first use in
this function) drivers/ssb/driver_pcicore.c:457: error: (Each
undeclared identifier is reported only once
drivers/ssb/driver_pcicore.c:457: error: for each function it appears
in.) drivers/ssb/driver_pcicore.c: In function 'ssb_pcie_mdio_read':
drivers/ssb/driver_pcicore.c:503: error: expected ';' before
'pcicore_write32'
With the obvious fixes (providing a variable 'i' of int type as the
count variable and terminating the line which had no terminating
semi-colon), it compiled OK and the first time I booted up, booted up
OK but didn't fix the DMA error. Subsequent attempts to boot up gave me
a slew of errors on boot up so I am not sure what is going on there.
You might want to check that the obvious fixes to the patch are
complete.
Chris
next prev parent reply other threads:[~2010-08-16 19:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 17:59 [RFT] BCM4312 users with DMA errors, please test! Gábor Stefanik
2010-08-16 17:59 ` Gábor Stefanik
[not found] ` <AANLkTin0R6k0_GoSEN8aJ8t_fTJw9h_N_0etcxAokv6N@mail.gmail.com>
2010-08-16 18:15 ` Gábor Stefanik
2010-08-16 18:15 ` Gábor Stefanik
[not found] ` <AANLkTinkx+FjrAR48dziDR2kX48JRcjm3SF7jhhi4_oM@mail.gmail.com>
2010-08-16 18:45 ` Gábor Stefanik
2010-08-16 18:45 ` Gábor Stefanik
2010-08-17 15:49 ` Arthur Moreira
2010-08-16 19:06 ` Larry Finger
2010-08-16 19:06 ` Larry Finger
2010-08-16 19:16 ` Gábor Stefanik
2010-08-16 19:16 ` Gábor Stefanik
2010-08-16 19:30 ` Larry Finger
2010-08-16 19:30 ` Larry Finger
2010-08-16 19:32 ` Gábor Stefanik
2010-08-16 19:32 ` Gábor Stefanik
2010-08-16 19:41 ` Chris Vine [this message]
2010-08-16 19:41 ` Chris Vine
2010-08-16 22:35 ` Chris Vine
2010-08-16 22:35 ` Chris Vine
2010-08-16 23:53 ` Larry Finger
2010-08-16 23:53 ` Larry Finger
2010-08-17 0:09 ` Chris Vine
2010-08-17 0:09 ` Chris Vine
2010-08-17 0:10 ` Chris Vine
2010-08-17 0:10 ` Chris Vine
2010-08-17 0:14 ` Chris Vine
2010-08-17 0:14 ` Chris Vine
2010-08-17 1:01 ` Larry Finger
2010-08-17 1:01 ` Larry Finger
2010-08-17 12:23 ` Chris Vine
2010-08-17 12:23 ` Chris Vine
2010-08-17 20:28 ` Chris Vine
2010-08-17 20:28 ` Chris Vine
2010-08-17 20:38 ` Gábor Stefanik
2010-08-17 20:38 ` Gábor Stefanik
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=20100816204154.5100b604@boulder.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
/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.