Hi Nishanth,
On 06:13-20231006, Nishanth Menon wrote:
> On 09:46-20231006, Manorit Chawdhry wrote:
> > Hi Nishanth,
> >
> > On 06:26-20231005, Nishanth Menon wrote:
> > > On 10:29-20231005, Manorit Chawdhry wrote:
> > > > Hi Nishanth,
> > > >
> > > > On 07:24-20231004, Nishanth Menon wrote:
> >
On 10/8/23 23:36, Simon Glass wrote:
When the SMBIOS table is written to an address above 4GB a 32-bit table
address is not large enough.
Use an SMBIOS3 table in that case.
Signed-off-by: Simon Glass
---
include/smbios.h | 22 +-
lib/smbios.c | 22
Current code allows up to 3 MBR partitions without extended one.
If more than 3 partitions are required, then extended partition(s)
must be used.
This commit allows up to 4 primary MBR partitions without the
need for extended partition.
Add mbr test unit. In order to run the test manually,
On 10/8/23 23:36, Simon Glass wrote:
EFI does not use the 'anchor string' to determine the SMBIOS table
version, instead preferring to have two separate GUIDs. Use the correct
one, depending on the table version.
Signed-off-by: Simon Glass
---
include/efi_api.h | 4
The NanoPC-T6 is a Rockchip RK3588 based SBC by FriendlyElec.
There are four variants depending on the DRAM size: 4G/32GB eMMC,
8G/64GB eMMC, 16G/16MB SPI NOR, and 16G/256GB eMMC/16MB SPI NOR
Specifications:
CPU: Rockchip RK3588, 4x Cortex-A76 (up to 2.4GHz)
+ 4x
On 10/8/23 22:59, Fabio Estevam wrote:
From: Fabio Estevam
Select the USB options to allow running "ums 0 mmc 0".
Signed-off-by: Fabio Estevam
---
Changes since v1:
- Remove unrelated config options. (Marek)
configs/mx28evk_defconfig | 12
1 file changed, 12 insertions(+)
Hi Peter,
On Sun, Oct 08, 2023 at 07:21:57PM +0100, Peter Robinson wrote:
> On Sat, Oct 7, 2023 at 4:55 PM Ben Wolsieffer wrote:
> >
> > Using the unqualified "mmc" boot target causes the Raspberry Pi 4 to
> > fail to boot. c771e5b explains this approach as follows:
> >
> > > We don't need to
Hi Simon,
On Sat, Oct 07, 2023 at 02:18:48PM -0600, Simon Glass wrote:
> Hi Ben,
>
> On Sat, 7 Oct 2023 at 09:55, Ben Wolsieffer wrote:
> >
> > Using the unqualified "mmc" boot target causes the Raspberry Pi 4 to
> > fail to boot. c771e5b explains this approach as follows:
> >
> > > We don't
On 10/1/23 16:52, Andre Przywara wrote:
As the code to switch an ARM core from secure to the non-secure state
needs to know the base address of the Generic Interrupt Controller
(GIC), we read an Arm Cortex defined system register that is supposed to
hold that base address. However there are SoCs
In preparation for adding support for SMBIOS3 move this code into an
else statement. There is no functional change.
Signed-off-by: Simon Glass
---
lib/smbios.c | 38 +-
1 file changed, 21 insertions(+), 17 deletions(-)
diff --git a/lib/smbios.c
When the SMBIOS table is written to an address above 4GB a 32-bit table
address is not large enough.
Use an SMBIOS3 table in that case.
Signed-off-by: Simon Glass
---
include/smbios.h | 22 +-
lib/smbios.c | 22 ++
2 files changed, 39 insertions(+),
All callers handle this alignment, so drop the unnecessary code. This
simplifies things a little.
Signed-off-by: Simon Glass
---
include/smbios.h | 5 +
lib/smbios.c | 2 --
2 files changed, 1 insertion(+), 6 deletions(-)
diff --git a/include/smbios.h b/include/smbios.h
index
EFI does not use the 'anchor string' to determine the SMBIOS table
version, instead preferring to have two separate GUIDs. Use the correct
one, depending on the table version.
Signed-off-by: Simon Glass
---
include/efi_api.h | 4
lib/efi_loader/efi_smbios.c | 12 ++--
2
Move all of this logic into the else clause, since it will not be used
for SMBIOS3
Signed-off-by: Simon Glass
---
lib/smbios.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/lib/smbios.c b/lib/smbios.c
index 96f67cd6ad7b..c7a557bc9b7b 100644
---
When the malloc() region extends beyond 4GB on ARM we may end up with
an SMBIOS table in that region.
Add support for writing an SMBIOS3 table, which supports a 64-bit
address.
Note that this problem does not happen on x86 since it requires the
tables to be placed just below 1MB in memory,
This video covers the basics in a short time, so add a link to it.
Signed-off-by: Simon Glass
---
doc/learn/talks.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/learn/talks.rst b/doc/learn/talks.rst
index 0bb44aeabe55..d65e3b92be1a 100644
--- a/doc/learn/talks.rst
+++
From: Fabio Estevam
Select the USB options to allow running "ums 0 mmc 0".
Signed-off-by: Fabio Estevam
---
Changes since v1:
- Remove unrelated config options. (Marek)
configs/mx28evk_defconfig | 12
1 file changed, 12 insertions(+)
diff --git a/configs/mx28evk_defconfig
From: Fabio Estevam
Since commit 4fcba5d556b4 ("regulator: implement basic reference
counter") the return value of regulator_set_enable() may be EALREADY or
EBUSY for fixed/GPIO regulators.
Switch to using the more relaxed regulator_set_enable_if_allowed() to
continue if regulator already was
From: Fabio Estevam
Use dev_ofnode() to retrieve the USB node pointer from the udevice
structure.
This fixes the following build error:
drivers/usb/host/ehci-mxs.c:143:38: error: 'struct udevice' has no member named
'node_'
Signed-off-by: Fabio Estevam
Reviewed-by: Marek Vasut
---
Changes
Hi Peter,
On Sun, 8 Oct 2023 at 12:02, Peter Robinson wrote:
>
> Hi Simon,
>
> > > So with more testing of 2023.10 in Fedora we found a regression where
> > > the display dies when the vc4 module loads in the kernel. With further
> > > debug it was found that it was due to the new U-Boot and
The NanoPC-T6 is a Rockchip RK3588 based SBC by FriendlyARM.
There are four variants depending on the DRAM size: 4G/32GB eMMC,
8G/64GB eMMC, 16G/16MB SPI NOR, and 16G/256GB eMMC/16MB SPI NOR
Specifications:
CPU: Rockchip RK3588, 4x Cortex-A76 (up to 2.4GHz)
+ 4x
Jonas, thank you for your detailed review. The explanations for each of config
change recommendations were especially helpful.
As for the CFG_IRAM_BASE / BROM_LAST_BOOTSOURCE issue, I have made a step
forward, but expect I will be getting feedback as to a better approach.
Note: This patchset
On Sat, Oct 7, 2023 at 4:55 PM Ben Wolsieffer wrote:
>
> Using the unqualified "mmc" boot target causes the Raspberry Pi 4 to
> fail to boot. c771e5b explains this approach as follows:
>
> > We don't need to specify the mmc devices individually, since they are
> > used in order from 0 to 2, and
Hi Simon,
> > So with more testing of 2023.10 in Fedora we found a regression where
> > the display dies when the vc4 module loads in the kernel. With further
> > debug it was found that it was due to the new U-Boot and with
> > bisecting it myself I have found this series is the cause of the
> >
Display the STMicroelectronics logo with features VIDEO_LOGO and
SPLASH_SCREEN on stm32f469-disco board.
Signed-off-by: Dario Binacchi
---
Changes in v2:
- Add Patrice Chotard's Reviewed-by tag to patches 1, 2 and 3 of the series.
- Fix frame buffer allocation for stm32f469 discovery board.
Add support to Orise Tech OTM8009A display on stm32f469-disco board.
It was necessary to retrieve the framebuffer address from the device tree
because the address returned by the video-uclass driver pointed to a memory
area that was not usable.
Furthermore, unlike Linux, the DSI driver requires
As described in [1], the "clocks" property contains "a phandle to the
clock device node, an index selecting between gated clocks (0) and other
clocks (1), and an index specifying the clock to use." The current version
of the clock driver, unlike the kernel, is currently able to properly
handle
As described in [1], the "clocks" property contains "a phandle to the
clock device node, an index selecting between gated clocks (0) and other
clocks (1), and an index specifying the clock to use." The current version
of the clock driver, unlike the kernel, is currently able to properly
handle
Sync the devicetree with linux 6.5 for stm32f746-disco board.
Signed-off-by: Dario Binacchi
Reviewed-by: Patrice Chotard
---
Changes in v2:
- Add Patrice Chotard's Reviewed-by tag.
arch/arm/dts/stm32f469-disco.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
The series adds support for the Orise Tech OTM8009A display on the
stm32f469-disco board. Substantial differences in the drivers for clock
management, LTDC and DSI compared to Linux, made it necessary to modify
the device tree. These changes were made in stm32f469-disco-uboot.dtsi to
avoid
Hello Patrice,
On Wed, Sep 27, 2023 at 8:19 AM Patrice CHOTARD
wrote:
>
>
>
> On 9/3/23 22:57, Dario Binacchi wrote:
> > Add support to Orise Tech OTM8009A display on stm32f469-disco board.
> >
> > It was necessary to retrieve the framebuffer address from the device tree
> > because the address
Handle 2GBit memory size value "2" from tlv eeprom on ddr
initialisation, to support SoMs with 512MB ddr memory.
Signed-off-by: Josua Mayer
---
board/solidrun/clearfog/clearfog.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/board/solidrun/clearfog/clearfog.c
Extend the existing tlv vendor extension used for ram size by one byte to
also store the number of ddr channels.
The length of the tlv entry can indicate whether the new information is
present. If not default to single channel.
Signed-off-by: Josua Mayer
---
board/solidrun/clearfog/clearfog.c |
This series adds support for additional memory configuration that
were been produced in the past - most notably
a dual-channel configuration with two 512MB modules.
Josua Mayer (2):
arm: mvebu: clearfog: read number of ddr channels from tlv data
arm: mvebu: clearfog: support 512MB memory size
The SelectMAP configuration interface provides an 8-bit,
16-bit or 32-bit bidirectional data bus interface to the Versal FPGA
configuration logic that can be used for both configuration and readback.
A connected microcontoller to the SelectMAP interface can load boot
image with bitstream, TF-A
Armada 388 can boot from either eMMC data, boot0 or boot1 partitions.
data partition requires booting from LBA-4096 to avoid conflict with
MBR. When booting from boot0/boot1 environment should be stored there
respectively, too.
Add 3 new defconfigs, for each eMMC partition:
-
Disarm the error message forcing u-boot/spl image to be located at
sector 0 on eMMC data-partition and microSD.
Offset 0 makes sense on eMMC boot partitions only, data partition must
use 4096 to avoid conflicting with MBR.
Valid offsets when booting from microSD, reported by boot-rom v1.73:
A38x bootrom only searches 2 sectors when booting from eMMC,
irregardless of data or boot partition: 0 & 4096.
For eMMC boot partitions sector 0 is fine, but on data partition it
conflicts with MBR.
Change bubt command default to 4096 for eMMC data partition only, to
allow using an MBR partition
On Armada 388 booting from eMMC is different to SD-Card in two major ways:
- Environment location
- Sectors scanned by Boot-ROM
This patchset first makes it possible to select offset 4096 for
eMMC partition. Here U-Boot can be placed to avoid conflict
conflict with MBR.
Secondly the bubt
In commit fd6e425, Jonas finds the rock-5b device has a value of 6 at
CFG_IRAM_BASE + 0x10 (0xff10) when booted from spi and creates the
BROM_BOOTSOURCE_SPINOR_RK3588 enum value.
https://github.com/u-boot/u-boot/commit/fd6e425be243dce518a02710482514faccf3c211
When I boot the nanopv-t6 from
On 2023/10/8 05:25, John Clark wrote:
NanoPC-T6 is a Rockchip RK3588 based SBC by FriendlyElec.
There are four variants depending on the DRAM size: 4G/32GB eMMC, 8G/64GB eMMC,
16G/16MB SPI NOR, and 16G/256GB eMMC/16MB SPI NOR
So the board is using SPI NOR flash.
[...]
diff --git
Hi John,
Quick feedback below, will look at schematics and runtime test later.
On 2023-10-07 23:25, John Clark wrote:
> NanoPC-T6 is a Rockchip RK3588 based SBC by FriendlyElec.
>
> There are four variants depending on the DRAM size: 4G/32GB eMMC, 8G/64GB
> eMMC,
> 16G/16MB SPI NOR, and
Hi Kever,
On 2023-10-08 03:13, Kever Yang wrote:
> Hi Jonas,
>
> On 2023/10/7 18:37, Jonas Karlman wrote:
>> Hi Kever,
>>
>> Looks like the following patch is missing:
>>
>> [v2,7/7] rockchip: rk3568-radxa-e25: Enable pcie3x1 node
>> https://patchwork.ozlabs.org/patch/1816145/
>
> This patch
43 matches
Mail list logo
