On Monday 01 September 2014 22:45:25 Jonas Gorski wrote: > 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. Is this also the case on ARM? According to the documented boot protocol, ARM systems are supposed to pass the command line either through the ATAGS interface or through a DT, and we have code to move it from the former into the latter one. Of course it wouldn't be the first system that ignores the boot protocol, but it has fortunately become rather rare these days. > 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. Can you have two systems that can use the same DTB with the exception of the clock rate? This sounds no different than on any other system that has a variable clock input. Arnd -- 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
