MIPS RELOCATABLE: [PATCH 14/20] RISC-V: erizo: migrate to PBL

[Ahmad Fatoum]

Hello,

On 15.03.21 13:08, Antony Pavlov wrote:
> On Mon, 15 Mar 2021 12:45:15 +0100
> Oleksij Rempel <o.rempel at pengutronix.de> wrote:
> 
>> On Mon, Mar 15, 2021 at 11:43:53AM +0300, Antony Pavlov wrote:
>>> On Sun, 14 Mar 2021 13:27:58 +0100
>>> Ahmad Fatoum <a.fatoum at pengutronix.de> wrote:
>>>
>>> Hi!
>>>
>>>> diff --git a/common/Kconfig b/common/Kconfig
>>>> index 36207274f07f..37204fb40a44 100644
>>>> --- a/common/Kconfig
>>>> +++ b/common/Kconfig
>>>> @@ -44,7 +44,7 @@ config BLOCK_WRITE
>>>>  
>>>>  config USE_COMPRESSED_DTB
>>>>  	bool
>>>> -	depends on ARM
>>>> +	depends on ARM || RISCV
>>>>  	select UNCOMPRESS
>>>>  	select LZO_DECOMPRESS
>>>>  
>>>> @@ -358,7 +358,7 @@ config KALLSYMS
>>>>  	  This is useful to print a nice backtrace when an exception occurs.
>>>>  
>>>>  config RELOCATABLE
>>>> -	depends on PPC || ARM
>>>> +	depends on PPC || ARM || RISCV
>>>>  	bool "generate relocatable barebox binary"
>>>>  	help
>>>>  	  A non relocatable barebox binary will run at it's compiled in
>>>
>>> Hmmm. AFAIR MIPS barebox is relocatable. Why CONFIG_RELOCATABLE does not depend on MIPS?
>>>
>> good point, I'll need to test it
> 
> At the first glance the only point to enable CONFIG_RELOCATABLE is to enable FS_PSTORE.

Without having dug into the MIPS code, the main point of CONFIG_RELOCATABLE
is that PBL can check for it to decide where to copy barebox proper to.

This is very relevant if there's no TEXT_BASE that works for all boards
that you need to support with your multi-image barebox.

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |