Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Matyukevich <geomatsi@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 4/5] configs/solidrun_macchiatobin_mainline: bump kernel and U-Boot
Date: Tue, 20 Nov 2018 19:31:04 +0300	[thread overview]
Message-ID: <20181120163104.wxmaqro2yukllssf@bars> (raw)
In-Reply-To: <2ef4e9d2b5fff465da879d99e412437ea7109b66.1542720610.git.baruch@tkos.co.il>

> Bump U-Boot to version 2018.11. This version supports autodetection of
> SD/eMMC boot source, so we can now enable environment load from SD card.
> Add a U-Boot kconfig fragment that sets SD/eMMC as environment load/save
> device. This avoids stale environment values from the SPI flash. That in
> turn, allows to use the more convenient distro boot which is enabled in
> the default environment.
> 
> Bump kernel to version 4.19.2. This version enables
> CONFIG_PHY_MVEBU_CP110_COMPHY in the arm64 defconfig, so remove it from
> the kernel kconfig fragment. Enable support for SFP modules detection
> and configuration. Leave the PHY drivers for now to keep them built into
> the kernel. The kernel defconfig builds these drivers as modules. But
> that does not work as expected in the default configuration.
> 
> Cc: Sergey Matyukevich <geomatsi@gmail.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
>  board/solidrun/macchiatobin/extlinux.conf          |  4 ++++
>  board/solidrun/macchiatobin/linux-extras.config    |  2 +-
>  board/solidrun/macchiatobin/post-build-mainline.sh |  5 +++++
>  board/solidrun/macchiatobin/uboot-fragment.config  |  2 ++
>  configs/solidrun_macchiatobin_mainline_defconfig   | 13 ++++++++-----
>  5 files changed, 20 insertions(+), 6 deletions(-)
>  create mode 100644 board/solidrun/macchiatobin/extlinux.conf
>  create mode 100755 board/solidrun/macchiatobin/post-build-mainline.sh
>  create mode 100644 board/solidrun/macchiatobin/uboot-fragment.config
 
Thanks! Verified the changes on MacchiatoBin v2 board:

Tested-by: Sergey Matyukevich <geomatsi@gmail.com>

By the way, it looks like mainline U-Boot v2018.11 still detects only 2GiB
of DRAM on my boards. Meanwhile vendor U-Boot provided by alternative
config solidrun_macchiatobin_marvell_defconfig detects 4GiB.

Regards,
Sergey

  reply	other threads:[~2018-11-20 16:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 13:30 [Buildroot] [PATCH next 1/5] toolchain: add 4.19.x choice for headers Baruch Siach
2018-11-20 13:30 ` [Buildroot] [PATCH next 2/5] linux-headers: bump to kernel version 4.19.2 Baruch Siach
2018-11-22 16:39   ` Peter Korsgaard
2018-11-20 13:30 ` [Buildroot] [PATCH next 3/5] linux: bump default to 4.19.2 Baruch Siach
2018-11-22 16:39   ` Peter Korsgaard
2018-11-20 13:30 ` [Buildroot] [PATCH next 4/5] configs/solidrun_macchiatobin_mainline: bump kernel and U-Boot Baruch Siach
2018-11-20 16:31   ` Sergey Matyukevich [this message]
2018-11-20 16:57     ` Baruch Siach
2018-11-20 20:03       ` Sergey Matyukevich
2018-11-22 16:40   ` Peter Korsgaard
2018-11-20 13:30 ` [Buildroot] [PATCH next 5/5] board: macchiatobin: update readme.txt Baruch Siach
2018-11-22 16:40   ` Peter Korsgaard
2018-11-22 16:38 ` [Buildroot] [PATCH next 1/5] toolchain: add 4.19.x choice for headers Peter Korsgaard

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=20181120163104.wxmaqro2yukllssf@bars \
    --to=geomatsi@gmail.com \
    --cc=buildroot@busybox.net \
    /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