All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Gorski <jogo@openwrt.org>
To: b43-dev@lists.infradead.org
Subject: Extracting (boardvendor and) boardtype
Date: Tue, 19 Mar 2013 12:03:24 +0100	[thread overview]
Message-ID: <CAOiHx=ngEQtEiKgW16Ah7pTYqP269s183J-e8NxUpqiK29MQ1w@mail.gmail.com> (raw)
In-Reply-To: <CACna6rzmuA5=Vhj5CwSmMgg6=segiL6RDq0TCzxgXdGfvP62uA@mail.gmail.com>

On 19 March 2013 11:36, Rafa? Mi?ecki <zajec5@gmail.com> wrote:
> However take a look at siutils.c you're using internally at Broadcom.
> I've found it in:
> GPL_RT_AC66U_3004270/asuswrt/release/src-rt-6.x/shared/siutils.c
> This file contains si_nvram_process. This function calls that
> si_getdevpathintvar and getintvar I'm not sure about. Does
> si_nvram_process prefer SPROM's boardtype (offset SROM_SSID==0x2 or
> offset SSB_SPROM1_SPID==0x4) if it's available (not 0xFFFF)?

The getdevpathintvar and getintvar are for extracting these values
from nvram instead of SPROM - remember that embedded bcm47xx devices
are "sprom"-less and have these values stored in nvram. Since there is
only one global nvram, you need to prefix these values with the
"pci/sb" device path to differentiate if you have more than one wifi
chip (e.g. "sb/1/boardflags" or "pci/1/boardflags"). But this isn't
necessarily done for single wifi devices, hence the getdevpathintvar
-> getinvar path (as the fall back).

-- 
Jonas

  reply	other threads:[~2013-03-19 11:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19  9:48 Extracting (boardvendor and) boardtype Rafał Miłecki
2013-03-19 10:19 ` Arend van Spriel
2013-03-19 10:36   ` Rafał Miłecki
2013-03-19 11:03     ` Jonas Gorski [this message]
2013-03-19 11:18       ` Rafał Miłecki
2013-03-19 11:22         ` Arend van Spriel
2013-03-19 11:37           ` Rafał Miłecki
2013-03-19 11:45             ` Arend van Spriel
2013-03-19 11:47               ` Arend van Spriel
2013-03-19 11:52               ` Rafał Miłecki

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='CAOiHx=ngEQtEiKgW16Ah7pTYqP269s183J-e8NxUpqiK29MQ1w@mail.gmail.com' \
    --to=jogo@openwrt.org \
    --cc=b43-dev@lists.infradead.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.