On 2024-09-16, Herman Rimm wrote:
> --- /dev/null
> +++ b/gnu/packages/patches/u-boot-50M-kernel.patch
> @@ -0,0 +1,51 @@
> +This patch configures the U-Boot for Raspberry Pis to reserve 50 MB for
> +linux kernels, because the 6.9 and newer linux-libre-arm64-generic
> +kernels can be larger than 36
On 2023-11-21, Tom Rini wrote:
> On Tue, Nov 21, 2023 at 11:10:57AM -0800, Vagrant Cascadian wrote:
>
>> I've been reviewing the copyright and license information for Das U-Boot
>> in preparation for uploading to Debian, and found a few surprises.
>>
>> too
I've been reviewing the copyright and license information for Das U-Boot
in preparation for uploading to Debian, and found a few surprises.
tools/libfdt/fdt_rw.c: /* SPDX-License-Identifier: GPL-2.0+ BSD-2-Clause */
I *think* according to the SPDX spec this needs an OR or an AND. I also
see no c
On 2023-05-01, Wolfgang Zarre wrote:
> If u-boot is installed on the internal emmc, then this will
> allow to boot without failure.
>
> Signed-off-by: Wolfgang Zarre
> Reviewed-by: Kever Yang
This is marked as accepted in patchwork, but I do not see it in git
yet...
Is this planned to land in 2
On 2023-04-28, Vagrant Cascadian wrote:
> On 2023-02-05, Vagrant Cascadian wrote:
>> On 2023-02-06, Patrick Wildt wrote:
>>> The MNT Reform 2 is a modular DIY laptop. In its initial version it
>>> is based on the BoundaryDevices i.MX8MQ SoM. Some parts have been
>
On 2023-02-05, Vagrant Cascadian wrote:
> On 2023-02-06, Patrick Wildt wrote:
>> The MNT Reform 2 is a modular DIY laptop. In its initial version it
>> is based on the BoundaryDevices i.MX8MQ SoM. Some parts have been
>> lifted from BoundaryDevices official U-Bo
d measure
double-checked that it did not introduce regressions on rock64-rk3328,
because it readily available to test. :)
Looks good to me, thanks!
live well,
vagrant
> Signed-off-by: Simon Glass
> Tested-by: Vagrant Cascadian
> ---
> Changes in v4:
> None.
> ---
> arch/ar
Adding u-boot maintainers for rpi (Matthias Brugger, Peter Robinson)
platforms and u-boot list to CC.
On 2023-03-22, Salvatore Bonaccorso wrote:
> Thanks for tracking this down. I would like to loop in Masahiro and
> upstream to see if something can/should be done on upstream side.
>
> Masahiro, i
uot;ram: rockchip: Update ddr pctl regs for px30")
> Signed-off-by: Jonas Karlman
> Reviewed-by: Simon Glass
> Reviewed-by: Kever Yang
> Reviewed-by: Jagan Teki
> Tested-by: Jagan Teki # roc-rk3328-cc
Thanks! This allows booting the rock64-rk3328 with v2023.04-rc2, which
otherwise j
On 2023-02-21, Vagrant Cascadian wrote:
> On 2023-02-21, Simon Glass wrote:
>> This board has moved to standard boot but the old 'distro_bootcmd'
>> command is still active. Disable DISTRO_DEFAULTS to fix this.
>
> Works for booting rockpro64-rk3399, thanks!
I c
On 2023-02-21, Simon Glass wrote:
> This board has moved to standard boot but the old 'distro_bootcmd'
> command is still active. Disable DISTRO_DEFAULTS to fix this.
Works for booting rockpro64-rk3399, thanks!
Tested-by: Vagrant Cascadian
> Signed-off-by: Simon Glass
On 2023-02-21, Simon Glass wrote:
> This is needed to enable the boot command used to start standard boot.
> Enable it by default. This brings in quite a few features, mostly in
> common with DISTRO_DEFAULTS
Works for booting rockpro64-rk3399, thanks!
Tested-by: Vagrant Cascadian
>
ed-off-by: Simon Glass
Works for booting rockpro64-rk3399, thanks!
Tested-by: Vagrant Cascadian
> configs/rockpro64-rk3399_defconfig | 5 -
> 1 file changed, 5 deletions(-)
>
> diff --git a/configs/rockpro64-rk3399_defconfig
> b/configs/rockpro64-rk3399_defconfig
> ind
On 2023-02-20, Simon Glass wrote:
> On Sat, 18 Feb 2023 at 19:19, Vagrant Cascadian wrote:
>> On 2022-12-07, Simon Glass wrote:
>> > Drop the use of scripts and rely on standard boot for all operation.
>>
>> This patch, applied as 3891c68ef50eda38d78c95ecd03aed
On 2022-12-07, Simon Glass wrote:
> Drop the use of scripts and rely on standard boot for all operation.
This patch, applied as 3891c68ef50eda38d78c95ecd03aed030aa6bb53 broke
booting on pinebook-pro-rk3399, which still tries to "run
distro_bootcmd" but distro_bootcmd is no longer defined... probab
booting Debian with a 6.1.x linux kernel on a mnt/reform2 using
nvme rootfs and microsd /boot. Some oddities with video and wifi that do
not occur with the vendor u-boot, but seems like huge progress.
Thanks!
Tested-by: Vagrant Cascadian
> ---
> Changes since v7:
> - Re-added lost r
On 2023-01-19, Patrick Wildt wrote:
> The MNT Reform 2 is a modular DIY laptop. In its initial version it
> is based on the BoundaryDevices i.MX8MQ SoM. Some parts have been
> lifted from BoundaryDevices official U-Boot downstream project.
>
> Signed-off-by: Patrick Wildt
> ---
> Changes since v
On 2023-01-16, Fabio Estevam wrote:
> Select the CONFIG_CMD_EXT4 option so that files can be loaded
> from an ext4 partition.
>
> Signed-off-by: Fabio Estevam
Debian has been carrying this patch since 2014; thanks for submitting
upstream!
Unfortunately, I do not know if anyone is actively using
; Suggested-by: Heinrich Schuchardt
> Fixes: a56f663f0707 ("vbe: Add info about the VBE device to the fwupd node")
I was able to reproduce the issue using the qemu-riscv64 instructions
Karsten provided, and applying the patch fixes it, thanks!
Tested-by: Vagrant Cascadian
live wel
On 2023-01-13, Tom Rini wrote:
> On Fri, Jan 13, 2023 at 06:26:00PM -0300, Fabio Estevam wrote:
>> I am trying to upgrade U-Boot to 2023.01 in OpenEmbedded, but I see
>> the following error when trying to build u-boot-tools:
>>
>> | /bin/sh: line 1: tools/bmp_logo: No such file or directory
>>
>>
ell.
Thanks!
Tested-by: Vagrant Cascadian
live well,
vagrant
> ---
> v2:
> use efi_get_memory_map_alloc()
> ---
> lib/lmb.c | 36
> 1 file changed, 36 insertions(+)
>
> diff --git a/lib/lmb.c b/lib/lmb.c
> index c599608f
Tested-by: Vagrant Cascadian
live well,
vagrant
> ---
> v2:
> new patch
> ---
> cmd/efidebug.c | 18 --
> include/efi_loader.h| 3 +++
> lib/efi_loader/efi_memory.c | 34 ++
> 3 files changed, 41 insert
On 2022-12-25, Jochen Sprickerhof wrote:
> * Vagrant Cascadian [2022-11-04 14:22]:
>>On 2022-06-02, Jochen Sprickerhof wrote:
>>> with the latest u-boot-exynos in unstable it tries to load
>>> exynos5422-smdk5420xu4.dtb whereas linux-image-5.17.0-3-armmp only
>>&g
On 2022-12-13, Pali Rohár wrote:
> Vagrant and Aurelien, could you test if this change fully fixes your
> Debian issue?
Well, apparently the issue has been fixed some other way, as u-boot
2022.03-rc3 builds the qemu-ppce500 target fine in Debian with binutils
2.39.50.20221208-5 even without the ol
On 2022-10-12, Tom Rini wrote:
> On Fri, Sep 02, 2022 at 01:06:16AM +0300, Andrey Skvortsov wrote:
>> If extlinux.conf is used, then it's not possible to customize boot
>> environment, because scripts are not loaded.
>> Usually it's possible to make some changes manually using command line
>> and s
On 2022-08-28, Vagrant Cascadian wrote:
> On 2022-08-28, Rasmus Villemoes wrote:
>> On 26/08/2022 22.59, Tom Rini wrote:
>>> On Thu, Aug 18, 2022 at 10:31:34AM -0700, Vagrant Cascadian wrote:
>>>> From: Vagrant Cascadian
>>>>
>>>> The KBUILD_
On 2022-08-28, Rasmus Villemoes wrote:
> On 26/08/2022 22.59, Tom Rini wrote:
>> On Thu, Aug 18, 2022 at 10:31:34AM -0700, Vagrant Cascadian wrote:
>>
>>> From: Vagrant Cascadian
>>>
>>> The KBUILD_CFLAGS and KBUILD_AFLAGS variables are adjusted to us
From: Vagrant Cascadian
The KBUILD_CFLAGS and KBUILD_AFLAGS variables are adjusted to use
-ffile-prefix-map and --debug-prefix-map, respectively, to use
relative paths for occurrences of __FILE__ and debug paths.
This enables reproducible builds regardless of the absolute path to
the build
It looks like u-boot 2022.07-rc1 introduced a reproducibility issue that
is dependent on the running kernel.
I believe the commit that triggered this issue is:
f7691a6d736bec7915c227ac14076f9993a27367 sandbox: allow cross-compiling
sandbox
While the use of uname in the Makefile goes back well
Fix spelling of "followed" in kwboot.1 manpage.
Series: 2
Signed-off-by: Vagrant Cascadian
---
Changes in v2:
Use "tools: kwboot:" prefix.
Add full commit message.
doc/kwboot.1 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/kwboot.1 b/doc/kwboo
Signed-off-by: Vagrant Cascadian
---
doc/kwboot.1 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/kwboot.1 b/doc/kwboot.1
index f555ff26a2..d663bf1f77 100644
--- a/doc/kwboot.1
+++ b/doc/kwboot.1
@@ -74,7 +74,7 @@ BootROM's standard input and BootROM's termina
Add options to enable AHCI, SCSI and SATA.
Signed-off-by: Vagrant Cascadian
---
configs/rockpro64-rk3399_defconfig | 7 +++
1 file changed, 7 insertions(+)
diff --git a/configs/rockpro64-rk3399_defconfig
b/configs/rockpro64-rk3399_defconfig
index d5e98a4f73..858410e8f7 100644
--- a
Include SCSI in the list of boot targets if CONFIG_CMD_SCSI is
enabled.
Signed-off-by: Vagrant Cascadian
---
include/configs/rockchip-common.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/include/configs/rockchip-common.h
b/include/configs/rockchip-common.h
index ba7061a287
This patch series adds SCSI booting to rockchip-common.h to enable
scsi boot options from distro boot, and enables SCSI options in the
rockpro64-rk3399 configuration.
Vagrant Cascadian (2):
rockchip: Enable SCSI in distro bootcmd for rk3399.
rockchip: Enable AHCI/SCSI/SATA on rockpro64
On 2022-01-25, Vagrant Cascadian wrote:
> On 2022-01-15, Aurelien Jarno wrote:
>> On 2022-01-11 16:40, Vagrant Cascadian wrote:
>>> On 2022-01-11, Lennart Sorensen wrote:
>>> > On Mon, Jan 10, 2022 at 05:10:04PM -0800, Vagrant Cascadian wrote:
>>> >>
A bug in Debian is causing a build failure of the qemu-ppce500 target:
https://bugs.debian.org/1003490
I've CCed u-boot in case they're not aware of the issue.
Some background follows...
On 2022-01-15, Aurelien Jarno wrote:
> On 2022-01-11 16:40, Vagrant Cascadian wrote:
>
---
drivers/usb/gadget/dwc2_udc_otg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/dwc2_udc_otg.c
b/drivers/usb/gadget/dwc2_udc_otg.c
index 2f31814442..b30604eba0 100644
--- a/drivers/usb/gadget/dwc2_udc_otg.c
+++ b/drivers/usb/gadget/dwc2_udc_otg.c
@@ -4
---
arch/arm/mach-keystone/ddr3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-keystone/ddr3.c b/arch/arm/mach-keystone/ddr3.c
index 9ee3284156..53117c2695 100644
--- a/arch/arm/mach-keystone/ddr3.c
+++ b/arch/arm/mach-keystone/ddr3.c
@@ -344,7 +344,7 @@ void d
---
drivers/ddr/altera/sequencer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ddr/altera/sequencer.c b/drivers/ddr/altera/sequencer.c
index 8a016f0628..e402f2929a 100644
--- a/drivers/ddr/altera/sequencer.c
+++ b/drivers/ddr/altera/sequencer.c
@@ -2770,7 +2770,7 @@
---
common/fdt_support.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/fdt_support.c b/common/fdt_support.c
index 8992ac5d3f..a7dbe0efdf 100644
--- a/common/fdt_support.c
+++ b/common/fdt_support.c
@@ -1407,7 +1407,7 @@ int fdt_get_dma_range(const void *blob, int node,
---
drivers/core/of_addr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/core/of_addr.c b/drivers/core/of_addr.c
index 3fbc0a7afa..431dd4e565 100644
--- a/drivers/core/of_addr.c
+++ b/drivers/core/of_addr.c
@@ -367,7 +367,7 @@ int of_get_dma_range(const struct device_
---
drivers/net/fec_mxc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/fec_mxc.c b/drivers/net/fec_mxc.c
index 40a86a3e12..811bc275c1 100644
--- a/drivers/net/fec_mxc.c
+++ b/drivers/net/fec_mxc.c
@@ -1465,7 +1465,7 @@ static int fecmxc_probe(struct udevice *dev)
---
cmd/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmd/Kconfig b/cmd/Kconfig
index 5b30b13e43..bb11aec9b7 100644
--- a/cmd/Kconfig
+++ b/cmd/Kconfig
@@ -1012,7 +1012,7 @@ config CMD_IDE
select IDE
help
Provides an 'ide' command which allow
---
arch/arm/cpu/armv8/fsl-layerscape/fsl_lsch2_serdes.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/cpu/armv8/fsl-layerscape/fsl_lsch2_serdes.c
b/arch/arm/cpu/armv8/fsl-layerscape/fsl_lsch2_serdes.c
index 41c89b8904..60769e139e 100644
--- a/arch/arm/cpu/armv8/fsl
---
drivers/usb/musb/musb_udc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/musb/musb_udc.c b/drivers/usb/musb/musb_udc.c
index b9510e3045..2ffcb7caaa 100644
--- a/drivers/usb/musb/musb_udc.c
+++ b/drivers/usb/musb/musb_udc.c
@@ -269,7 +269,7 @@ static void musb
---
drivers/mtd/ubispl/ubispl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/ubispl/ubispl.c b/drivers/mtd/ubispl/ubispl.c
index 03b31f002b..b58d8e8d56 100644
--- a/drivers/mtd/ubispl/ubispl.c
+++ b/drivers/mtd/ubispl/ubispl.c
@@ -953,7 +953,7 @@ retry:
---
arch/arm/mach-bcm283x/msg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-bcm283x/msg.c b/arch/arm/mach-bcm283x/msg.c
index 01a8ed2a7b..fe243e2dca 100644
--- a/arch/arm/mach-bcm283x/msg.c
+++ b/arch/arm/mach-bcm283x/msg.c
@@ -194,7 +194,7 @@ int bcm2711_noti
and .dtb, thanks!
Tested-By: Vagrant Cascadian
This may not be specific to this patch series, but one problem I had
during build is that it doesn't appear to respect the BL31 environment
variable that many other platforms support to specify the path to the
ATF firmware; is there a way to
On 2021-11-11, Patrick Wildt wrote:
> On Thu, Nov 11, 2021 at 12:21:26PM +0100, Patrick Wildt wrote:
>> On Wed, Nov 10, 2021 at 02:26:54PM -0800, Vagrant Cascadian wrote:
>> > On 2021-09-02, Patrick Wildt wrote:
>> > > The MNT Reform 2 is a modular DIY laptop. In it
On 2021-09-02, Patrick Wildt wrote:
> The MNT Reform 2 is a modular DIY laptop. In its initial version it
> is based on the BoundaryDevices i.MX8MQ SoM. Some parts have been
> lifted from BoundaryDevices official U-Boot downstream project.
Thanks for working on this!
I'm struggling a bit gettin
On 2021-10-22, Andre Przywara wrote:
> On Fri, 22 Oct 2021 09:47:35 -0700
> Vagrant Cascadian wrote:
>> On 2021-10-22, Tom Rini wrote:
>> > On Fri, Oct 22, 2021 at 04:56:09PM +0100, Andre Przywara wrote:
>> >> On Fri, 22 Oct 2021 11:09:27 -0400
>> >&g
On 2021-10-22, Tom Rini wrote:
> On Fri, Oct 22, 2021 at 04:56:09PM +0100, Andre Przywara wrote:
>> On Fri, 22 Oct 2021 11:09:27 -0400
>> Tom Rini wrote:
>> > On Fri, Oct 22, 2021 at 04:59:22PM +0200, Marek Behún wrote:
>> > > On Fri, 22 Oct 2021 12:09:19 +0200
>> > > Heinrich Schuchardt wrote:
Signed-off-by: Vagrant Cascadian
---
tools/image-host.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/image-host.c b/tools/image-host.c
index d3a882ec29..a6b0a94420 100644
--- a/tools/image-host.c
+++ b/tools/image-host.c
@@ -313,7 +313,7 @@ static int
On 2021-08-22, Tom Rini wrote:
> On Sat, Aug 21, 2021 at 09:19:56PM -0500, Samuel Holland wrote:
>> On 6/21/21 6:56 PM, Andre Przywara wrote:
>> > On Mon, 21 Jun 2021 16:35:37 -0400
>> > Tom Rini wrote:
>> >> On Mon, Jun 21, 2021 at 04:43:00PM +0100, Andre Przywara wrote:
>> >>> On Sun, 20 Jun 202
On 2021-03-07, Nicolas Boulenguez wrote:
> From: Arnaud Ferraris
>
> The PineTab device-tree is already in u-boot, this commit adds the
> corresponding
> defconfig, based on pinephone_defconfig.
>
> Signed-off-by: Arnaud Ferraris
...
> --- /dev/null
> +++ b/configs/pinetab_defconfig
...
> +CONFI
It seems like commit:
3f04db891a353f4b127ed57279279f851c6b4917 image: Check for unit addresses in FIT
Broke test/image/test-imagetools.sh.
I get the impression test-imagetools.sh is more-or-less unmaintained and
deprecated. Does test-imagetools.sh perform tests that are not covered
elsewhere? If
On 2021-02-10, Rick Thomas wrote:
> On Wed, Feb 10, 2021, at 5:55 PM, Tom Rini wrote:
>> On Wed, Feb 10, 2021 at 05:01:47PM -0800, Rick Thomas wrote:
>> > On Wed, Feb 10, 2021, at 12:15 PM, Tom Rini wrote:
>> > > I assume that however you're building U-Boot the warnings that get
>> > > printed abou
It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot when usb
is started. It hangs indefinitely at:
## Flattened Device Tree blob at 01f0
Booting using the fdt blob at 0x1f0
I have observed this also using 2020.10 on rockpro64-rk3399, though on
pinebook-pro-rk3399 usb doe
he u-boot CC on follow-ups.
On 2020-09-03, Andre Heider wrote:
> On 03/09/2020 20:59, Vagrant Cascadian wrote:
>> On 2020-09-03, Andre Heider wrote:
>>> On 03/09/2020 18:40, Dennis Gilmore wrote:
>>> If so, adding fdtfile like that would break booting debian using its
>
enting what is needed.
>>
>> Signed-off-by: Dennis Gilmore
>>
>> Cc: Atish Patra
>> Cc: Lukas Auer
>> Cc: Tom Rini
>> Cc: Masahiro Yamada
>> Cc: Vagrant Cascadian
>> Cc: Stephen Warren
>> Cc: Karsten Merker
>> ---
>>
On 2020-07-27, Fabio Estevam wrote:
> Vagrant Cascadian reported that mx6cuboxi target no longer builds
> reproducibility on Debian.
>
> One example of builds mismatches:
>
> 00096680: 696e 6700 736f 756e 642d 6461 6900 6465 ing.sound-dai.de
> -00096690: 7465 637
On 2020-07-26, Fabio Estevam wrote:
> On Sun, Jul 26, 2020 at 2:16 PM Tom Rini wrote:
>
>> I mean just literally changing the malloc(...) to calloc(1, ...), audit any
>> other malloc(...) calls in the file and change nothing else. Thanks!
>
> Thanks for the clarification, Tom
>
> Vagrant,
>
> Doe
On 2020-07-21, Tom Rini wrote:
> On Sun, Jul 19, 2020 at 11:23:05AM -0700, Vagrant Cascadian wrote:
>
>> The mx6cuboxi target no longer builds reproducibility on Debian. I've
>> bisected it down to:
>>
>> eb9124f5748c96ffd548e50fd6989c3b5395b353 mx6cuboxi: en
The mx6cuboxi target no longer builds reproducibility on Debian. I've
bisected it down to:
eb9124f5748c96ffd548e50fd6989c3b5395b353 mx6cuboxi: enable OF_CONTROL with
DM_MMC and DM_USB
Based on the diffoscope output, it *might* have something to do with the
changes to how board detection uses
Signed-off-by: Vagrant Cascadian
---
cmd/booti.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmd/booti.c b/cmd/booti.c
index ae37975494..af0603b96e 100644
--- a/cmd/booti.c
+++ b/cmd/booti.c
@@ -141,7 +141,7 @@ static char booti_help_text[] =
"\tspecifyin
Signed-off-by: Vagrant Cascadian
---
doc/board/sifive/fu540.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/board/sifive/fu540.rst b/doc/board/sifive/fu540.rst
index 43402cb2e5..39fb8d8990 100644
--- a/doc/board/sifive/fu540.rst
+++ b/doc/board/sifive/fu540.rst
On 2020-04-27, Simon Glass wrote:
> On Sun, 26 Apr 2020 at 18:58, Heinrich Schuchardt wrote:
>>
>> Am April 27, 2020 12:29:29 AM UTC schrieb Simon Glass :
>> >At present U-Boot always builds dtc if CONFIG_OF_CONTROL is defined.
>> >This
>> >is wasteful when the system already has a suitable versio
On 2020-04-20, Peter Robinson wrote:
> add "boe,nv140fhmn49" display to compatible node.
I didn't see u-boot output on the eDP panel; not sure if that's
expected. Once linux booted it did work just fine.
live well,
vagrant
> Signed-off-by: Peter Robinson
> Cc: Anatolij Gustschin
> ---
> dri
t and boot tested on Debian and GNU Guix on a Pinebook Pro, so (for
the whole series):
Tested-by: Vagrant Cascadian
live well,
vagrant
> ---
> arch/arm/dts/rk3399-pinebook-pro-u-boot.dtsi | 43 ++
> arch/arm/mach-rockchip/rk3399/Kconfig | 8 ++
> board/pine64/p
iewed-by: Anatolij Gustschin
This fixed the build I was having with the pinebook pro patches when
applied to v2020.04, built on both Debian and GNU Guix.
Thanks!
Tested-by: Vagrant Cascadian
> ---
> drivers/video/rockchip/rk_edp.c | 1 +
> drivers/video/rockchip/rk_lvds.c | 3 ++-
>
On 2020-04-20, Peter Robinson wrote:
> It took a little longer than I planned, took me a little bit to get it
> working with the upstream device tree that landed in 5.7-rc1 but it's
> there now.
>
> Tested with Fedora 32.
I was unable to build applied against 2020.04 on Debian or GNU Guix,
ending
On 2020-03-29, Chris Dumont wrote:
>* What led up to the situation?
> read the manpage for mkimage and then used 'mkimage -T -h'
...
>* What was the outcome of this action?
> The output (ellipsized)
>
> $ mkimage -T -h
>
> Invalid image type, supported are:
> Unknown image t
On 2019-12-18, Vagrant Cascadian wrote:
> On 2019-11-14, Peter Robinson wrote:
>> Add initial support for Pinebook Pro laptop.
Now that the device-tree is in linux-next (should land in linux 5.7),
anyone have a chance to take a stab at a v2 of this patch series? I did
a quick-and-dirt
On 2020-03-08, Bernhard wrote:
> I had an additional look for the possible problem with the AXP813 for
> BananaPi M3 in U-Boot.
> With help of Google, i found a patchset for U-Boot from 2016:
>
> https://lists.denx.de/pipermail/u-boot/2016-January/240259.html
>
>> +++ b/configs/Bananapi_m3_defconf
On 2020-01-18, Maxime Ripard wrote:
> On Sat, Jan 18, 2020 at 03:15:15AM -0800, Vagrant Cascadian wrote:
>> Video output on the pinebook LCD screen was broken by:
>>
>> commit 2cc393f32fd9 ("video: make BPP and ANSI configs optional").
>>
>> Enable
Video output on the pinebook LCD screen was broken by:
commit 2cc393f32fd9 ("video: make BPP and ANSI configs optional").
Enable VIDEO_BPP32 which was previously enabled by default when
DM_VIDEO was set.
Signed-off-by: Vagrant Cascadian
---
configs/pinebook_defconfig | 1 +
1 file
n
> - USB 3.0, 2.0
> - USB Type C power and data
> - DC 12V/2A
5V/3A, as already mentioned.
> Signed-off-by: Peter Robinson
> ---
>
> Initial v1 for feedback
Tested on u-boot v2020.01-rc5; applied with trivial adjustments.
Thanks for working on it!
Tested-by: Vagrant Casc
On 2019-12-18, David Abdurachmanov wrote:
> On Wed, Dec 18, 2019 at 3:13 AM Vagrant Cascadian wrote:
>>
>> On 2019-09-25, Vagrant Cascadian wrote:
>> > On 2019-08-21, David Abdurachmanov wrote:
>> >> Commit 37304aaf60bf92a5dc3ef222ba520698bd862a44 removed preb
On 2019-09-25, Vagrant Cascadian wrote:
> On 2019-08-21, David Abdurachmanov wrote:
>> Commit 37304aaf60bf92a5dc3ef222ba520698bd862a44 removed preboot
>> commands in RISC-V targets and broke extlinux support as reported
>> by Fu Wei .
>>
>> The patch finishes mi
The instructions in doc/README.rockchip for installing rock64-rk3328
make use of u-boot.itb, but it is not built by default.
Add u-boot.itb to BUILD_TARGET for RK3328 platforms.
Signed-off-by: Vagrant Cascadian
---
Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
On 2019-09-27, Heinrich Schuchardt wrote:
> On 9/27/19 6:36 PM, Peter Robinson wrote:
>>> I'm currently kicking test.py to use Python 3 instead of Python 2.7 and
>>> seeing places where it would (seemingly) be nice to be able to say that
>>> we have Python 3.6 as our minimum version. To do this ho
I just tested mx6cuboxi with 2019.10-rc4, and it fails to load
u-boot.img from MMC:
1 2019-09-26_17:31:27.63089 U-Boot SPL 2019.10-rc4+dfsg-1 (Sep 24 2019 -
08:03:23 +)
2 2019-09-26_17:31:27.63092 Trying to boot from MMC2
3 2019-09-26_17:31:27.63095 MMC Device 1 not found
4 2019-09-26_17:31:27
On 2019-08-20, Vagrant Cascadian wrote:
> On 2019-08-19, Marek Vasut wrote:
>> On 6/4/19 9:06 AM, Vagrant Cascadian wrote:
>>> On 2019-05-17, Marek Vasut wrote:
>>>> Update Kosagi Novena to DM / DT and remove the warnings.
> ...
>>> I have two oustand
On 2019-09-26, Bin Meng wrote:
> On Thu, Sep 26, 2019 at 8:57 AM Vagrant Cascadian wrote:
>> On 2019-07-15, Vagrant Cascadian wrote:
>> > This allows booting an initrd without headers generated by mkimage,
>> > which is generally needed when using distro_bootcmd wi
Tested using qemu-riscv64_smode and it fixes extlinux booting. Thanks!
Please CC me on future updates to the patch series.
Tested-by: Vagrant Cascadian
live well,
vagrant
> Signed-off-by: David Abdurachmanov
> ---
> configs/qemu-riscv64_smode_defconfig | 2 ++
> configs/si
Haven't heard any comment on this; is there someone better to CC?
Would be really nice if it could be considered for v2019.10.
Thanks!
live well,
vagrant
On 2019-07-15, Vagrant Cascadian wrote:
> This allows booting an initrd without headers generated by mkimage,
> which is gener
I've been unable to successfully run "make envtools" on recent versions
of u-boot, and finally got a chance to git bisect it.
It looks like commit 9fb625ce05539fe6876a59ce1dcadb76b33c6f6e,
introduced after 2019.10-rc1, breaks building envtools:
#!/bin/sh
# test-bisect
set -e
set -x
make clean
mak
On 2019-08-19, Marek Vasut wrote:
> On 6/4/19 9:06 AM, Vagrant Cascadian wrote:
>> On 2019-05-17, Marek Vasut wrote:
>>> Update Kosagi Novena to DM / DT and remove the warnings.
...
>> I have two oustanding issues... with some files it sometimes fails to
>&
This allows booting an initrd without headers generated by mkimage,
which is generally needed when using distro_bootcmd with
extlinux-style boot menus.
Signed-off-by: Vagrant Cascadian
---
configs/qemu-riscv64_defconfig | 1 +
configs/qemu-riscv64_smode_defconfig | 1 +
2 files changed
On 2019-06-04, Vagrant Cascadian wrote:
> On 2019-05-17, Marek Vasut wrote:
Retried with a build from:
https://github.com/marex/u-boot-imx/tree/imx-dm
commit:7a381bb7edfd43aefc1dbfea6d574234ef9d7771
Which contains the two patchsets needed.
> I have two oustanding issues... with some
?series=108463 and this
series applied, with the above caveats:
Tested-by: Vagrant Cascadian
live well,
vagrant
> Marek Vasut (7):
> ARM: dts: imx: novena: Import Novena DT from Linux
> ARM: imx: novena: Enable DM pin control
> ARM: imx: novena: Enable DM GPIO
> ARM: imx
On 2019-05-20, Matwey V. Kornilov wrote:
> пн, 20 мая 2019 г. в 20:11, Vagrant Cascadian :
>>
>> On 2019-05-19, Matwey V. Kornilov wrote:
>> > The ROCK64 is a credit card size SBC based on Rockchip RK3328
>> > Quad-Core ARM Cortex A53.
>> >
>> > T
On 2019-05-19, Matwey V. Kornilov wrote:
> The ROCK64 is a credit card size SBC based on Rockchip RK3328
> Quad-Core ARM Cortex A53.
>
> This series allow building u-boot SPL and u-boot.itb for Rock64
> board. The proprietary TPL is stil required for deploy:
>
> ./tools/mkimage -n rk3328 -T rksd
On 2019-05-13, Vagrant Cascadian wrote:
> On 2019-05-13, Vagrant Cascadian wrote:
>> On 2019-05-08, Matwey V. Kornilov wrote:
>>> Signed-off-by: Matwey V. Kornilov
>>> ---
>>> configs/rock64-rk3328_defconfig | 91
>>> +++
On 2019-05-13, Vagrant Cascadian wrote:
> On 2019-05-08, Matwey V. Kornilov wrote:
>> Signed-off-by: Matwey V. Kornilov
>> ---
>> configs/rock64-rk3328_defconfig | 91
>> +
>> 1 file changed, 91 insertions(+)
>
On 2019-05-08, Matwey V. Kornilov wrote:
> Signed-off-by: Matwey V. Kornilov
> ---
> configs/rock64-rk3328_defconfig | 91
> +
> 1 file changed, 91 insertions(+)
> create mode 100644 configs/rock64-rk3328_defconfig
Thanks for submitting these patches ups
On 2019-05-06, Marek Vasut wrote:
> On 5/6/19 5:26 AM, Vagrant Cascadian wrote:
>> On 2019-05-06, Marek Vasut wrote:
>>> Enable DM USB support on iMX6Q Novena.
...
>> => load usb 0:1 $kernel_addr_r misc/Binaries/linux/Image
>> data abort
>> pc : [] l
On 2019-05-06, Marek Vasut wrote:
> On 5/6/19 5:31 AM, Vagrant Cascadian wrote:
>> On 2019-05-06, Marek Vasut wrote:
>>> Enable DM Video support on iMX6Q Novena and fix minor details
>>> to restore previous behavior of the system.
>>
>> Also required:
&
would hang after initializing video.
I don't see video output though. Not sure when I last tested video
output from u-boot, though. But at least it boots!
live well,
vagrant
> Signed-off-by: Marek Vasut
> Cc: Fabio Estevam
> Cc: Stefano Babic
> Cc: Vagrant Cascadian
>
at said, I haven't tested USB recently; it may be no worse.
live well,
vagrant
> Signed-off-by: Marek Vasut
> Cc: Fabio Estevam
> Cc: Stefano Babic
> Cc: Vagrant Cascadian
> ---
> configs/novena_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
&g
1 - 100 of 321 matches
Mail list logo