mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: afaerber@suse.de (Andreas Färber)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] odroid-c2: Enable distro boot
Date: Tue, 1 Nov 2016 22:51:14 +0100	[thread overview]
Message-ID: <9e90b2e4-0e5c-0c99-51e2-2601757c8dce@suse.de> (raw)
In-Reply-To: <10583128-f7ef-8196-7533-fd7406fa6621@suse.de>

Hi Alex,

Am 01.11.2016 um 22:19 schrieb Alexander Graf:
> On 01/11/2016 22:11, Andreas F?rber wrote:
>> diff --git a/include/configs/meson-gxbb-common.h
>> b/include/configs/meson-gxbb-common.h
>> index 3bba2e6..0c467fe 100644
>> --- a/include/configs/meson-gxbb-common.h
>> +++ b/include/configs/meson-gxbb-common.h
>> @@ -40,4 +40,17 @@
>>
>>  #include <config_distro_defaults.h>
>>
>> +#define BOOT_TARGET_DEVICES(func) \
>> +    func(DHCP, dhcp, na)
> 
> Does the board have more common I/O available than Ethernet? MMC? SATA?

The board yes, U-Boot no. :) That's why I needed to get PXE to work. ;)
Thanks for your help.

FTR I noticed that in v2016.11-rc3 `bootp; bootefi 0x01000000` leads to
an odd $net_{default,efinet0}_mac in GRUB. CONFIG_DISTRO_DEFAULTS
(pulling in CONFIG_CMD_DHCP) resolved this, even when not booting
through the distro framework as before.

BTW it was unclear to me why CONFIG_CMD_SOURCE was disabled in the
defconfig - the distro framework emits an error if missing when it first
tries to execute the PXE file as script, therefore restoring the default
of enabling.

> If so, please add those too :).
> 
>> +#include <config_distro_bootcmd.h>
>> +
>> +#define CONFIG_EXTRA_ENV_SETTINGS \
>> +    "fdt_addr_r=0x01000000\0" \
> 
> This puts the device tree at 16MB. I don't know how smart the kernel is
> these days about accessing
> 
>   a) critical memory below its own starting point
>   b) memory that might collide with its own relocation point
> 
> so to be safe I think you're better off putting the device tree
> somewhere higher up. Maybe around 800MB?

The fdt and kernel addresses were adopted from the vendor U-Boot and
they worked for my PXE GRUB setup. ramdisk_addr_r was chosen by me and
is untested.

That said, maybe the linux-amlogic people have some input here.

Cheers,
Andreas

>> +    "scriptaddr=0x1f000000\0" \
>> +    "kernel_addr_r=0x20000000\0" \
>> +    "pxefile_addr_r=0x20000000\0" \
>> +    "ramdisk_addr_r=0x28000000\0" \
>> +    MESON_FDTFILE_SETTING \
>> +    BOOTENV
>> +
>>  #endif /* __MESON_GXBB_COMMON_CONFIG_H */
[snip]

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)

      reply	other threads:[~2016-11-01 21:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-01 21:11 Andreas Färber
2016-11-01 21:19 ` Alexander Graf
2016-11-01 21:51   ` Andreas Färber [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9e90b2e4-0e5c-0c99-51e2-2601757c8dce@suse.de \
    --to=afaerber@suse.de \
    --cc=linus-amlogic@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®