linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Saul St. John" <saul.stjohn@gmail.com>,
	"Larry Finger" <Larry.Finger@lwfinger.net>
Subject: Re: [RFC] bcma: add support for on-chip OTP memory used for SPROM storage
Date: Mon, 5 Mar 2012 10:16:36 +0100	[thread overview]
Message-ID: <4F548474.10703@broadcom.com> (raw)
In-Reply-To: <CACna6rxDBh-4Yb182atxvXj+peyk2=5mJAMj7H0-wzeyEzwQ4Q@mail.gmail.com>

On 03/03/2012 11:44 PM, Rafał Miłecki wrote:
> 2012/2/28 Hauke Mehrtens<hauke@hauke-m.de>:
>> On 02/27/2012 11:12 AM, Arend van Spriel wrote:
>>>
>>> Appreciate any testing on SoCs. I think I will need some time to modify
>>> brcmsmac so let your patch go first.
>>
>> The sprom part of my SoC is working with this patch on top of my sprom
>> patches, but it uses the sprom from flash/nvram for both wifi devices
>> (one integrated in the bCM4716 and the other a BCM43224 connected to the
>> PCIe host controller of the BCM4716).
>> For my BCM4716 bcma_sprom_ext_available() and
>> bcma_sprom_onchip_available() are returning false and for the BCM43224
>> bcma_sprom_ext_available() is returning false and
>> bcma_sprom_onchip_offset() 0.
>
> I guess that's wrong...? So is there something wrong with the Arend's
> patch causing this regression? Or was this wrong even earlier?
>
> I'm not sure if I should test this patch against my cards or should I
> wait for V2.
>

Hi Rafał,

It is not wrong. I asked Hauke a question about his router regarding 
this. The story for routers is that sprom data for both cards resides in 
nvram/flash, ie. the fallback sprom source in Hauke's patch. Not sure 
why that bcma patch has not yet made it into wireless-next. Your cards 
are probably pci(e) cards so those should have sprom data on board.

Gr. AvS


  reply	other threads:[~2012-03-05  9:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 21:52 [RFC] bcma: add support for on-chip OTP memory used for SPROM storage Arend van Spriel
2012-02-24  2:42 ` Saul St. John
2012-02-24  9:55   ` Arend van Spriel
2012-02-24  7:52 ` Rafał Miłecki
2012-02-24 10:15   ` Arend van Spriel
2012-02-24 10:39   ` Arend van Spriel
2012-02-24 10:58     ` Johannes Berg
2012-02-24 11:18       ` Arend van Spriel
2012-02-25 12:52 ` Hauke Mehrtens
2012-02-25 14:29   ` Rafał Miłecki
2012-02-27 10:12   ` Arend van Spriel
2012-02-28 20:11     ` Hauke Mehrtens
2012-03-01 14:12       ` Arend van Spriel
2012-03-01 14:35         ` Hauke Mehrtens
2012-03-01 15:16           ` Arend van Spriel
2012-03-01 16:14             ` Hauke Mehrtens
2012-03-03 22:44       ` Rafał Miłecki
2012-03-05  9:16         ` Arend van Spriel [this message]
2012-03-06  8:52           ` Rafał Miłecki
2012-03-06 12:26             ` Arend van Spriel
2012-03-01 21:26     ` Arend van Spriel
2012-03-01 21:42       ` Larry Finger
2012-03-01 21:56       ` Hauke Mehrtens
2012-03-02 10:39         ` Arend van Spriel

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=4F548474.10703@broadcom.com \
    --to=arend@broadcom.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=saul.stjohn@gmail.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).