On Mon, Sep 1, 2014 at 4:57 PM, Arnd Bergmann <arnd@xxxxxxxx> wrote: > On Monday 01 September 2014 09:48:48 Rafał Miłecki wrote: >> On 31 August 2014 11:20, Rafał Miłecki <zajec5@xxxxxxxxx> wrote: >> So I think we'll need to change our vision of flash access in >> bcm74xx_nvram driver. I guess we will have to: >> 1) Register NAND core early >> 2) Initialize NAND driver >> 3) Use mtd/nand API in bcm47xx_nvram > > This would mean it's available really late. Is that a problem? That's probably mostly fine (for MIPS), except for two places: a) the kernel command line is stored in nvram, and used for finding out the correct console tty. b) on one specific chip, the configured system clock rate needs to be read out from nvram. Both can be also done through DT, but b) is somewhat important to do right, as it will cause the time running fast/slow if the value is wrong. > A possible solution for this would be to use the boot wrapper > I mentioned earlier, to put all the data from nvram into DT > properties before the kernel gets started. That sounds like quite a bit of effort, and a bit over-engineered for just 2.5 platforms. Jonas -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
