All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Arend Van Spriel <arend@broadcom.com>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
	"Saul St. John" <saul.stjohn@gmail.com>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] use alternate SPROM offset for 43224
Date: Sun, 19 Feb 2012 16:37:13 +0100	[thread overview]
Message-ID: <4F411729.5070705@hauke-m.de> (raw)
In-Reply-To: <400C43189542CE41BC0A5B252FC90136BC8414D128@SJEXCHCCR02.corp.ad.broadcom.com>

On 02/14/2012 11:39 PM, Arend Van Spriel wrote:
>> Sent: dinsdag 14 februari 2012 23:04
>>
>> On 02/14/2012 02:20 PM, Hauke Mehrtens wrote:
>>>>>  I think it is more complicated than the above. On my 43224, I get
>> the
>>>>>  message "No SPROM available", which arises because
>> bcma_sprom_get() is
>>>>>  returning -ENOENT. The reason is that the value tested in "if
>>>>>  (!(sromctrl&  BCMA_CC_SROM_CONTROL_PRESENT))" is zero. The
>> contents of
>>>>>  sromctl are 0x12, and the mask is 1.
>>> This check is the main part of ai_is_sprom_available() in brcmsmac.
>> If
>>> this check fails, like in your case, brcmsmac tries otp_read_pci() to
>>> read out the sprom, which is not implemented in bcma.
>>
>> I will try implementing a similar routine in bcma.
>>
> 
> I started adding proper OTP support in BCMA, but I am currently working on async firmware loading feature. Different chipsets can either have an external SPROM or on-chip OTP. Some have both, but only one holds the data.
> 
> Gr. AvS
Nice to hear you are working on OTP support in bcma. In that process,
are you also working on making brcmsmac using the sprom provided by bcma?

Hauke


  reply	other threads:[~2012-02-19 15:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14  4:01 [RFC] use alternate SPROM offset for 43224 Saul St. John
2012-02-14 10:07 ` Arend Van Spriel
2012-02-14 13:35   ` Rafał Miłecki
2012-02-14 13:34 ` Rafał Miłecki
2012-02-14 16:22   ` Saul St. John
2012-02-14 17:29     ` Rafał Miłecki
2012-02-14 18:33       ` Hauke Mehrtens
2012-02-14 18:52       ` Saul St. John
2012-02-14 20:10         ` Larry Finger
2012-02-14 20:20           ` Hauke Mehrtens
2012-02-14 22:04             ` Larry Finger
2012-02-14 22:39               ` Arend Van Spriel
2012-02-19 15:37                 ` Hauke Mehrtens [this message]
2012-02-20  9:20                   ` 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=4F411729.5070705@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=arend@broadcom.com \
    --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 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.