On Fri, Feb 16, 2024 at 10:31:20AM +0530, Sahaj Sarup wrote:
> On a verdin-imx8mp platform I am now unable to use the ethernet ports.
I believe it's a known regression, we are currently working on a fix.
See
https://lore.kernel.org/all/e40ed93bd8f371ec56b8fc451dcb458f3ce6dcba.ca...@toradex.com/
Hi Andrew
On 14/02/24 22:00, Andrew Davis wrote:
The address we load TF-A and OP-TEE to is configurable by Kconfig
CONFIG_K3_{ATF,OPTEE}_LOAD_ADDR, but the DT nodes reserving this memory
are often statically defined. As these binaries are dynamically loadable,
and in the case of OP-TEE may not
Hi,
On a verdin-imx8mp platform I am now unable to use the ethernet ports.
My last build was from December
(8f5043ee6d378d7c10d947cf48b047a5954ef5b3) so it was working fine
then.
Boot log:
```
U-Boot SPL 2024.04-rc2-2-gbef352dd57-dirty (Feb 16 2024 - 10:07:17 +0530)
Training FAILED
DDR
On 14/02/24 22:00, Andrew Davis wrote:
Much like we have for ATF, OP-TEE has a standard address that we load
it too and run it from. Add a Kconfig item for this to remove some
hard-coding and allow this address to be more easily changed.
Signed-off-by: Andrew Davis
---
Hi Andrew
On 14/02/24 22:00, Andrew Davis wrote:
There is a default ATF load address that is used for devices that have
ATF running in SRAM. For AM62 and AM62a, ATF runs from DRAM. Instead
of having to override the address in every defconfig, make add a
default for these ATF in DRAM devices.
Hi all,
Since commit f8cebb4f789c9950caf55a0b73e88049e7a1c3a3 enabled LTO by
default for imx8m platforms,
I have been having issues building u-boot.
I am primarily working on imx8mp instead of imx8mm platforms so the
bug resolved by that commit doesn't affect me yet.
But I guess it's a generic
Am 16. Februar 2024 00:25:34 MEZ schrieb Mark Kettenis :
>Moving the efi_carve_out_dt_rsv() call in commit 1be415b21b2d
>("efi_loader: create memory reservations in ACPI case")
>broke boards that create additional memory reservations in
>ft_board_setup() since it is now called before those
Moving the efi_carve_out_dt_rsv() call in commit 1be415b21b2d
("efi_loader: create memory reservations in ACPI case")
broke boards that create additional memory reservations in
ft_board_setup() since it is now called before those additional
memory reservations are made. This is the case for the
Am 15. Februar 2024 23:00:32 MEZ schrieb Tom Rini :
>On Thu, Feb 15, 2024 at 10:53:59PM +0100, Heinrich Schuchardt wrote:
>>
>>
>> Am 15. Februar 2024 22:28:24 MEZ schrieb Tom Rini :
>> >On Thu, Feb 15, 2024 at 10:24:40PM +0100, Heinrich Schuchardt wrote:
>> >>
>> >>
>> >> Am 15. Februar
On Thu, Feb 15, 2024 at 10:53:59PM +0100, Heinrich Schuchardt wrote:
>
>
> Am 15. Februar 2024 22:28:24 MEZ schrieb Tom Rini :
> >On Thu, Feb 15, 2024 at 10:24:40PM +0100, Heinrich Schuchardt wrote:
> >>
> >>
> >> Am 15. Februar 2024 22:10:25 MEZ schrieb Tom Rini :
> >> >The first big issue is
Am 15. Februar 2024 22:28:24 MEZ schrieb Tom Rini :
>On Thu, Feb 15, 2024 at 10:24:40PM +0100, Heinrich Schuchardt wrote:
>>
>>
>> Am 15. Februar 2024 22:10:25 MEZ schrieb Tom Rini :
>> >The first big issue is that the "gcc" file talked a lot about the
>> >general build requirements as well,
On Thu, Feb 15, 2024 at 10:24:40PM +0100, Heinrich Schuchardt wrote:
>
>
> Am 15. Februar 2024 22:10:25 MEZ schrieb Tom Rini :
> >The first big issue is that the "gcc" file talked a lot about the
> >general build requirements as well, but was titled in a gcc-centric
> >manner. Solve this by
Am 15. Februar 2024 22:10:25 MEZ schrieb Tom Rini :
>The first big issue is that the "gcc" file talked a lot about the
>general build requirements as well, but was titled in a gcc-centric
>manner. Solve this by renaming the file to compile.rst and more fully
>reflecting that it is general build
First, since this document was written the biggest challenges at the
time are simply not applicable anymore. Second, we need to list the
challenges which are preventing more platforms from being able to be
built with Clang today. Next, we update the general wording to be host
distribution
The first big issue is that the "gcc" file talked a lot about the
general build requirements as well, but was titled in a gcc-centric
manner. Solve this by renaming the file to compile.rst and more fully
reflecting that it is general build instructions. Next, add a section
about the prebuilt
Drop the U-Boot specific dragonboard820c.dts file in favour of the
upstream apq8096-db820c.dts and an additional -u-boot.dtsi with the
U-Boot specific additions.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/Makefile |
Add drivers and DTS files, as well as regex matches for
qcom/qualcomm/snapdragon.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
MAINTAINERS | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index
Drop the U-Boot specific DTS in favour of upstream. We'll only include
the -4000 variant as that is what U-Boot already supported.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/Makefile|2 +-
Drop the U-Boot specific dragonboard410c.dts in favour of the upstream
msm8916-sbc.dts. No additional changes are needed to this DTS for U-Boot
support.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/Makefile |2 +-
Import dt-binding headers for MSM8996/APQ8096 from Linux.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
include/dt-bindings/clock/qcom,gcc-msm8996.h | 362 +
include/dt-bindings/clock/qcom,mmcc-msm8996.h | 295
Import the headers needed for QCS404-evb.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
include/dt-bindings/clock/qcom,turingcc-qcs404.h | 15 +++
1 file changed, 15 insertions(+)
diff --git
Don't use hardcoded clock IDs, use the IDs from the dt-bindings to be
compatible with upstream.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/dragonboard820c.dts | 5 +++--
drivers/clk/qcom/clock-apq8096.c | 5 +++--
2 files changed, 6
Import the dt-bindings headers in preparation for switching to upstream
DTS for MSM8916.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
include/dt-bindings/arm/coresight-cti-dt.h | 37 +
include/dt-bindings/clock/qcom,rpmcc.h | 174
Import PM8994 and PMI8994 DTSI files in preparation for switching
MSM8996 boards to upstream DTS.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/pm8994.dtsi | 152 ++
arch/arm/dts/pmi8994.dtsi
This board is entirely supported by the generic arch code and DTS. The
board code used to handle turning on the vbus regulator, however this is
now handled via DT.
With this, the board specific defconfig is also no longer needed, so
drop it as well.
Reviewed-by: Neil Armstrong
Signed-off-by:
The MSM8916/APQ8016 Technical Reference Manual is publicly available and
contains a lot of useful register maps for many core parts of the SoC.
Include an archive.org link to it in the dragonboard410c documentation.
Signed-off-by: Caleb Connolly
---
doc/board/qualcomm/dragonboard410c.rst | 2 ++
Import the supporting pm8916.dtsi and msm8916-pm8916.dtsi files from
upstream in preparation for switching boards over.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/msm8916-pm8916.dtsi | 157 ++
Replace the board specific docs with a generic board.rst file which
documents the build/boot process for the sdm845 and qcs404 boards now
that the only differences are the DTB in use.
At the same time, create a debugging page to document some useful
snippets and tips for working with Qualcomm
On Qualcomm platforms, the TZ may already have certain memory regions
under protection by the time U-Boot starts. There is a rare case on some
platforms where the prefetcher might speculatively access one of these
regions resulting in a board crash (TZ traps and then resets the board).
We
Import the DT bindings headers that are used by SDM845 from Linux.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
include/dt-bindings/clock/qcom,camcc-sdm845.h | 116 ++
include/dt-bindings/clock/qcom,dispcc-sdm845.h | 56 +++
Import the PM8998 and PMI8998 PMIC DTSI files from Linux as well
as the common audio codec in preperation for replacing board DTS files
with upstream.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/pm8998.dtsi | 130
Use the root compatible strings from upstream Linux, add missing
'#clock-cells' property to the gcc node.
Adjust some of the msm8916/apq8016 drivers to use the correct upstream
compatible properties and DT bindings.
This prepares us to switch to upstream DT in a future patch.
Reviewed-by: Neil
With just a few basic rules, we can generate the $fdtfile environment
variable to match the format used in Linux. This uses the root
compatible property inside u-boot, with specific handling for the
Dragonboard845c which is a special case, and for the qrb robotics
boards.
This is known to work on
db820c predated support for prepending the kernel image header
automatically, drop it's custom linker script and head.S in favour of
this generic support.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/mach-snapdragon/Kconfig | 1 +
Introduce a basic pinctrl driver for the SPMI PMIC GPIOs. This is
necessary to make proper use of upstream DT bindings specifically on the
dragonboard410c where they're used to switch between USB host and device
modes.
Only support for driving the pins as output low or high is enabled for
now.
Heavily inspired by Apple board code. Use the LMB allocator to configure
load addresses at runtime, and implement a lookup table for selecting a
devicetree.
As some Qualcomm RBx boards have different RAM capacities and base
addresses, it isn't possible to hardcode these regions.
Signed-off-by:
We should be returning the rate that we set the clock to, drivers like
MMC rely on this. So fix it.
Signed-off-by: Caleb Connolly
---
drivers/clk/qcom/clock-qcs404.c | 25 +
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/drivers/clk/qcom/clock-qcs404.c
On the DB410c we support running as a first stage bootloader. This
requires initialising the GPIOs which are muxed to UART before they can
be used. Add DM_FLAG_PRE_RELOC to the apq8016 pinctrl driver to ensure
that we do this early enough.
This is required to prevent the first few lines of UART
Historically, Qualcomm boards have relied on heavy hardcoding in U-Boot,
in many cases to the specific SoC but also to the board itself (e.g.
memory map). This has been largely resolved by modernising the Qualcomm
drivers in U-Boot, however the board code still largely follows this
model.
This
Upstream devicetrees label GPIOs with "gpioX", not "GPIO_X", fix this
for SoCs where we're now using upstream DT.
Signed-off-by: Caleb Connolly
---
drivers/pinctrl/qcom/pinctrl-apq8016.c | 26 +++
drivers/pinctrl/qcom/pinctrl-apq8096.c | 16 +-
Some platforms hard reset when attempting to configure PMIC GPIOs. Add
support for quirks specified in match data with a single quirk to skip
this configuration. We rely on the GPIO already be configured correctly,
which is always the case for volume up (the only current user of these
GPIOs).
Some of the db410c board support code was written to be generic and
placed in mach-snapdragon. However, as the db410c is the only board
using this, move the code out of mach-snapdragon. This makes is more
obvious what code is relevant for which targets and helps tidy things up
a little more.
Add support for a vbus-supply regulator specified in devicetree. This
provides generic support to avoid hardcoded GPIO configuration in board
init code.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
This patch has no dependencies
Cc: Marek Vasut
---
Add a config fragment for building U-Boot such that it can be
chainloaded by aboot/LK rather than being flashed directly to the aboot
partition.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
board/qualcomm/dragonboard410c/configs/chainloaded.config | 7 +++
1 file changed,
Use the modern helpers to fetch the clock and use the correct property
("clocks" instead of "clock"). Drop the call to pinctrl_select_state()
as no boards have a "uart" pinctrl state and this prints confusing
errors.
Signed-off-by: Caleb Connolly
---
arch/arm/dts/dragonboard410c.dts | 3 ++-
Most platforms have a handful of "special" GPIOs, like the MMC
clock/data lanes, UFS reset, etc. These don't follow the usually naming
scheme of "gpioX" and also have unique capabilities and registers. We
can get away without supporting them all for now, but DT compatibility
is still an issue.
Adjust the DT to match upstream bindings.
Signed-off-by: Caleb Connolly
---
arch/sandbox/dts/sandbox.dtsi | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/arch/sandbox/dts/sandbox.dtsi b/arch/sandbox/dts/sandbox.dtsi
index 241f397ba6e7..c93ce7128942 100644
---
Qualcomm PMICs number their GPIOs starting from 1, implement a custom
.xlate method to handle this.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
drivers/gpio/qcom_pmic_gpio.c | 22 ++
1 file changed, 22 insertions(+)
diff --git
Use the clk_* helper functions and the correct property name for clocks.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
drivers/mmc/msm_sdhci.c | 69 +
1 file changed, 47 insertions(+), 22 deletions(-)
diff --git
Introduce support for early debugging. This relies on the previous stage
bootloader to initialise the UART clocks, when running with U-Boot as
the primary bootloader this feature doesn't work. It will require a way
to configure the clocks before the driver model is available.
Signed-off-by: Caleb
When booting U-Boot on board with a locked down first-stage bootloader,
we emulate the Linux boot header. By passing the U-Boot FDT through this
first-stage bootloader and retrieving it afterwards we can pre-populate
the memory nodes and other info like the KASLR address.
Add a function to export
Historically, Qualcomm boards in U-Boot have all had their own
board/qualcomm/xyz directory, their own CONFIG_TARGET_XYZ option, their
own hardcoded sysmap-xyz.c file, and their own U-Boot specific
devicetree with little/no compatibility with upstream DT.
This series makes a few final prepatory
Adjust the apq8016 and apq8096 drivers to use the upstream compatible
properties, and adjust the associated dts files in U-Boot.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/dragonboard410c.dts | 2 +-
drivers/clk/qcom/clock-apq8016.c | 2 +-
The upstream DT is supported here, so drop the U-Boot specific binding
docs.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
doc/device-tree-bindings/mmc/msm_sdhci.txt | 25 -
1 file changed, 25 deletions(-)
diff --git
On Fri, Jan 19, 2024 at 11:20:43PM +0530, Apurva Nandan wrote:
> TI K3 J784S4 and AM69 are new additions to the K3 SoC family.
> Add documentation about the J784S4 EVM and AM69 SK.
>
> Signed-off-by: Dasnavis Sabiya
> Signed-off-by: Apurva Nandan
> ---
> board/ti/j784s4/MAINTAINERS | 1 +
>
On 2/15/24 2:06 AM, Francesco Dolcini wrote:
Hello Andrew,
thanks for this series.
On Wed, Feb 14, 2024 at 10:30:09AM -0600, Andrew Davis wrote:
The current address of TF-A in DRAM is just below the 512MB address line.
This means if the DRAM in a system is 512MB then TF-A is right at the
end
On 2/15/24 14:31, Sean Anderson wrote:
> On 2/15/24 14:08, Michal Simek wrote:
>>
>>
>> On 2/15/24 18:19, Sean Anderson wrote:
>>> Currently, when we boot from JTAG we try to boot U-Boot from RAM.
>>> However, this is a bit tricky to time, since the debugger has to wait
>>> for SPL to initialize
On 2/15/24 14:08, Michal Simek wrote:
>
>
> On 2/15/24 18:19, Sean Anderson wrote:
>> Currently, when we boot from JTAG we try to boot U-Boot from RAM.
>> However, this is a bit tricky to time, since the debugger has to wait
>> for SPL to initialize RAM before it can load U-Boot. This can result
On 2/15/24 18:19, Sean Anderson wrote:
Currently, when we boot from JTAG we try to boot U-Boot from RAM.
However, this is a bit tricky to time, since the debugger has to wait
for SPL to initialize RAM before it can load U-Boot. This can result in
long waits, since occasionally initializing
Currently, when we boot from JTAG we try to boot U-Boot from RAM.
However, this is a bit tricky to time, since the debugger has to wait
for SPL to initialize RAM before it can load U-Boot. This can result in
long waits, since occasionally initializing RAM (and other things in
psu_init) takes a
.04-rc2 (2024-02-13 18:16:57 -0500)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/custodians/u-boot-dfu.git
> tags/u-boot-dfu-20240215
>
> for you to fetch changes up to e2f6270f2da844d598555702d3af4f2e3fae3f9f:
>
> doc: android:
A RNG driver for Armada 3720 boards running the Turris Mox rWTM firmware
from CZ.NIC in the secure processor.
Signed-off-by: Max Resch
---
Changes in v5:
- check return code turris_rwtm_rng_fill_entropy
- remove empty line
Changes in v4:
- wrongful/missing git rebase
Changes in v3:
- More
On Thu, 15 Feb 2024 17:56:10 +0100
Frieder Schrempf wrote:
Hi Frieder,
> On 15.02.24 17:50, Andre Przywara wrote:
> > On Thu, 15 Feb 2024 14:35:19 +0100
> > Frieder Schrempf wrote:
> >
> >> From: Frieder Schrempf
> >>
> >> The datasheet can be found here:
> >>
Don't define checksum algos when the underlying hashes are not enabled.
This allows disabling these hashes in SPL (or U-Boot).
Fixes: d16b38f4270 ("Add support for SHA384 and SHA512")
Fixes: 646257d1f40 ("rsa: add sha256-rsa2048 algorithm")
Signed-off-by: Sean Anderson
---
boot/image-sig.c | 8
Hello Frieder,
On 2024-02-15 17:56, Frieder Schrempf wrote:
On 15.02.24 17:50, Andre Przywara wrote:
On Thu, 15 Feb 2024 14:35:19 +0100
Frieder Schrempf wrote:
From: Frieder Schrempf
The datasheet can be found here:
https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/EN25Q80B_Ver.E.pdf
Hi Andre,
On 15.02.24 17:50, Andre Przywara wrote:
> On Thu, 15 Feb 2024 14:35:19 +0100
> Frieder Schrempf wrote:
>
>> From: Frieder Schrempf
>>
>> The datasheet can be found here:
>> https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/EN25Q80B_Ver.E.pdf
>>
>> Signed-off-by: Frieder Schrempf
On Thu, 15 Feb 2024 14:35:19 +0100
Frieder Schrempf wrote:
> From: Frieder Schrempf
>
> The datasheet can be found here:
> https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/EN25Q80B_Ver.E.pdf
>
> Signed-off-by: Frieder Schrempf
> Reviewed-by: Fabio Estevam
> ---
> Changes in v3:
> * none
-20240215
for you to fetch changes up to e2f6270f2da844d598555702d3af4f2e3fae3f9f:
doc: android: avb: sync usage details (2024-02-15 10:38:34 +0100)
u-boot-dfu-20240215
- Fix avb_verify command with SD cards
- Add u-boot-dfu maintainer
On 2/12/24 08:47, Sughosh Ganu wrote:
The version 2 of the FWU metadata allows for appending opaque vendor
specific data to the metadata structure. Add support for appending
this data to the metadata. The vendor specific data needs to be
provided through a file, passed through a command-line
Hi,
On 2/12/24 08:47, Sughosh Ganu wrote:
Migrate the metadata generation tool to generate the version 2
metadata.
Signed-off-by: Sughosh Ganu
---
Changes since V1:
* Compute location of struct fwu_fw_store_desc using pointer
arithmetic.
tools/mkfwumdata.c | 45
On 2024-02-15 14:13, Tom Rini wrote:
On Wed, Feb 14, 2024 at 04:48:52AM +0100, Dragan Simic wrote:
On 2024-02-06 12:00, Dragan Simic wrote:
> Prevent the error messages produced by which(1), such as the one quoted
> below, from being visible in the build outputs.
>
> which: no dtc in
Hi Heinrich,
thanks for your comments. I fixed all these issues in v4.
On 15.02.24 14:53, Heinrich Schuchardt wrote:
> On 15.02.24 2:35 PM, Frieder Schrempf wrote:
>> From: Frieder Schrempf
>>
>> Describe how to build and boot for the Sielaff i.MX6 Solo board.
>>
>> Signed-off-by: Frieder
On Thu, Feb 15, 2024 at 02:53:12PM +0100, Heinrich Schuchardt wrote:
> On 15.02.24 2:35 PM, Frieder Schrempf wrote:
> > From: Frieder Schrempf
> >
> > Describe how to build and boot for the Sielaff i.MX6 Solo board.
> >
> > Signed-off-by: Frieder Schrempf
[snip]
> > +Build U-Boot
> >
From: Frieder Schrempf
Describe how to build and boot for the Sielaff i.MX6 Solo board.
Signed-off-by: Frieder Schrempf
---
Changes in v4:
* changes requested by Heinrich (thanks!)
Changes in v3:
* include docs in upper-level index
Changes in v2:
* none
---
doc/board/index.rst
From: Frieder Schrempf
The Sielaff i.MX6 Solo board is a control and HMI board for vending
machines. Add support for this board.
The devicetree files are taken from pending changes in the Linux
kernel that are available from linux-next and will likely be
part of Linux v6.9.
Signed-off-by:
From: Frieder Schrempf
The datasheet can be found here:
https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/EN25Q80B_Ver.E.pdf
Signed-off-by: Frieder Schrempf
Reviewed-by: Fabio Estevam
---
Changes in v4:
* none
Changes in v3:
* none
Changes in v2:
* Add R-b tag from Fabio (Thanks!)
---
On 15.02.24 2:35 PM, Frieder Schrempf wrote:
From: Frieder Schrempf
Describe how to build and boot for the Sielaff i.MX6 Solo board.
Signed-off-by: Frieder Schrempf
---
Changes in v3:
* include docs in upper-level index
Changes in v2:
* none
---
doc/board/index.rst | 1 +
On 15.02.24 13:27, Fabio Estevam wrote:
> Hi Frieder,
>
> On Tue, Feb 13, 2024 at 2:22 PM Frieder Schrempf wrote:
>>
>> From: Frieder Schrempf
>>
>> The Sielaff i.MX6 Solo board is a control and HMI board for vending
>> machines. Add support for this board.
>>
>> The devicetree files are taken
From: Frieder Schrempf
Describe how to build and boot for the Sielaff i.MX6 Solo board.
Signed-off-by: Frieder Schrempf
---
Changes in v3:
* include docs in upper-level index
Changes in v2:
* none
---
doc/board/index.rst | 1 +
doc/board/sielaff/imx6dl-sielaff.rst | 32
From: Frieder Schrempf
The Sielaff i.MX6 Solo board is a control and HMI board for vending
machines. Add support for this board.
The devicetree files are taken from pending changes in the Linux
kernel that are available from linux-next and will likely be
part of Linux v6.9.
Signed-off-by:
From: Frieder Schrempf
The datasheet can be found here:
https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/EN25Q80B_Ver.E.pdf
Signed-off-by: Frieder Schrempf
Reviewed-by: Fabio Estevam
---
Changes in v3:
* none
Changes in v2:
* Add R-b tag from Fabio (Thanks!)
---
On Sun, Jan 21, 2024 at 10:17:22AM -0500, Tom Rini wrote:
> On Sun, Jan 21, 2024 at 03:42:16PM +0100, Heinrich Schuchardt wrote:
> > Hello Tom,
> >
> > as we have started to generate ACPI tables in U-Boot we should request an
> > ACPI vendor ID for the U-Boot project.
> >
> > As described in
On Tue, Feb 13, 2024 at 08:43:42AM -0300, Fabio Estevam wrote:
>
> From: Fabio Estevam
>
> There is no imx8mp-msc-sm2s.dtb file in upstream Linux.
>
> Change it to imx8mp-msc-sm2s-ep1.dtb.
>
> Signed-off-by: Fabio Estevam
Reviewed-by: Ian Ray
> ---
> configs/msc_sm2s_imx8mp_defconfig | 2
On Tue, Feb 13, 2024 at 08:43:40AM -0300, Fabio Estevam wrote:
>
> From: Fabio Estevam
>
> Add mmc alias so that the eMMC is mmc0 and the SD card
> is mmc1 to have a well defined device numbering scheme.
>
> Signed-off-by: Fabio Estevam
Reviewed-by: Ian Ray
> ---
>
On Tue, Feb 13, 2024 at 08:43:41AM -0300, Fabio Estevam wrote:
>
> From: Fabio Estevam
>
> Redundant environment support is required for software updates.
>
> Add support for it.
>
> Signed-off-by: Fabio Estevam
Reviewed-by: Ian Ray
> ---
> configs/msc_sm2s_imx8mp_defconfig | 6 +-
>
On Tue, Feb 13, 2024 at 08:43:38AM -0300, Fabio Estevam wrote:
>
> From: Fabio Estevam
>
> The conversion to DM_SERIAL is mandatory, so do the conversion.
>
> Signed-off-by: Fabio Estevam
Reviewed-by: Ian Ray
> ---
> arch/arm/dts/imx8mp-msc-sm2s-u-boot.dtsi | 8
>
On Tue, Feb 13, 2024 at 08:43:39AM -0300, Fabio Estevam wrote:
>
> From: Fabio Estevam
>
> Currently, the Ethernet ports are not working.
>
> The Ethernet PHY reset lines are controlled by the TCA6424 I2C GPIO
> expander.
>
> The TCA6424 I2C GPIO expander is supported by the CONFIG_DM_PCA953X
On Wed, Feb 14, 2024 at 04:59:52PM +0100, Michal Simek wrote:
> Hi Tom,
>
> please pull these patches to your branch. Most of them are related to device
> tree and aligning with the latest dt schema for SR certification.
> CI is not reporting any issue too.
>
> Thanks,
> Michal
>
>
> The
On Wed, Feb 14, 2024 at 04:48:52AM +0100, Dragan Simic wrote:
> On 2024-02-06 12:00, Dragan Simic wrote:
> > Prevent the error messages produced by which(1), such as the one quoted
> > below, from being visible in the build outputs.
> >
> > which: no dtc in (./scripts/dtc)
> >
> > This makes
Hi Andy,
On 2/15/24 12:55, Andy Yan wrote:
[You don't often get email from andys...@163.com. Learn why this is important
at https://aka.ms/LearnAboutSenderIdentification ]
Hi Quentin：
At 2024-02-15 18:40:25, "Quentin Schulz"
wrote:
Hi Andy,
On 2/15/24 11:35, Andy Yan wrote:
[...]
diff
Hi Frieder,
On Tue, Feb 13, 2024 at 2:22 PM Frieder Schrempf wrote:
>
> From: Frieder Schrempf
>
> The Sielaff i.MX6 Solo board is a control and HMI board for vending
> machines. Add support for this board.
>
> The devicetree files are taken from pending changes in the Linux
> kernel that are
Hi Quentin：
At 2024-02-15 18:40:25, "Quentin Schulz"
wrote:
>Hi Andy,
>
>On 2/15/24 11:35, Andy Yan wrote:
>[...]
diff --git a/configs/coolpi-4b-rk3588s_defconfig
b/configs/coolpi-4b-rk3588s_defconfig
new file mode 100644
index 00..3e3e5abc86
--- /dev/null
Hello,
I am working on the secure boot for raspberry pi topic as described here
https://github.com/raspberrypi/usbboot/tree/master?tab=readme-ov-file#secure-boot---image-creation
The
boot.img file contains u-boot.bin, config.txt, boot.scr, Image, DTB and
other raspberry pi necessary files.
But
Hi all,
I seem to be running into a double free error with
ubi_volume_desc/ubi_close_volume during a ubifsmount/ubifsload/ubifsumount
sequence.
This is the sequence that I'm seeing:
ubifsmount
- do_ubifs_mount
- cmd_ubifs_mount
- uboot_ubifs_mount
- ubifs_mount
- open_ubi
Hi all,
I seem to be running into a double free error with
ubi_volume_desc/ubi_close_volume during a ubifsmount/ubifsload/ubifsumount
sequence.
This is the sequence that I'm seeing:
ubifsmount
- do_ubifs_mount
- cmd_ubifs_mount
- uboot_ubifs_mount
- ubifs_mount
- open_ubi
Hello.
I am bringing up a new am335x platform and need splash screen support. I
already wrote new backlight and LCD panel Linux drivers for the platform.
The kernel side is solid. I brought the device tree and backlight driver
from the kernel and put it into v2023.04 U-Boot. Currently getting a
Hi Andy,
On 2/15/24 11:35, Andy Yan wrote:
[...]
diff --git a/configs/coolpi-4b-rk3588s_defconfig
b/configs/coolpi-4b-rk3588s_defconfig
new file mode 100644
index 00..3e3e5abc86
--- /dev/null
+++ b/configs/coolpi-4b-rk3588s_defconfig
@@ -0,0 +1,105 @@
+CONFIG_ARM=y
At 2024-02-14 22:13:08, "Quentin Schulz"
wrote:
>Hi Andy,
>
>On 2/14/24 10:31, Andy Yan wrote:
>> [You don't often get email from andys...@163.com. Learn why this is
>> important at https://aka.ms/LearnAboutSenderIdentification ]
>>
>> CoolPi 4B is a rk3588s based SBC.
>>
>> Specification:
Hi Igor,
Thank you for the patch.
On mer., févr. 14, 2024 at 19:34, Igor Opaniuk
wrote:
> Support CMD_OPTEE_RPMB for SANDBOX configurations.
> Test:
>
> $ ./u-boot -d arch/sandbox/dts/test.dtb
> ...
> => optee_rpmb write_pvalue test_variable test_value
> Wrote 11 bytes
> => optee_rpmb
On jeu., févr. 01, 2024 at 12:20, Alexey Romanov
wrote:
> An example of how we use fastboot oeam board subcommand
> for Sean Anderson.
>
> 1 - OEM_BOARD_WRITE_BOOTLOADER_CMD:
>
> We use it for custom Amlogic bootloader + tpl
> flashing protocol.
>
> 2 - OEM_BOARD_ERASE_CMD:
>
> Custom logic for
1 - 100 of 103 matches
Mail list logo
