public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name dt property
Date: Wed, 29 Jun 2016 22:07:21 +0200	[thread overview]
Message-ID: <6119590.gPKNGsSJ3t@wuerfel> (raw)
In-Reply-To: <1467230078.2598.2.camel@plaes.org>

On Wednesday, June 29, 2016 10:54:38 PM CEST Priit Laes wrote:
> On Wed, 2016-06-29 at 21:33 +0200, Arnd Bergmann wrote:

> > What is the size of this nvram file? As it's board specific, I wonder
> > if we can simply include it inside of the DT verbatim. I remember
> > doing that (in the pre-dtb days, on real open firmware) for the
> > "spidernet"
> > ethernet driver.
> 
> It contains a bit too much info:
> 
> This is what CubieTruck requires:
> 
> http://dl.cubieboard.org/public/Cubieboard/benn/firmware/ap6210/nvram_a
> p6210.txt

Ah, I had not realized that this is a text based interface rather than
a small binary blob with fixed offsets.

On the other hand, each line in there could be translated easily into
a separate DT property, and some of them (manfid/prodid, macaddr, ...)
look like they directly correspond to properties we already have.

As Arend said there is also the option of having a chip specific
nvram file (brcmfmac43362-sdio.txt) as a fallback when there is no
more specific module. How many of the lines in your example would
actually differ between the two? Does this affect all of them, or
just a subset that could be turned into a smaller set of DT
properties?

	Arnd

  reply	other threads:[~2016-06-29 20:07 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 14:04 [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property Hans de Goede
2016-06-29 14:04 ` [PATCH 2/4] ARM: dts: sun7i-a20-cubietruck: Set brcm,nvram_file_name Hans de Goede
2016-06-29 17:01   ` [PATCH 2/4] ARM: dts: sun7i-a20-cubietruck: Set brcm, nvram_file_name Kalle Valo
2016-06-29 18:01     ` [linux-sunxi] Re: [PATCH 2/4] ARM: dts: sun7i-a20-cubietruck: Set brcm,nvram_file_name Hans de Goede
2016-06-29 14:04 ` [PATCH 3/4] ARM: dts: sun7i-a20-wits-pro-a20-dkt: Set brcm, nvram_file_name Hans de Goede
2016-06-29 14:04 ` [PATCH 4/4] ARM: dts: sun5i-a10s-auxtek-t004: " Hans de Goede
2016-06-29 14:42 ` [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property Jonas Gorski
2016-06-29 15:16   ` Hans de Goede
2016-06-29 17:00     ` Kalle Valo
2016-06-29 18:01       ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Hans de Goede
2016-06-29 18:51         ` Arend Van Spriel
2016-06-29 18:57           ` Arend Van Spriel
2016-06-30  8:50             ` Kalle Valo
2016-06-29 19:33           ` Arnd Bergmann
2016-06-29 19:54             ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Priit Laes
2016-06-29 20:07               ` Arnd Bergmann [this message]
2016-06-30  9:02               ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Kalle Valo
2016-06-30  9:50                 ` Hans de Goede
2016-06-30  9:58                   ` Kalle Valo
2016-06-30 10:04                     ` Hans de Goede
2016-06-30 10:18                       ` Jonas Gorski
2016-06-30 10:25                         ` Hans de Goede
2016-06-30 11:31                           ` Arnd Bergmann
2016-06-30 19:23                             ` Arend Van Spriel
2016-07-01  8:51                               ` Arnd Bergmann
2016-07-01  8:58                               ` Jonas Gorski
2016-07-02  6:59                                 ` Kalle Valo
2016-07-02 18:20                                 ` Arend Van Spriel
2016-07-02 21:30                                   ` Arnd Bergmann
2016-07-04  8:41                                     ` Arend Van Spriel
2016-07-04  8:55                                       ` Arnd Bergmann
2016-07-04  9:08                                         ` Arend Van Spriel
2016-07-04 14:54                                           ` Arnd Bergmann
2016-07-04 18:36                                             ` Arend van Spriel
2016-07-05 13:43                                               ` Arnd Bergmann
2016-07-06  8:08                                                 ` Arend Van Spriel
2016-07-06 13:42                                                   ` Arnd Bergmann
2016-07-06 19:19                                                     ` Arend Van Spriel
2016-07-07  8:46                                                       ` Arnd Bergmann
2016-07-07  9:16                                                         ` Arend Van Spriel
2016-07-07  9:24                                                           ` Arnd Bergmann
2016-07-17 21:45                                                         ` Rob Herring
2016-07-18  7:51                                                           ` Arend Van Spriel
2016-06-30  8:46           ` Kalle Valo
2016-06-30  9:49             ` Hans de Goede
2016-06-30  9:53           ` Hans de Goede
2016-07-01  2:08 ` [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Rob Herring
2016-07-01  8:17   ` Arend Van Spriel
2016-07-01  9:20     ` Arnd Bergmann
2016-07-04 16:12     ` Rob Herring

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=6119590.gPKNGsSJ3t@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox