Hi Henrik,
> -Original Message-
> From: Henrik Grimler
> Sent: Saturday, March 11, 2023 7:32 PM
> To: Jaehoon Chung
> Cc: jo...@diskos.nl; peng@nxp.com; andy...@sony.com; s...@chromium.org;
> u-boot@lists.denx.de;
> ~postmarketos/upstream...@lists.sr.ht
> Subject: Re: [PATCH 1/2] Re
Hi,
> -Original Message-
> From: Tom Rini
> Sent: Saturday, March 11, 2023 3:09 AM
> To: Marek Vasut
> Cc: Jaehoon Chung ; U-Boot Mailing List
> ; Loic Poulain
> ; Stefan Roese ; Jae hoon Chung
>
> Subject: Re: [GIT PULL] Please pull u-boot-mmc master
>
> On Fri, Mar 10, 2023 at 05:2
On Sun, Mar 12, 2023 at 3:35 AM Simon Glass wrote:
>
> Bring in some U-Boot additions
>
> This seems to build OK, but 'make menuconfig' does not build the
> scripts/kconfig/mconf utility.
>
> Signed-off-by: Simon Glass
> ---
>
> scripts/kconfig/Makefile | 10 ++
> 1 file changed, 10 inse
On Sun, Mar 12, 2023 at 8:05 AM Simon Glass wrote:
>
> Bring in this code wholesale, replacing the old U-Boot code.
>
> Signed-off-by: Simon Glass
> ---
>
> scripts/kconfig/.gitignore| 20 +-
> scripts/kconfig/Makefile | 211 ++--
> scripts/kconfig/con
It's useful to enable Debug UART for future DM Serial regression tests
for Kirkwood boards.
Also, see background discussion in this thread:
https://lists.denx.de/pipermail/u-boot/2023-March/512010.html
Signed-off-by: Tony Dinh
---
configs/nsa310s_defconfig | 4
1 file changed, 4 insertion
The original function was only called once, before relocation. The new
one is called again after relocation. This was not the intend of the
original call. Fix this by renaming and updating the calling logic.
With this, chromebook_link64 makes it through SPL.
Fixes: 7fe32b3442f ("event: Convert ar
Move MTRR-listing code into a common file so it can be used from SPL.
Update the 'mtrr' command to call it.
Use this in SPL just before adjusting the MTRRs, so we can see the state
set up by the board. Only show it when debug is enabled.
Signed-off-by: Simon Glass
---
arch/x86/cpu/mtrr.c
We don't actually set up all of these registers in SPL, so using
mtrr_commit() with erase some. Use mtrr_set_next_var() instead.
Signed-off-by: Simon Glass
---
arch/x86/lib/spl.c | 10 +-
configs/chromebook_link64_defconfig | 2 ++
2 files changed, 7 insertions(+), 5 d
The 'tiny' SPI nor functions have the same name as their big brothers,
which can be confusing. Use different names so it is clear which
version is in the image.
Signed-off-by: Simon Glass
---
drivers/mtd/spi/spi-nor-tiny.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
With tiny SPI flash the erasesize is 0 which can cause a divide-by-zero
error. Check for this and returns a proper error instead.
Signed-off-by: Simon Glass
---
drivers/mtd/spi/sf_probe.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/spi/sf_probe.c b/drivers/
The bd82x6x_get_gpio_base() does not work if the LPC is not set up.
Probe it early to avoid this problem.
In chromebook_link64 this propblem shows up as an inability to read
the GPIO straps for the memory type.
Signed-off-by: Simon Glass
---
arch/x86/cpu/ivybridge/bd82x6x.c | 17 +-
Show the area of memory cleared for BSS, when debugging is enabled.
Signed-off-by: Simon Glass
---
arch/x86/lib/spl.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/x86/lib/spl.c b/arch/x86/lib/spl.c
index bdf57ef7b5bd..eb0af219ae29 100644
--- a/arch/x86/lib/spl.c
+
SPL printf() does not normally support %#x so just use %x instead. Hex is
expected in U-Boot anyway.
Signed-off-by: Simon Glass
---
arch/x86/lib/mrccache.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/lib/mrccache.c b/arch/x86/lib/mrccache.c
index 38632e513fce..2
For now, just enable the fast-but-large string functions in 32-boot
U-Boot proper only. Avoid using them in SPL. We cannot use then in 64-bit
builds since we only have 32-bit assembly.
Signed-off-by: Simon Glass
---
arch/x86/include/asm/string.h | 6 +-
arch/x86/lib/Makefile | 4 +++
The debug UART is already set up in SPL, so there is no need to do
anything here. We must provide the (empty) function though.
Signed-off-by: Simon Glass
---
arch/x86/cpu/x86_64/cpu.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/x86/cpu/x86_64/cpu.c b/arch/x86/cpu/x86_64/cpu.
This adds a lot of code so that it cannot be build with the binary
blobs. It is not used on this board. Drop it.
Signed-off-by: Simon Glass
---
configs/chromebook_samus_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/chromebook_samus_defconfig
b/configs/chromebook_samus_d
The previous attempt at fixing this broke the normal usage of the -A
flag.
At present, 'buildman -A sandbox' adds the path containing the
toolchain. We can assume that this is in the path and we don't want to
set CROSS_COMPILE=/bin/
Change this to align with what MakeEnvironment() does, but only
This reverts commit bd0a548ad4a155fec29473d4cc8e135832926973.
Signed-off-by: Simon Glass
---
tools/buildman/toolchain.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/buildman/toolchain.py b/tools/buildman/toolchain.py
index 8f9130bdcdf6..688f2e268726 100644
--- a/
Hi Johan,
On Sun, 12 Mar 2023 at 06:21, Johan Jonker wrote:
>
>
>
> On 3/11/23 02:37, Simon Glass wrote:
> > Hi Johan,
> >
> > On Fri, 10 Mar 2023 at 08:42, Johan Jonker wrote:
> >>
> >> The fdt_addr_t and phys_addr_t size have been decoupled.
> >> A 32bit CPU can expect 64-bit data from the dev
On Sun, 12 Mar 2023 at 18:29, Johan Jonker wrote:
>
> The fdt_addr_t and phys_addr_t size have been decoupled.
> A 32bit CPU can expect 64-bit data from the device tree parser,
> so use a regs variable with uintptr_t size in the
> dw-apb-timer.c file.
>
> Signed-off-by: Johan Jonker
> ---
>
> Cha
On Sun, 12 Mar 2023 at 18:30, Johan Jonker wrote:
>
> The fdt_addr_t and phys_addr_t size have been decoupled.
> A 32bit CPU can expect 64-bit data from the device tree parser,
> so use a base variable with uintptr_t size in the
> rk_pwm.c file.
>
> Signed-off-by: Johan Jonker
> ---
>
> Changed V
On Sun, 12 Mar 2023 at 18:30, Johan Jonker wrote:
>
> The fdt_addr_t and phys_addr_t size have been decoupled.
> A 32bit CPU can expect 64-bit data from the device tree parser,
> so use a base variable with uintptr_t size in the
> rk_spi.c file.
>
> Signed-off-by: Johan Jonker
> ---
>
> Changed V
On Sun, 12 Mar 2023 at 18:30, Johan Jonker wrote:
>
> The fdt_addr_t and phys_addr_t size have been decoupled.
> A 32bit CPU can expect 64-bit data from the device tree parser,
> so convert regmap_init_mem_plat() input to handel both. The
> syscon class driver also makes use of the regmap_init_mem
On Sun, 12 Mar 2023 at 18:31, Johan Jonker wrote:
>
> The Rockchip SoC rk3288 has 2 types of device trees floating around.
> A 64bit reg size when synced from Linux and a 32bit for U-boot.
> A pre-probe function in the syscon class driver assumes only 32bit.
> For other odd reg structures the regm
On Sun, 12 Mar 2023 at 18:31, Johan Jonker wrote:
>
> The fdt_addr_t and phys_addr_t size have been decoupled. A 32bit CPU
> can expect 64-bit data from the device tree parser, so use
> dev_read_addr_index_ptr instead of the dev_read_addr_index function
> in the various files in the drivers direct
Hi Tom,
This is for the -next branch
https://source.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/15568
The following changes since commit bcf343146ff365a88481b9a80920ed146c6dee5b:
Merge tag 'dm-next-9mar23' of
https://source.denx.de/u-boot/custodians/u-boot-dm into next
(2023-03-09 11:22:
> -Original Message-
> From: Bough Chen
> Sent: 2023年2月10日 17:27
> To: h...@denx.de; al.koc...@gmail.com; ma...@denx.de
> Cc: u-boot@lists.denx.de; dl-uboot-imx ;
> xypron.g...@gmx.de; Bough Chen
> Subject: [PATCH] i2c: correct I2C deblock logic
>
> From: Haibo Chen
>
> Current code us
The DT specification supports CPUs with both 32-bit and 64-bit addressing
capabilities. In U-boot the fdt_addr_t and phys_addr_t size are coupled
by a typedef. The MTD NAND drivers for 32-bit CPU's can describe partitions
with a 64-bit reg property. These partitions synced from Linux end up with
th
The fdt_addr_t and phys_addr_t size have been decoupled.
A 32bit CPU can expect 64-bit data from the device tree parser,
so fix ofnode_get_addr_size function with fdt_addr_t input to
be able to handle both sizes for stm32mp SoC in spl.c file.
Signed-off-by: Johan Jonker
Reviewed-by: Simon Glass
The fdt_addr_t and phys_addr_t size have been decoupled. A 32bit CPU
can expect 64-bit data from the device tree parser, so fix some
debug strings with fdt_addr_t to be able to handle both sizes.
Signed-off-by: Johan Jonker
Reviewed-by: Simon Glass
---
Changed V5:
new patch
---
arch/arm/mach
The fdt_addr_t and phys_addr_t size have been decoupled. A 32bit CPU
can expect 64-bit data from the device tree parser, so use
devfdt_get_addr_ptr instead of the devfdt_get_addr function in
the various files in the drivers directory that cast to a pointer.
Signed-off-by: Johan Jonker
Reviewed-by
The fdt_addr_t and phys_addr_t size have been decoupled. A 32bit CPU
can expect 64-bit data from the device tree parser, so use
devfdt_get_addr_index_ptr instead of the devfdt_get_addr_index function
in the various files in the drivers directory that cast to a pointer.
As we are there also streamli
The fdt_addr_t and phys_addr_t size have been decoupled. A 32bit CPU
can expect 64-bit data from the device tree parser, so use
devfdt_get_addr_size_index_ptr instead of the devfdt_get_addr_size_index
function in the various files in the drivers directory that cast to
a pointer.
Signed-off-by: Joh
The fdt_addr_t and phys_addr_t size have been decoupled. A 32bit CPU
can expect 64-bit data from the device tree parser, so use
dev_read_addr_ptr instead of the dev_read_addr function in the
various files in the drivers directory that cast to a pointer.
As we are there also streamline the error res
The fdt_addr_t and phys_addr_t size have been decoupled. A 32bit CPU
can expect 64-bit data from the device tree parser, so use
dev_read_addr_index_ptr instead of the dev_read_addr_index function
in the various files in the drivers directory that cast to a pointer.
As we are there also streamline t
The fdt_addr_t and phys_addr_t size have been decoupled.
A 32bit CPU can expect 64-bit data from the device tree parser,
so use devfdt_get_addr_index_ptr and devfdt_get_addr_size_index_ptr
function in the spi-aspeed-smc.c file. Also fix dev_dbg to be able
to handle both sizes. As we are there also
Add dev_read_addr_index_ptr function with the
same functionality as dev_read_addr_index,
but instead a return pointer is given.
Use map_sysmem() function as cast for the return.
Make same fix for dev_read_addr_ptr() function.
Signed-off-by: Johan Jonker
Reviewed-by: Simon Glass
---
Changed V6:
Add devfdt_get_addr_size_index_ptr function with the same
functionality as devfdt_get_addr_size_index, but instead
a return pointer is given.
Use map_sysmem() function as cast for the return.
Make same fix for devfdt_get_addr_index_ptr() function.
Suggested-by: Michael Nazzareno Trimarchi
Signed-
The Rockchip SoC rk3288 has 2 types of device trees floating around.
A 64bit reg size when synced from Linux and a 32bit for U-boot.
A pre-probe function in the syscon class driver assumes only 32bit.
For other odd reg structures the regmap must be defined in the individual
syscon driver. Store rk3
The fdt_addr_t and phys_addr_t size have been decoupled.
A 32bit CPU can expect 64-bit data from the device tree parser,
so convert regmap_init_mem_plat() input to handel both. The
syscon class driver also makes use of the regmap_init_mem_plat()
function, but has no way of knowing the format of the
When fdt_addr_t and phys_addr_t are split it turns out that
the header don't match the functions, so fix the headers.
Signed-off-by: Johan Jonker
Reviewed-by: Simon Glass
Reviewed-by: Kever Yang
---
include/dm/ofnode.h | 16
1 file changed, 8 insertions(+), 8 deletions(-)
dif
The fdt_addr_t and phys_addr_t size have been decoupled.
A 32bit CPU can expect 64-bit data from the device tree parser,
so use a base variable with uintptr_t size in the
rk_spi.c file.
Signed-off-by: Johan Jonker
---
Changed V8:
new patch
---
drivers/spi/rk_spi.c | 2 +-
1 file changed, 1 in
The fdt_addr_t and phys_addr_t size have been decoupled.
A 32bit CPU can expect 64-bit data from the device tree parser,
so use a base variable with uintptr_t size in the
rk_pwm.c file.
Signed-off-by: Johan Jonker
---
Changed V8:
use uintptr_t instead of phys_addr_t
Changed V6:
new patch
--
The fdt_addr_t and phys_addr_t size have been decoupled.
A 32bit CPU can expect 64-bit data from the device tree parser,
so use a regs variable with uintptr_t size in the
dw-apb-timer.c file.
Signed-off-by: Johan Jonker
---
Changed V8:
use uintptr_t instead of phys_addr_t
Changed V6:
remove
The fdt_addr_t and phys_addr_t size have been decoupled.
A 32bit CPU can expext 64-bit data from the device tree parser,
so use dev_read_addr_ptr in the rockchip-saradc.c file.
As we are there also streamline the error response to -EINVAL on return.
Signed-off-by: Johan Jonker
Reviewed-by: Kever
Sandisk SDTNQGAMA is a 8GB size, 3.3V 8 bit chip with 16KB page size,
1KB write size and 40 bit ecc support
Signed-off-by: Paweł Jarosz
Signed-off-by: Johan Jonker
Reviewed-by: Kever Yang
Acked-by: Michael Trimarchi
---
drivers/mtd/nand/raw/nand_ids.c | 3 +++
1 file changed, 3 insertions(+)
The MTD framework reserves 1 or 2 bytes for the bad block marker
depending on the bus size. The rockchip_nfc driver currently only
supports a 8 bit bus, but reserves standard 2 bytes for the BBM.
The first free OOB byte is therefore OOB2 at offset 2.
Page address(PA) bytes are moved to the last 4 p
Add flash_node to the rockchip_nfc driver chip structure in order
to find the partitions in the add_mtd_partitions_of() function.
Signed-off-by: Johan Jonker
Reviewed-by: Kever Yang
Reviewed-by: Michael Trimarchi
---
drivers/mtd/nand/raw/rockchip_nfc.c | 1 +
1 file changed, 1 insertion(+)
di
The MTD framework in U-boot is not identical for drivers ported
from Linux. The rockchip_nfc driver was ported with OOB ops functions
while the framework expects a layout structure per chip.
Fix by adding a structure with OOB data and remove unused functions.
Signed-off-by: Johan Jonker
Reviewed-
The compatible string for rk3308 has as fallback string
"rockchip,rv1108-nfc". As there is no logic in probe priority between
the SoC orientated string and the fall back, so remove the compatible
string "rockchip,rk3308-nfc" from the driver.
Signed-off-by: Johan Jonker
Reviewed-by: Kever Yang
Re
The fdt_addr_t and phys_addr_t size have been decoupled.
A 32bit CPU can expext 64-bit data from the device tree parser,
so use dev_read_addr_ptr in the rockchip_nfc.c file.
Signed-off-by: Johan Jonker
Reviewed-by: Michael Trimarchi
---
Changed V6:
use -EINVAL on return
---
drivers/mtd/nand/
The previous attempt at fixing this broke the normal usage of the -A
flag.
At present, 'buildman -A sandbox' adds the path containing the
toolchain. We can assume that this is in the path and we don't want to
set CROSS_COMPILE=/bin/
Change this to align with what MakeEnvironment() does, but only
This reverts commit bd0a548ad4a155fec29473d4cc8e135832926973.
Signed-off-by: Simon Glass
---
tools/buildman/toolchain.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Applied to u-boot-dm/next, thanks!
This serie contains fixes for the Rockchip NFC driver,
which was ported to U-boot and merged with little review
and testing it seems.
Part 1 aims at passing the probe function without errors.
Extended with tree wide function cleanup needed for 64bit DT parsing.
Fixed are:
64bit FDT parsing
com
Hi Pali,
On Sun, Mar 12, 2023 at 2:38 PM Pali Rohár wrote:
>
> On Sunday 12 March 2023 14:30:29 Tony Dinh wrote:
> > Hi Pali,
> >
> > On Sat, Mar 11, 2023 at 4:29 PM Pali Rohár wrote:
> > >
> > > On Saturday 11 March 2023 15:47:29 Tony Dinh wrote:
> > > > Hi Pali,
> > > >
> > > > On Sat, Mar 11,
Dear Tom,
> -Original Message-
> From: Tom Rini
> Sent: Saturday, March 11, 2023 12:44 AM
> To: Jaehoon Chung
> Cc: U-Boot Mailing List ; Loic Poulain
> ; Marek Vasut
> ; Stefan Roese ; Jae hoon Chung
>
> Subject: Re: [GIT PULL] Please pull u-boot-mmc master
>
> On Fri, Mar 10, 2023
Hi Eugen,
On 2023-03-08 09:57, Eugen Hristev wrote:
> On 1/29/23 11:04, Jonas Karlman wrote:
>> On 2023-01-27 14:21, Jagan Teki wrote:
>>> On Fri, 27 Jan 2023 at 05:13, Jonas Karlman wrote:
On 2023-01-26 23:16, Jonas Karlman wrote:
> Hi Jagan,
> On 2023-01-26 20:17, Jagan Teki w
On Sunday 12 March 2023 14:30:29 Tony Dinh wrote:
> Hi Pali,
>
> On Sat, Mar 11, 2023 at 4:29 PM Pali Rohár wrote:
> >
> > On Saturday 11 March 2023 15:47:29 Tony Dinh wrote:
> > > Hi Pali,
> > >
> > > On Sat, Mar 11, 2023 at 2:57 AM Pali Rohár wrote:
> > > >
> > > > Same change as was done for
Hi Pali,
On Sat, Mar 11, 2023 at 4:29 PM Pali Rohár wrote:
>
> On Saturday 11 March 2023 15:47:29 Tony Dinh wrote:
> > Hi Pali,
> >
> > On Sat, Mar 11, 2023 at 2:57 AM Pali Rohár wrote:
> > >
> > > Same change as was done for mvebu in commit 5bb2c550b11e ("arm: mvebu:
> > > Move
> > > internal
Add the documentation about binman sign option and providing an
example.
Signed-off-by: Ivan Mikhaylov
---
tools/binman/binman.rst | 18 ++
1 file changed, 18 insertions(+)
Applied to u-boot-dm/next, thanks!
Applied to u-boot-dm/next, thanks!
Hi Ivan,
On Tue, 7 Mar 2023 at 14:13, Ivan Mikhaylov wrote:
>
> Introduce proof of concept for binman's new option which provides sign
> and replace FIT containers in binary images.
>
> Usage as example:
>
> from:
> mkimage -G privateky -r -o sha256,rsa4096 -F fit
> binman replace -i flash.bin -f
Hi Ivan,
On Fri, 10 Mar 2023 at 17:47, Simon Glass wrote:
>
> Add the test which provides sequence of actions:
> 1. create the image from binman dts
> 2. create public and private keys
> 3. add public key into dtb with fdt_add_pubkey
> 4. 1. sign FIT container with new sign option with ex
On 3/11/23 02:37, Simon Glass wrote:
> Hi Johan,
>
> On Fri, 10 Mar 2023 at 08:42, Johan Jonker wrote:
>>
>> The fdt_addr_t and phys_addr_t size have been decoupled.
>> A 32bit CPU can expect 64-bit data from the device tree parser,
>
> Sorry if you already responded and I missed it.
>
> I
On Sun, Mar 12, 2023 at 1:55 AM Tom Rini wrote:
>
> On Fri, Mar 10, 2023 at 09:39:15PM -0800, Randy Dunlap wrote:
> > Hi--
> >
> > On 3/10/23 18:37, Simon Glass wrote:
> > > (I am sending this again to get more feedback)
> > >
> > > In the case of Linux, only one build is produced so there is only
Hi Tom,
On Fri, Mar 10, 2023 at 01:12:24PM -0500, Tom Rini wrote:
> On Sun, Jan 29, 2023 at 06:30:22PM +0200, Laurent Pinchart wrote:
>
> > FIT image support is commonly used to bundle a kernel image, a device
> > tree, and device tree overlays. Applying overlays requires the
> > OF_LIBFDT_OVERLA
65 matches
Mail list logo
