On Wed, Nov 16, 2016 at 11:33:26AM +0100, Alexander Graf wrote:
> On 16/11/2016 11:28, Daniel Kiper wrote:
> >On Tue, Nov 15, 2016 at 10:07:39PM +0100, Alexander Graf wrote:
[...]
> >>Uh, the point of the function was to share code between 32bit and 64bit
> >>arm platforms which are completely se
On 16/11/2016 11:28, Daniel Kiper wrote:
On Tue, Nov 15, 2016 at 10:07:39PM +0100, Alexander Graf wrote:
On 15/11/2016 22:00, Daniel Kiper wrote:
On Sat, Nov 12, 2016 at 12:03:33PM +0300, Andrei Borzenkov wrote:
29.02.2016 02:22, Alexander Graf ??:
Searching for a device tree that
On Tue, Nov 15, 2016 at 10:07:39PM +0100, Alexander Graf wrote:
>
>
> On 15/11/2016 22:00, Daniel Kiper wrote:
> >On Sat, Nov 12, 2016 at 12:03:33PM +0300, Andrei Borzenkov wrote:
> >>29.02.2016 02:22, Alexander Graf ??:
> >>>Searching for a device tree that EFI passes to us via configurati
On Sat, Nov 12, 2016 at 12:03:33PM +0300, Andrei Borzenkov wrote:
> 29.02.2016 02:22, Alexander Graf ??:
> > Searching for a device tree that EFI passes to us via configuration tables
> > is nothing architecture specific. Move it into generic code.
> >
> > Signed-off-by: Alexander Graf
> >
On 15/11/2016 22:00, Daniel Kiper wrote:
On Sat, Nov 12, 2016 at 12:03:33PM +0300, Andrei Borzenkov wrote:
29.02.2016 02:22, Alexander Graf ??:
Searching for a device tree that EFI passes to us via configuration tables
is nothing architecture specific. Move it into generic code.
Sign
29.02.2016 02:22, Alexander Graf пишет:
> Searching for a device tree that EFI passes to us via configuration tables
> is nothing architecture specific. Move it into generic code.
>
> Signed-off-by: Alexander Graf
> ---
> grub-core/kern/efi/init.c| 22 ++
> grub-core/load
Searching for a device tree that EFI passes to us via configuration tables
is nothing architecture specific. Move it into generic code.
Signed-off-by: Alexander Graf
---
grub-core/kern/efi/init.c| 22 ++
grub-core/loader/arm64/fdt.c | 24 +---
include/
