On Sun, 4 Sept 2022 at 12:23, Sergei Antonov saproj@gmail.com wrote:
On Sat, 3 Sept 2022 at 19:16, Tom Rini trini@konsulko.com wrote:
On Sat, Sep 03, 2022 at 05:49:50PM +0300, Sergei Antonov wrote:
On Sat, 3 Sept 2022 at 17:31, Tom Rini trini@konsulko.com wrote:
On Sat, Sep 03, 2022 at 05:30:30PM +0300, Sergei Antonov wrote:
CONFIG_SYS_FLASH_AUTOPROTECT_LIST is a feature of drivers/mtd/cfi_flash.c driver. It allows to specify a range of protected eraseblocks on flash memory.
Fixes build error: Error: You must add new CONFIG options using Kconfig The following new ad-hoc CONFIG options were detected: CONFIG_SYS_FLASH_AUTOPROTECT_LIST
Signed-off-by: Sergei Antonov saproj@gmail.com
scripts/config_whitelist.txt | 1 + 1 file changed, 1 insertion(+)
Please move this to Kconfig so that it can be enabled, thanks.
What type must it be in Kconfig? Note, it is an array initializer similar to CONFIG_SYS_BAUDRATE_TABLE.
Ah, ugh. So, it's also currently unused code, what does it look like in the platform you're making use of this on?
In my _defconfig I use this line: CONFIG_SYS_FLASH_AUTOPROTECT_LIST="{{0x80000000, 0x40000}}" To protect the first 256 KB of flash memory.
Please, disregard the previous message. I was too hasty to reply.
I have include/configs/myplatform.h file which contains this line: #define CONFIG_SYS_FLASH_AUTOPROTECT_LIST {{0x80000000, 0x40000}}
And I could not convert it to Kconfig string parameter.