Re: [RFC 2/7] bcm47xx-nvram: add new broadcom nvram driver with dt support

On 24 August 2014 23:24, Hauke Mehrtens [off-list ref] wrote:

+On NorthStar ARM SoCs the NAND flash is available at 0x1c000000 and the
+NOR flash is at 0x1e000000
+
+Example:
+
+nvram0: nvram@0 {
+       compatible = "brcm,bcm47xx-nvram";
+       reg = <0x1c000000 0x01000000>;
+};

Could we avoid that? Type of flash can easily be checked in the code.
All we need to do is to read BCMA_IOST register of BCMA_CORE_NS_ROM
core.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

On 08/26/2014 10:54 PM, Rafał Miłecki wrote:

On 24 August 2014 23:24, Hauke Mehrtens [off-list ref] wrote:

quoted

+On NorthStar ARM SoCs the NAND flash is available at 0x1c000000 and the
+NOR flash is at 0x1e000000
+
+Example:
+
+nvram0: nvram@0 {
+       compatible = "brcm,bcm47xx-nvram";
+       reg = <0x1c000000 0x01000000>;
+};

Could we avoid that? Type of flash can easily be checked in the code.
All we need to do is to read BCMA_IOST register of BCMA_CORE_NS_ROM
core.

So there is a boot status register you can read to tell what type of
flash you booted from, but does that also give you the resource ranges
for these type of flashes? Presumably they will be mapped into different
addresses (at least bcm63xx is like that), that information needs to be
listed somewhere.
--
Florian