From: Mehmet Fide <mehmet.fide@gmail.com>
To: u-boot@lists.u-boot-project.org
Cc: Tom Rini <trini@konsulko.com>,
Francesco Dolcini <francesco@dolcini.it>,
Stefano Babic <sbabic@nabladev.com>,
Fabio Estevam <festevam@gmail.com>,
Franz Schnyder <franz.schnyder@toradex.com>,
Stefan Agner <stefan@agner.ch>,
Mehmet Fide <mehmet.fide@screeningeagle.com>
Subject: [PATCH 0/2] colibri_vf: fix NAND boot and add the board documentation
Date: Thu, 13 Aug 2026 17:07:24 +0200 [thread overview]
Message-ID: <20260813150726.2184452-1-mehmet.fide@gmail.com> (raw)
From: Mehmet Fide <mehmet.fide@screeningeagle.com>
Following the CONFIG_TEXT_BASE report [1] and Francesco's suggestion,
two patches: the first restores the text base the Vybrid BootROM
actually accepts, measured on hardware both through the BootROM NAND
path and the WinCE-era loader; the second adds the missing
doc/board/toradex page for the Colibri VF50/VF61.
[1] https://lore.kernel.org/u-boot/20260806124816.262259-1-mehmet.fide@gmail.com/
Mehmet Fide (2):
colibri_vf: restore the pre-2017 text base, the BootROM refuses the
low one
doc: board: toradex: add the Colibri VF50/VF61 page
configs/colibri_vf_defconfig | 4 +-
doc/board/toradex/colibri_vf.rst | 70 ++++++++++++++++++++++++++++++++
doc/board/toradex/index.rst | 1 +
3 files changed, 73 insertions(+), 2 deletions(-)
create mode 100644 doc/board/toradex/colibri_vf.rst
--
2.54.0
next reply other threads:[~2026-08-13 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 15:07 Mehmet Fide [this message]
2026-08-13 15:07 ` [PATCH 1/2] colibri_vf: restore the pre-2017 text base, the BootROM refuses the low one Mehmet Fide
2026-08-14 7:19 ` Francesco Dolcini
2026-08-14 8:17 ` Mehmet Fide
2026-08-13 15:07 ` [PATCH 2/2] doc: board: toradex: add the Colibri VF50/VF61 page Mehmet Fide
2026-08-14 7:23 ` Francesco Dolcini
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=20260813150726.2184452-1-mehmet.fide@gmail.com \
--to=mehmet.fide@gmail.com \
--cc=festevam@gmail.com \
--cc=francesco@dolcini.it \
--cc=franz.schnyder@toradex.com \
--cc=mehmet.fide@screeningeagle.com \
--cc=sbabic@nabladev.com \
--cc=stefan@agner.ch \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.