On 13.04.16 20:54, Andreas Färber wrote:
> Am 13.04.2016 um 20:47 schrieb Alexander Graf:
>> load mmc 0 $fdt_addr_r my_awesome.dtb ;\
>> load mmc 0 $kernel_addr_r some/random/path/grub2.efi ;\
>> bootefi $kernel_addr_r
>
> If we're going in that direction, I would rather pass $fdt_addr_r a
Am 13.04.2016 um 20:47 schrieb Alexander Graf:
> load mmc 0 $fdt_addr_r my_awesome.dtb ;\
> load mmc 0 $kernel_addr_r some/random/path/grub2.efi ;\
> bootefi $kernel_addr_r
If we're going in that direction, I would rather pass $fdt_addr_r as
second optional argument to bootefi. That would be
On 13.04.16 20:31, Stephen Warren wrote:
> On 04/13/2016 12:24 PM, Alexander Graf wrote:
>>
>>
>>> If by some chance U-Boot is configured by DTB and that DTB is fully
>>> suitable to pass to the Linux kernel, then the board-specific code can
>>> arrange for ${kernel_addr_r} to point at that same
On 04/13/2016 12:24 PM, Alexander Graf wrote:
On 13.04.16 19:54, Stephen Warren wrote:
I've spotted a couple of problems in 74522c898b35 "efi_loader: Add
distro boot script for removable media". These help explain something I
found strange in the commit description of the recently sent patch
"
On 13.04.16 19:54, Stephen Warren wrote:
> I've spotted a couple of problems in 74522c898b35 "efi_loader: Add
> distro boot script for removable media". These help explain something I
> found strange in the commit description of the recently sent patch
> "jetson-tk1: Set fdtfile environment varia
I've spotted a couple of problems in 74522c898b35 "efi_loader: Add
distro boot script for removable media". These help explain something I
found strange in the commit description of the recently sent patch
"jetson-tk1: Set fdtfile environment variable"; "The 4.5.0 kernel cannot
cope with U-Boot
6 matches
Mail list logo
