On 6/1/24 4:23 PM, Elena Popa wrote:
Hi Marek,
Hi,
sorry for the really late reply.
Does it also work if you 'setenv usb_pgood_delay 2000' ?
No, the USB stick is still not initialized.
Can you include the 5ms patch ?
I've attached the patch which makes it work. Of course, I'm not sure
On 7/1/24 10:42 AM, Quentin Schulz wrote:
Hi Marek,
Hi,
Shouldn't this rather be in /config node?
This is what I had there originally, but then I realized that some
DTs might not have the /config node in them (or am I mistaken?), so
I moved the new properties into the root node, which sur
On 6/27/24 10:19 AM, Simon Glass wrote:
Hi Marek,
Hi,
Add new binman etype which allows signing both the SPL and fitImage sections
of i.MX8M flash.bin using CST. There are multiple DT properties which govern
the signing process, nxp,loader-address is the only mandatory one which sets
the SPL
On Tue, Jul 2, 2024 at 12:38 PM Simon Glass wrote:
>
> For some reason every second time imx93_11x11_evk is built it gives an
> error:
>
>make O=/tmp/x BINMAN_ALLOW_MISSING=1
>
> It seems to sometimes skip generation of the .cfgout file and then
> eventually Binman complains:
>
>ValueError
On Fri, Jul 5, 2024 at 4:30 AM Michael Trimarchi
wrote:
>
> The mux ops for i.MX8M composite clk needs to be specialized.
> In order to reduce the code duplication we need to make public some
> interface and write a specific function in the mux ops. Those patches
> implement the behavior.
>
> Addr
On Tue, Jul 2, 2024 at 7:26 AM Michael Trimarchi
wrote:
>
> The mux flags (u8), div flags (u8), and gate flags (u8) are not the clk
> flags (unsigned long). They have different meanings
>
> Signed-off-by: Michael Trimarchi
Applied both, thanks.
On Wed, Jun 26, 2024 at 9:14 PM Marek Vasut wrote:
>
> Enable PCA953x GPIO expander driver in DH i.MX8MP DHCOM PDK2 configuration.
> The PCA9539 GPIO expander is used on production DH i.MX8MP DHCOM SoM rev.200.
> This is already enabled in DH i.MX8MP DHCOM PDK3 configuration so align the
> two con
On Wed, Jun 26, 2024 at 9:01 PM Marek Vasut wrote:
>
> Enable 'cat' command to print file from filesystem to stdout.
> Enable 'xxd' command to hexdump file from filesystem to stdout.
>
> Signed-off-by: Marek Vasut
Applied, thanks.
On Tue, Jun 25, 2024 at 5:26 AM Marek Vasut wrote:
>
> The older i.MX8M Mini Verdin SoMs may came with 20 MHz SPI CAN controller
> oscillator, the newer SoMs always use 40 MHz oscillator. Handle both by
> overriding the oscillator frequency just before booting the kernel.
>
> These are the known v
On Fri, Jul 5, 2024 at 9:11 AM Leonard Anderweit wrote:
>
> Initialize the Cryptographic Accelerator and Assurance Module.
>
> Signed-off-by: Leonard Anderweit
Applied, thanks.
On Thu, Jul 4, 2024 at 9:03 AM Fabio Estevam wrote:
>
> From: Fabio Estevam
>
> Booting an initramfs with the current initrd_addr address may lead to
> initramfs corruption and boot failure.
>
> Fix the initramfs problem by applying the following layout
> suggested by Tom Rini:
>
> loadaddr=0x404
On Fri, Jul 5, 2024 at 11:26 AM Alexander Stein
wrote:
>
> Add missing newline character and also add the return code of
> regulator_set_value() to the output.
>
> Signed-off-by: Alexander Stein
Applied, thanks.
On Thu, Jul 4, 2024 at 6:22 PM Adam Ford wrote:
>
> Since commit ecb1c37a7b64 ("clk: imx8mp: Add EQoS MAC clock"),
> the clocks for the DWMAC driver can be configured, and removing
> them breaks operation.
>
> Fixes: ecb1c37a7b64 ("clk: imx8mp: Add EQoS MAC clock")
> Suggested-by: Tim Harvey
> Si
ans/u-boot-imx.git
tags/u-boot-imx-master-20240706
for you to fetch changes up to 3d4c29258f8b4c4a5cf4ce79fb1ac80f66e4cf65:
clk: imx: add mux ops for i.MX8M composite clk (2024-07-06 15:40:04 -0300)
u-boot-imx-master-20240706
--
CI: https://source.denx.de/u-boot/custodi
Skip setting parent with dummy fixed-clock. Upstream linux might declare
an additional clock for the mtk timer and that additional clock might
also be a fixed-clock defined in DT. Setting parent of a dummy fixed-clock
resulta in error hence mtk timer fails to probe.
Skip setting parent to permit c
The following changes since commit fd46ea0e701920eb205c2bce9d527bf0dec10b59:
Merge branch '2024-07-05-assorted-updates' (2024-07-05 16:36:43 -0600)
are available in the Git repository at:
git://source.denx.de/u-boot-usb.git master
for you to fetch changes up to 2fc8638403c740e2dffb8d338bb58
This is for master branch .
The following changes since commit 1ebd659cf020843fd8e8ef90d85a66941cbab6ec:
Merge tag 'u-boot-dfu-20240606' of
https://source.denx.de/u-boot/custodians/u-boot-dfu (2024-06-06 08:24:15 -0600)
are available in the Git repository at:
https://source.denx.de/u-boot/
Marek Vasut writes:
>> ...om-overlay-rev100.dts => imx8mp-dhcom-som-overlay-rev100.dtso} | 0
>> 4 files changed, 0 insertions(+), 0 deletions(-)
>> rename arch/arm/dts/{imx8mp-dhcom-pdk-overlay-eth2xfast.dts =>
>> imx8mp-dhcom-pdk-overlay-eth2xfast.dtso} (100%)
>> rename arch/arm/dts/{im
On 05.07.2024 20:56, Peter Robinson wrote:
> Hi Mikhail,
>
>> This series of patches greatly improve TCP support.
> Where's the changelog of what changed from v1?
no changes, just remove some patches and add a cover letter
>
>> The benefits:
>> * a lot of bug was fixed
>> * tcp cliens become
Distinguish more clearly between source files meant for producing .dtb
from those meant for producing .dtbo.
Note that in the linux tree, all device tree overlay sources have been
renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit
81d362732bac). So this is also a step towards st
[equivalent to linux commit 81d362732bac]
As a follow up to the series allowing DTB overlays to built from .dtso
files. Now that all overlays have been renamed, remove the ability to
build from overlays from .dts files to prevent any files with the old
name from accidental being added.
Signed-off
Distinguish more clearly between source files meant for producing .dtb
from those meant for producing .dtbo.
In this case, the files are really meant to be compiled to .dtbo ->
.dtbo.S -> .dtbo.o that get embedded in the image, which means that
the begin/end symbols generated by the makefile rule
This is a followup to the patches that landed in 2024.01 and nearly
made sure that source files for producing .dtbo files use the .dtso
extension. In the same release, a few new .dts files snuck in, and
there was also some test code involving .dtbo -> .dtbo.S -> .dtbo.o I
didn't really know how to
Distinguish more clearly between source files meant for producing .dtb
from those meant for producing .dtbo. No functional change, as we
currently have rules for producing a foo.dtbo from either foo.dts or
foo.dtso.
Note that in the linux tree, all device tree overlay sources have been
renamed to
[linux commit 941214a512d8, modified for U-Boot by removing the
include of vmlinux.lds.h and replacing STRUCT_ALIGNMENT by 16.]
DTB files can be built into the kernel by converting them to assembly
files then assembling them into object files. We extend this here
for DTB overlays with the .dtso ex
25 matches
Mail list logo
