[PATCH 23/29] ARM: orion5x: use DT to describe NOR on edmini_v2

Chris Moore moore at free.fr
Sun Apr 13 19:10:31 PDT 2014


Le 13/04/2014 17:45, Thomas Petazzoni a écrit :
> Dear Andrew Lunn,
> On Sun, 13 Apr 2014 17:31:50 +0200, Andrew Lunn wrote:
>>> -/*****************************************************************************
>>> - * 512KB NOR Flash on BOOT Device
>>> - ****************************************************************************/
>>> -
>>> -/*
>>> - * Currently the MTD code does not recognize the MX29LV400CBCT as a bottom
>>> - * -type device. This could cause risks of accidentally erasing critical
>>> - * flash sectors. We thus define a single, write-protected partition covering
>>> - * the whole flash.
>>> - * TODO: once the flash part TOP/BOTTOM detection issue is sorted out in the MTD
>>> - * code, break this into at least three partitions: 'u-boot code', 'u-boot
>>> - * environment' and 'whatever is left'.
>>> - */
>> Hi Thomas
>> Did you check if this is still true? If it is fixed, maybe now would
>> be a good time to swap to three partitions?
> I don't know, and since the NOR contains the bootloader, and I'm not
> sure those Orion devices support UART booting, I clearly don't want to
> play too much with NOR writing, as I don't want to brick the only two
> Orion platforms that I have. So I'd prefer to leave the functionality
> as it was, and leave it to other more adventurous and interested people
> the work on improving this.

I subsequently added a fixup todrivers 
to correct top/bottom detection for many Macronix devices including the 
(Commit 87e92c062b19eea6054532f8143a91242f104a6f see 

Like Thomas, I was afraid of bricking my device so I didn't dare to 
modify and test the partitioning.
(Unfortunately I don't have working JTAG.)


More information about the linux-arm-kernel mailing list