On 08/08/18 01:10, Alexander Graf wrote:
> On 07.08.18 09:26, Kristian Amlie wrote:
>> What I want out of this exercise is to make sure that the EFI path in
>> distro_bootcmd will be able to boot an EFI app on any board, regardless
>> of whether it uses kernel_addr_r or loadaddr. Sounds reasonable,
On 07.08.18 09:26, Kristian Amlie wrote:
> On 07/08/18 00:06, Alexander Graf wrote:
>> On 06.08.18 13:00, Kristian Amlie wrote:
>>> Ping. Any objections to this change?
>>
>> I definitely don't want to have the bootefi path behave any different
>> from the other distro boot targets. That would ju
On 07/08/18 00:06, Alexander Graf wrote:
> On 06.08.18 13:00, Kristian Amlie wrote:
>> Ping. Any objections to this change?
>
> I definitely don't want to have the bootefi path behave any different
> from the other distro boot targets. That would just cause confusion down
> the road.
>
> Do they
On 06.08.18 13:00, Kristian Amlie wrote:
> Ping. Any objections to this change?
I definitely don't want to have the bootefi path behave any different
from the other distro boot targets. That would just cause confusion down
the road.
Do they (pxe boot, extlinux, etc) make use of loadaddr?
Than
Ping. Any objections to this change?
--
Kristian
On 10/07/18 15:29, Kristian Amlie wrote:
> loadaddr is configurable in Kconfig using CONFIG_LOADADDR, while
> kernel_addr_r is not. Hence, loadaddr is the future. Provide the
> existing kernel_addr_r as a fallback if loadaddr is not set.
>
> Sign
loadaddr is configurable in Kconfig using CONFIG_LOADADDR, while
kernel_addr_r is not. Hence, loadaddr is the future. Provide the
existing kernel_addr_r as a fallback if loadaddr is not set.
Signed-off-by: Kristian Amlie
---
include/config_distro_bootcmd.h | 18 --
1 file changed
6 matches
Mail list logo
