[OpenWrt-Devel] Fwd: Re: [PATCH 10/10] brcmfmac: Add support for multiple PCIE devices in nvram.

Ian Kent raven at themaw.net
Mon Apr 20 21:42:34 EDT 2015

On Mon, 2015-04-20 at 19:28 +0200, Arend van Spriel wrote:
> On 04/20/15 13:50, Jonas Gorski wrote:
> > Hi,
> >
> > On Mon, Apr 20, 2015 at 1:29 PM, Rafał Miłecki<zajec5 at gmail.com>  wrote:
> >> On 20 April 2015 at 11:27, Arend van Spriel<arend at broadcom.com>  wrote:
> >>>> Following an "nvram erase" none of the needed<key, value>   pairs remain
> >>>> in nvram. So we probably can't use nvram in a reliable way to create the
> >>>> wireless configuration.
> >>>
> >>>
> >>> So why do "nvram erase"? The assumption that it is not needed because you
> >>> are running an OpenWRT image is wrong or at least only partially true, ie.
> >>> for the user-space settings.
> >>
> >> I agree with Arend. If you're are erasing sensitive wireless info from
> >> your device, expect problems. The same will happen if you'll overwrite
> >> standard Broadcom PCI device SPROM (which contains the same kind of
> >> data).
> >
> > At least on older bcm47xx/MIPS devices nvram was also used for (user
> > changable) configuration like lan ip address, and consequently erasing
> > nvram caused CFE to restore the default values, which should include
> > the right wifi configuration values. Several devices even do so when
> > holding down reset for a long time at power up*. Does this not happen
> > anymore with bcm53xx/ARM? Are user values now stored in a different
> > partition?
> Hi Jonas,
> I was hoping that the firmware specific wifi config would indeed be in a 
> separate MTD partition. However, Hante has been looking at the MTD 
> partitions and none match up with what CFE dumps upon 'nvram show'. So 
> we are going through our CFE code, but no clues (yet) whether R8000 
> specific changes have been made. There is also an spiflash device 
> configured in DT but the bcm53xxspiflash driver does not seem to be 
> working for it.

Yes, that's what I see too.
Last time I looked I got the impression the device used isn't known to
the kernel.

> Regards,
> Arend
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list