b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linville@tuxdriver.com, zajec5@gmail.com,
	b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
	brcm80211-dev-list@broadcom.com
Subject: REGRESSION: [PATCH v2 0/9] bcma misc updates
Date: Tue, 17 Jul 2012 09:31:33 +0200	[thread overview]
Message-ID: <500514D5.4090207@broadcom.com> (raw)
In-Reply-To: <50048B39.7060507@hauke-m.de>

On 07/16/2012 11:44 PM, Hauke Mehrtens wrote:
> On 07/03/2012 10:22 AM, Arend van Spriel wrote:
>> On 07/03/2012 09:44 AM, Hauke Mehrtens wrote:
>>>> I suspect it tries reading OTP instead of the external SPROM.
>>>>>
>>>>> Gr. AvS
>>>>>
>>> Hi Arend,
>>>
>>> my BCM43224 uses a Sprom from the flash chip of the SoC, so it could be
>>> that something is wrong in the sprom reading, but I haven't touched the
>>> sprom code expect for using constants.
>>>
>>> Do you know which patch is causing this issue?
>>>
>>> Hauke
>>>
>>
>> I intended to bisect the series. I will let you know what I find.
>>
>> Gr. Av
> 
> Hi Arend,
> 
> Did you bisect this? I still have no idea which or why any of the
> patches could cause this.
> 
> Hauke
> 

Hi Hauke,

I seem to have a number of issues with BCMA, which all seem host_pci
related. It looks like there is some merge issue in PCI API. It may be
due to the fact that wireless-testing got rebased by John and I merged
it into our internal branch.

So my plan is to rebase our internal branch to wireless-testing instead
of a merge. I did not come back to you because I wanted to make sense of
the issues I was seeing.

Gr. AvS

      reply	other threads:[~2012-07-17  7:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 23:44 [PATCH v2 0/9] bcma misc updates Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 1/9] bcma: extend workaround for bcm4331 Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 2/9] bcma: add constants for chip ids Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 3/9] bcma: remove fix for 4329b0 bad LPOM is detection Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 4/9] bcma: add PCI ID for BCM43224 Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 5/9] bcma: complete workaround for BCMA43224 and BCM4313 Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 6/9] bcma: remove bcma_pmu_{pll,swreg}_init() Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 7/9] bcma: remove chip ids doing nothing from PMU initialization Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 8/9] bcma: add bcma_pmu_spuravoid_pllupdate() Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 9/9] bcma: add mdelay bcma_pmu_resources_init() Hauke Mehrtens
2012-06-30  9:19 ` [PATCH v2 0/9] bcma misc updates Rafał Miłecki
2012-07-03  6:51 ` REGRESSION: " Arend van Spriel
2012-07-03  7:44   ` Hauke Mehrtens
2012-07-03  8:22     ` Arend van Spriel
2012-07-16 21:44       ` Hauke Mehrtens
2012-07-17  7:31         ` Arend van Spriel [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=500514D5.4090207@broadcom.com \
    --to=arend@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=zajec5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).