From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: nm@ti.com, u-boot@lists.denx.de, trini@konsulko.com,
sjg@chromium.org, pbrobinson@gmail.com, eballetb@redhat.com,
uboot-imx@nxp.com, jwboyer@redhat.com, kever.yang@rock-chips.com,
heiko@sntech.de
Subject: Re: Request for hosting a boot-firmware repository in u-boot git (denx and GitHub)
Date: Fri, 21 Jun 2024 00:33:49 +0200 [thread overview]
Message-ID: <87msnf2qia.fsf@bloch.sibelius.xs4all.nl> (raw)
In-Reply-To: <a7cca1a2-5ba8-487b-9fce-1553da93c56e@cherry.de> (message from Quentin Schulz on Fri, 21 Jun 2024 00:22:43 +0200)
> Date: Fri, 21 Jun 2024 00:22:43 +0200
> From: Quentin Schulz <quentin.schulz@cherry.de>
Hi Quentin,
> FYI, the DDR bin is printing stuff on the console, so we had to modify
> it (with a tool from Rockchip) to remove the gibberish breaking the
> terminal by setting the appropriate controller, mux and baudrate (for
> our products, there's no one size fits all :) ). The question is how to
> handle this since we cannot realistically store every possible
> permutation of that binary for each UART controller, mux of UART
> controller and baudrate (the only parameters **we** modify, but there
> are tons of others).
To build the RK356x and RK3588 of the u-boot packages on OpenBSD I've
written a small program that changes the baudrate from 1500000 to
115200:
https://github.com/openbsd/ports/blob/master/sysutils/u-boot/rk356x/files/rkbinpatch.c
https://github.com/openbsd/ports/blob/master/sysutils/u-boot/rk3588/files/rkbinpatch.c
This just does the bare minimum and it might break with future changes
to the layout of the binaries. But I don't think it would be
difficult to add a few more parameters.
Cheers,
Mark
next prev parent reply other threads:[~2024-06-20 22:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 21:35 Request for hosting a boot-firmware repository in u-boot git (denx and GitHub) Nishanth Menon
2024-06-20 22:10 ` Peter Robinson
2024-06-21 14:54 ` Bryan Brattlof
2024-06-20 22:22 ` Quentin Schulz
2024-06-20 22:29 ` Peter Robinson
2024-06-21 8:44 ` Quentin Schulz
2024-06-21 8:56 ` Peter Robinson
2024-06-21 8:57 ` Peter Robinson
2024-06-21 9:29 ` Quentin Schulz
2024-06-21 9:37 ` Peter Robinson
2024-06-20 22:33 ` Mark Kettenis [this message]
2024-06-20 23:05 ` Simon Glass
2024-06-21 7:35 ` Peter Robinson
2024-06-21 14:57 ` Simon Glass
2024-06-21 15:35 ` Bryan Brattlof
2024-07-16 19:13 ` Tom Rini
2024-07-16 19:35 ` Heinrich Schuchardt
2024-07-16 20:01 ` Tom Rini
2024-07-16 20:14 ` Heinrich Schuchardt
2024-07-16 21:36 ` Tom Rini
2024-07-17 12:11 ` Nishanth Menon
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=87msnf2qia.fsf@bloch.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=eballetb@redhat.com \
--cc=heiko@sntech.de \
--cc=jwboyer@redhat.com \
--cc=kever.yang@rock-chips.com \
--cc=nm@ti.com \
--cc=pbrobinson@gmail.com \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
/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