# Re: \[linux-sunxi\] Re: \[PATCH 1/4\] brcmfmac: Add brcm,nvram\_file\_name dt property

- From: Hans de Goede \<hidden\>
- Date: 2016-06-30 09:50:01 
- List: linux-wireless
- Page: https://ratatoskr.run/linux-wireless/2016/06/8124833
- Thread: https://ratatoskr.run/linux-arm-kernel/2016/06/8124833/t.md

```text
Hi,

On 30-06-16 11:02, Kalle Valo wrote:
> Priit Laes [ref] writes:
>
>>> 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_ap6210.txt
>
> In the nvram file I see lots of identifiers:
>
> manfid=0x2d0
> prodid=0x492
> vendid=0x14e4
> devid=0x4343
> boardtype=0x0598
> boardrev=0x1307
> boardnum=777
>
> Are any of these (or a combination of them) unique for each board type?
> What if one of these is provided through DT and then the driver could
> choose the nvram file based on the board id? Just another idea...

That would require updating a table in the driver every time a new
board comes out, I do not believe that that is a good solution.

Regards,

Hans
```
