Re: [PATCH][RFC] MIPS: BCM47XX: Use mtd as an alternative way/API to get NVRAM content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3 September 2014 22:13, Hauke Mehrtens <hauke@xxxxxxxxxx> wrote:
> On 09/03/2014 07:14 PM, Rafał Miłecki wrote:
>> NVRAM can be read using magic memory offset, but after all it's just a
>> flash partition. On platforms where NVRAM isn't needed early we can get
>> it using mtd subsystem.
>
> Where would this work?
>
> Do you plan the following initialization order in bcma on arm and mips?
>
> 1. bcma SoC version
> 2. bcma bus scan
> 3. flash driver registration
> 4. nvram read
> 5. sprom generation from nvram and attaching to bcma
> 6. registration of the other bcam cores (wifi, ...)
>
> The nvram is memory mapped on every SoC, just on devices with nand flash
> booting we would need something to check for bad blocks.

The order you noted is probably quite accurate.

Indeed, I want to use "mtd" subsystem because of NAND. Mapping NAND
flash content to the memory is nice, but it's reliable for few first
sections/blocks only. The rest of flash may contain bad blocks and we
should read it being aware of that.


[Index of Archives]     [Linux MIPS Home]     [LKML Archive]     [Linux ARM Kernel]     [Linux ARM]     [Linux]     [Git]     [Yosemite News]     [Linux SCSI]     [Linux Hams]

  Powered by Linux