Implement reset use to discard any changes which could have been
applied to DSI before and can interfere with current configuration.
Tested-by: Ion Agorria # HTC One X
Tested-by: Svyatoslav Ryhel # Nvidia Tegratab T114
Signed-off-by: Svyatoslav Ryhel
---
drivers/video/tegra20/tegra-dsi.c | 14
Existing Tegra DSI driver mostly fits T114 apart MIPI calibration
which on T114 has dedicated driver. To resolve this MIPI calibration
logic was split for pre-T114 and T114+ devices.
Tested-by: Ion Agorria # HTC One X
Tested-by: Svyatoslav Ryhel # Nvidia Tegratab T114
Signed-off-by: Svyatoslav
Dedicated MIPI calibration driver is used on T114 and newer. Before
T114 MIPI calibration registers were part of VI and CSI.
Tested-by: Svyatoslav Ryhel # Nvidia Tegratab T114
Signed-off-by: Svyatoslav Ryhel
---
drivers/video/tegra20/Makefile | 2 +-
drivers/video/tegra20/tegra-mipi.c |
Add powergate use on T114 to complete resetting of DC.
Signed-off-by: Svyatoslav Ryhel
---
drivers/video/tegra20/tegra-dc.c | 27 +++
1 file changed, 27 insertions(+)
diff --git a/drivers/video/tegra20/tegra-dc.c b/drivers/video/tegra20/tegra-dc.c
index
Implement reset use to discard any changes which could have been
applied to DC before and can interfere with current configuration.
Tested-by: Agneli # Toshiba AC100 T20
Tested-by: Robert Eckelmann # ASUS TF101
Tested-by: Andreas Westman Dorcsak # ASUS Grouper E1565
Tested-by: Ion Agorria #
Tegra SoC has 2 independent display controllers called DC_A and
DC_B, they are handled differently by internal video devices like
DSI and HDMI controllers so it is important for last to know
which display controller is used to properly set up registers.
To achieve this, a pipe field was added to
T30+ SOC have second PLLD - PLLD2 which can be actively used by
DC and act as main DISP1/2 clock parent.
Tested-by: Agneli # Toshiba AC100 T20
Tested-by: Robert Eckelmann # ASUS TF101
Tested-by: Andreas Westman Dorcsak # ASUS Grouper E1565
Tested-by: Ion Agorria # HTC One X
Tested-by:
Consolidate HD headers and place the result into video/tegra20
since it is used only by devices from this directory.
Tested-by: Agneli # Toshiba AC100 T20
Tested-by: Robert Eckelmann # ASUS TF101
Tested-by: Andreas Westman Dorcsak # ASUS Grouper E1565
Tested-by: Ion Agorria # HTC One X
Diverge DC driver setup to better fit each of supported generations
of Tegra SOC.
Tested-by: Agneli # Toshiba AC100 T20
Tested-by: Robert Eckelmann # ASUS TF101
Tested-by: Andreas Westman Dorcsak # ASUS Grouper E1565
Tested-by: Ion Agorria # HTC One X
Tested-by: Svyatoslav Ryhel # Nvidia
Subtracting 1 from x and y fixes image shifting on rotated
panels.
Tested-by: Robert Eckelmann # ASUS Grouper E1565
Signed-off-by: Svyatoslav Ryhel
---
drivers/video/tegra20/tegra-dc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/tegra20/tegra-dc.c
T114 is not that different from T30 and all T30 drivers will work
on T114 as well with some adjustments.
Patches propose general improvements for existing Tegra DC and DSI
drivers as well Tegra 114 video support (experimentl).
Commits pass buildman for tegra.
---
Changes from v2:
- fixed image
Hi,
> -Original Message-
> From: Maniyam, Dinesh
> Sent: Thursday, December 7, 2023 3:46 PM
> To: u-boot@lists.denx.de
> Cc: Marek ; Simon ;
> Chee, Tien Fong ; Hea, Kok Kiang
> ; Maniyam, Dinesh ;
> Ng, Boon Khai ; Yuslaimi, Alif Zakuan
> ; Chong, Teik Heng
> ; Zamri, Muhammad Hazim
Hi Roger,
On 27/12/23 3:49 pm, MD Danish Anwar wrote:
> On 20/12/23 4:10 pm, Roger Quadros wrote:
>>
>>
>> On 19/12/2023 12:34, MD Danish Anwar wrote:
>>> Add ICSSG2 overlay and configuration to tispl and u-boot images.
>>>
>>> Signed-off-by: MD Danish Anwar
>>> ---
>>>
A busy controller shouldn't be game-over for all controllers,
so keep trying on hitting -EBUSY.
This change brings the actual behavior of the routine in line
with what the descriptions says.
Fixes: 982388eaa991 ("nvme: Add NVM Express driver support")
Reviewed-by: Simon Glass
Signed-off-by:
Return -EBUSY if controller is found busy rather than -ENOMEM
and update the error message accordingly.
Fixes: 982388eaa991 ("nvme: Add NVM Express driver support")
Reviewed-by: Simon Glass
Signed-off-by: Moritz Fischer
---
drivers/nvme/nvme.c | 4 ++--
1 file changed, 2 insertions(+), 2
This enables 64b BARs if CONFIG_SYS_PCI_64BIT is enabled.
Reviewed-by: Philip Oberfichtner
Reviewed-by: Simon Glass
Signed-off-by: Moritz Fischer
---
Changes from V3:
- Rebased onto v2024.01
Changes from V2:
- Turned IS_ENABLED() into #if defined to allow
building on platforms that don't
On Tue, Jan 9, 2024 at 9:47 PM Masahiro Yamada wrote:
>
> On Fri, Dec 29, 2023 at 3:39 PM Simon Glass wrote:
> >
> > Hi Masahiro,
> >
> > On Thu, Dec 14, 2023 at 7:34 AM Masahiro Yamada
> > wrote:
> > >
> > > On Thu, Dec 14, 2023 at 3:12 PM Masahiro Yamada
> > > wrote:
> > > >
> > > > On
The Turing RK1 is a Rockchip RK3588 based SoM from Turing Machines.
Specifications:
Rockchip RK3588 SoC
4x ARM Cortex-A76, 4x ARM Cortex-A55
8/16/32GB memory LPDDR4x
Mali G610MC4 GPU
32GB eMMC HS400
2x USB 2.0, 2x USB 3.0
2x MIPI CSI 4x lanes
1x MIPI-DSI DPHY 2x
Now it is clear that the feature actually depends on efi interfaces,
not "bootefi" command. efi_set_bootdev() will automatically be nullified
if necessary efi component is disabled.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
---
fs/fs.c | 7 +++
1 file changed, 3
Now it is clear that the feature actually depends on efi interfaces,
not "bootefi" command. efi_set_bootdev() will automatically be nullified
if necessary efi component is disabled.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Ramon Fried
Reviewed-by: Tom Rini
---
net/tftp.c | 10 --
1
At this point, EFI boot manager interfaces is fully independent from
bootefi command. So just rename the configuration parameter.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
---
boot/Makefile | 2 +-
cmd/Kconfig | 4 ++--
cmd/efidebug.c | 4 ++--
Some code moved from cmd/bootefi.c is actually necessary only for "bootefi
" command (starting an image manually loaded by a user using U-Boot
load commands or other methods (like JTAG debugger).
The code will never been opted out as unused code by a compiler which
doesn't know how EFI boot
This patch set is motivated by the discussion[1] regarding
CONFIG_BOOTEFI_BOOTMGR option.
# This version (v4) contains only the remaining commits.
At the end, bootefi.c will be decomposed into two parts, one for
providing the command itself and one for implementing helper functions.
EFI_LOADER
On Tue, 9 Jan 2024 at 22:02, Ilias Apalodimas
wrote:
>
> On Tue, 9 Jan 2024 at 03:00, Masahisa Kojima
> wrote:
> >
> > Hi Ilias,
> >
> > On Thu, 28 Dec 2023 at 00:14, Ilias Apalodimas
> > wrote:
> > >
> > > Kojima-san
> > >
> > > On Thu, Dec 21, 2023 at 06:52:58PM +0900, Masahisa Kojima wrote:
The function getchar() returns an 'int' and not a 'char'. Coverity notes
that "Assigning the return value of getchar to char ... truncates its value."
and so for the most part we can resolve this easily by using 'int' as
intended, and often used throughout the codebase. A few places are not
so
On Tue, Jan 09, 2024 at 12:26:13AM -0500, Sean Anderson wrote:
> Comments on NAND stuff only.
>
> On 1/8/24 12:45, Tom Rini wrote:
> >
> > *** CID 477216:(BAD_SHIFT)
> >
On Tue, Jan 09, 2024 at 06:09:12PM +0100, Heinrich Schuchardt wrote:
> The following changes since commit c5e461fbf7cc72f0c1c8a79226b6a5170e56cb4d:
>
> Merge tag 'u-boot-imx-master-20240108' of
> https://gitlab.denx.de/u-boot/custodians/u-boot-imx (2024-01-08 13:39:43
> -0500)
>
> are
On 12/26/23 10:47, Simon Glass wrote:
Hi Heinrich,
On Sat, Dec 23, 2023 at 1:03 AM Heinrich Schuchardt wrote:
From: Heinrich Schuchardt
QEMU provides SMBIOS tables with detailed information. We should not try to
replicate them in U-Boot.
If we want to inform about U-Boot, we can add a
On Tue, Jan 09, 2024 at 02:00:14PM -0600, Nishanth Menon wrote:
> On 14:48-20240109, Tom Rini wrote:
> [...]
> > > > --
> > > > 2.34.1
> > > >
> > >
> > > Why not a config fragment?
> >
> > To me, this makes sense to keep
On 21:00-20240109, Francesco Dolcini wrote:
> On Tue, Jan 09, 2024 at 02:54:00PM -0500, Tom Rini wrote:
> > On Tue, Jan 09, 2024 at 01:18:59PM -0600, Nishanth Menon wrote:
> > > On 14:26-20240109, Roger Quadros wrote:
> > > > CONFIG_CMD_PMIC=y
&
Hi Neil,
On Tue, Dec 19, 2023 at 5:21 PM Jagan Teki wrote:
>
> On Tue, Dec 19, 2023 at 2:34 PM Neil Armstrong
> wrote:
> >
> > On 18/12/2023 20:10, Jagan Teki wrote:
> > > From: Jagan Teki
> > >
> > > DW HDMI support Vendor PHY like Rockchip RK3328 Inno HDMI PHY.
> > >
> > > Extend the vendor
On Tue, Jan 09, 2024 at 02:54:00PM -0500, Tom Rini wrote:
> On Tue, Jan 09, 2024 at 01:18:59PM -0600, Nishanth Menon wrote:
> > On 14:26-20240109, Roger Quadros wrote:
> > > CONFIG_CMD_PMIC=y
> > > CONFIG_CMD_REGULATOR=y
> > > +CONFIG_CMD_MTDPARTS=y
> >
On 14:48-20240109, Tom Rini wrote:
[...]
> > > --
> > > 2.34.1
> > >
> >
> > Why not a config fragment?
>
> To me, this makes sense to keep in the main config. It can be turned off
> as needed, and at run time if it's not present, it's safe.
T
On Tue, Jan 09, 2024 at 01:18:59PM -0600, Nishanth Menon wrote:
> On 14:26-20240109, Roger Quadros wrote:
> > Enables configuration required for NAND in SPL and u-boot.
> >
> > Enable MTD Driver model and MTD + UBI command line utilities.
> >
> > Add mtdids/mt
On Tue, Jan 09, 2024 at 01:16:27PM -0600, Nishanth Menon wrote:
> On 14:26-20240109, Roger Quadros wrote:
> > Enables configuration required for NAND in SPL and u-boot.
> >
> > Enable MTD Driver model and MTD + UBI command line utilities.
> >
> > Add mtdids/mt
On 15:16-20240108, Roger Quadros wrote:
> The TMDS64EVM [1] ships with AM64X SR2.0 HS-FS chip
> and a slightly different board name in the board information
> EEPROM header. Support this board.
>
> [1] https://www.ti.com/tool/TMDS64EVM
>
> Gets rid of below message at boot
> "Unidentified board
On 14:26-20240109, Roger Quadros wrote:
> Enables configuration required for NAND in SPL and u-boot.
>
> Enable MTD Driver model and MTD + UBI command line utilities.
>
> Add mtdids/mtdparts for NAND as it is required for u-boot's
> MTD subsystem commands to recognize NAND part
We now can provide a map and have the standard fdtfile variable set from
code itself. This allows for bootstd to "just work".
While at this, replace findfdt in environment with a warning as it is no
longer needed.
Signed-off-by: Nishanth Menon
---
Changes from V1: None.
I have retained the the
We shouldn't need finfdt anymore. Drop the env script.
Signed-off-by: Nishanth Menon
---
Changes from V1: None.
V1: https://lore.kernel.org/r/20240108173301.2692332-11...@ti.com
include/env/ti/default_findfdt.env | 12
1 file changed, 12 deletions(-)
delete mode 100644
Stop using the findfdt script and switch to setting the fdtfile from C
code.
Signed-off-by: Nishanth Menon
---
Changes from V1:
* Just macro name change s/TI_EVM_FDT_FOLDER_PATH/TI_FDT_FOLDER_PATH
* Commit message update to drop the "warning added to findfdt" since
that is not done.
I have
This is a wide cleanup to switch to setting fdtfile using env_set
instead of scripted magic. 'fdtfile' is expected to be set by default.
This allows the stdboot triggered efi loaders to find the correct OS
device tree file even if regular boot process is interrupted by user
intervention.
This is
Stop using the findfdt script and switch to setting the fdtfile from C
code.
Signed-off-by: Nishanth Menon
---
Changes from V1:
* Just macro name change s/TI_EVM_FDT_FOLDER_PATH/TI_FDT_FOLDER_PATH
* Commit message update to drop the "warning added to findfdt" since
that is not done.
I have
We now can provide a map and have the standard fdtfile variable set from
code itself. This allows for bootstd to "just work".
While at this, replace findfdt in environment with a warning as it is no
longer needed.
Signed-off-by: Nishanth Menon
---
Changes from V1: None.
v1:
We now can provide a map and have the standard fdtfile variable set from
code itself. This allows for bootstd to "just work".
While at this, replace findfdt in environment with a warning as it is no
longer needed.
Signed-off-by: Nishanth Menon
---
Changes from V1: None.
V1:
Stop using the findfdt script and switch to setting the fdtfile from
C code.
While at this, replace findfdt in environment with a warning as it is
no longer needed
Signed-off-by: Nishanth Menon
---
Changes from V1: None.
I have retained the central call ti_set_fdt_env() to retain the
population
Introduce a common fdt operations library for basic device tree
operations that are common between various boards.
The first library to introduce here is the capability to set up
fdtfile as a standard variable as part of board identification rather
than depend on scripted ifdeffery.
Stop using the findfdt script and switch to setting the fdtfile from
C code.
While at this, replace findfdt in environment with a warning as it is
no longer needed
Signed-off-by: Nishanth Menon
---
Changes from V1: None.
I have retained the central call ti_set_fdt_env() to retain the
population
We now can provide a map and have the standard fdtfile variable set from
code itself. This allows for bootstd to "just work".
While at this, replace findfdt in environment with a warning as it is no
longer needed.
Signed-off-by: Nishanth Menon
---
Changes from V1: None.
I have retained the
On 14:26-20240109, Roger Quadros wrote:
> Hi,
>
> AM64-EVM [1] supports NAND via expansion card.
>
> This series fixes the GPMC memory and NAND drivers
> and provides NAND configuration for AM642 platform.
>
> The extension card support and NAND DT overlay is
> still
On 14:26-20240109, Roger Quadros wrote:
> Enables configuration required for NAND in SPL and u-boot.
>
> Enable MTD Driver model and MTD + UBI command line utilities.
>
> Add mtdids/mtdparts for NAND as it is required for u-boot's
> MTD subsystem commands to recognize NAND part
On Tue, Jan 09, 2024 at 10:55:16AM +0900, Minkyu Kang wrote:
> Dear Tom,
>
> The following changes since commit 2f0282922b2c458eea7f85c500a948a587437b63:
>
> Prepare v2024.01-rc4 (2023-12-04 13:46:56 -0500)
>
> are available in the git repository at:
>
>
On Tue, Jan 09, 2024 at 10:07:37AM +0100, Heinrich Schuchardt wrote:
> Dear Tom,
>
> The following changes since commit c5e461fbf7cc72f0c1c8a79226b6a5170e56cb4d:
>
> Merge tag 'u-boot-imx-master-20240108' of
> https://gitlab.denx.de/u-boot/custodians/u-boot-imx (2024-01-08 13:39:43
> -0500)
>
pr_err() doesn't add an newline symbol when printing.
Signed-off-by: Alexey Romanov
Reviewed-by: Sean Anderson
Reviewed-by: Mattijs Korpershoek
---
drivers/fastboot/fb_nand.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/fastboot/fb_nand.c
>From now we can use FASTBOOT_FLASH_NAND option for SPI NAND.
Signed-off-by: Alexey Romanov
Reviewed-by: Mattijs Korpershoek
---
drivers/fastboot/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/fastboot/Kconfig b/drivers/fastboot/Kconfig
index
SPI NAND devices also supports 'fastboot erase / flash' commands.
Signed-off-by: Alexey Romanov
Reviewed-by: Sean Anderson
Reviewed-by: Mattijs Korpershoek
---
drivers/fastboot/fb_nand.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/fastboot/fb_nand.c
Boards with SPI NAND also can use this command.
Signed-off-by: Alexey Romanov
Reviewed-by: Sean Anderson
---
cmd/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmd/Kconfig b/cmd/Kconfig
index 26ad03..4332894184 100644
--- a/cmd/Kconfig
+++ b/cmd/Kconfig
@@
Use CMD_RET_FAILURE and CMD_RET_SUCCESS defines instead
of 1 and 0.
Signed-off-by: Alexey Romanov
---
cmd/jffs2.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/cmd/jffs2.c b/cmd/jffs2.c
index 15bf8c0edf..d5aa9bcc7e 100644
--- a/cmd/jffs2.c
+++
It is bad practice to use such error codes. Error codes
must be negative.
Signed-off-by: Alexey Romanov
---
cmd/jffs2.c | 29 +++--
1 file changed, 15 insertions(+), 14 deletions(-)
diff --git a/cmd/jffs2.c b/cmd/jffs2.c
index e00fcc2022..15bf8c0edf 100644
---
It is bad practice to use such error codes. Error codes
must be negative.
Also, fastboot code expects that if successful, mtdparts
functions will return a value greater than 0. You can see
fastboot_nand_get_part_info() functions calls inside
getvar_get_part_info().
Signed-off-by: Alexey Romanov
Use 'return CMD_RET_FAILURE' define instead of 'return 1'.
Signed-off-by: Alexey Romanov
---
cmd/mtdparts.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/cmd/mtdparts.c b/cmd/mtdparts.c
index 00c07014b2..392ee511c9 100644
--- a/cmd/mtdparts.c
+++
Most functions that work with NAND device (for example fastboot),
use the get_nand_dev_by_index() function to work with NAND MTD.
In order to use this feature, SPI NAND must be registered via
nand_register().
Signed-off-by: Alexey Romanov
---
drivers/mtd/nand/spi/core.c | 3 ++-
1 file changed,
By analogy with RAW NAND drivers, select SYS_NAND_SELF_INIT
option and implement board_nand_init() function. It will be
called from nand_init().
Signed-off-by: Alexey Romanov
---
drivers/mtd/nand/spi/Kconfig | 1 +
drivers/mtd/nand/spi/core.c | 14 ++
2 files changed, 15
Currently nand_erase_opts() placed in the nand/raw/ folder,
because it uses the RAW NAND specific API (struct nand_chip).
This patch move it to core NAND folder and make function generic,
for both RAW/SPI NAND's usage.
Also, nand_erase_opts() used in fastboot/fb_nand.c, cmd/nand.c
and env/nand.c
This is right place for this API. Now, fastboot code uses this
API: these functions should be available regardless of the
selected NAND type (RAW / SPI).
Signed-off-by: Alexey Romanov
---
drivers/mtd/nand/Makefile| 2 +-
drivers/mtd/nand/raw/nand_util.c | 511
We use this function in SPI NAND subsystem, which already
filled mtd->name field with "spi-nand0" string.
Signed-off-by: Alexey Romanov
---
drivers/mtd/nand/core.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/mtd/nand/core.c b/drivers/mtd/nand/core.c
nand_register() and nand_init() is generic API for both
RAW and SPI NAND's. We have to move this functions
from drivers/mtd/nand/raw/nand.c to drivers/mtd/nand/core.c.
Functions designed to work with RAW NAND should remain
in drivers/mtd/nand/raw/nand.c.
Signed-off-by: Alexey Romanov
---
Currently, fastboot in U-Boot doens't support SPI NAND
devices. This patchset adds support for SPI NAND in fastboot
nand subsystem.
Changes V1 -> V2:
- Rebase patchset over u-boot/next.
- Move nand_unregister(), nand_reinit() and nang_page_size() functions
to NAND core folder too.
- Move
On 1/8/24 10:56 AM, Thomas Richard wrote:
This series is the U-Boot part of the work to add the suspend to RAM
support for the K3 J7200 EVM board.
During the boot R5 SPL makes a copy of DM-Firmware and TF-A in memory.
Resume detection is done by reading a magic value in a pmic register
(set by
The following changes since commit c5e461fbf7cc72f0c1c8a79226b6a5170e56cb4d:
Merge tag 'u-boot-imx-master-20240108' of
https://gitlab.denx.de/u-boot/custodians/u-boot-imx (2024-01-08 13:39:43
-0500)
are available in the Git repository at:
On 18:20-20240109, Roger Quadros wrote:
>
>
> On 08/01/2024 19:32, Nishanth Menon wrote:
> > We now can provide a map and have the standard fdtfile variable set from
> > code itself. This allows for bootstd to "just work".
> >
> > While at this, re
On 08/01/2024 19:32, Nishanth Menon wrote:
> We now can provide a map and have the standard fdtfile variable set from
> code itself. This allows for bootstd to "just work".
>
> While at this, replace findfdt in environment with a warning as it is no
> longer needed.
>
> Signed-off-by:
On 17:56-20240108, Thomas Richard wrote:
> This series is the U-Boot part of the work to add the suspend to RAM
> support for the K3 J7200 EVM board.
>
> During the boot R5 SPL makes a copy of DM-Firmware and TF-A in memory.
> Resume detection is done by reading a magic value in a pmic register
>
On Tue, Jan 09, 2024 at 10:55:16AM +0900, Minkyu Kang wrote:
> Dear Tom,
>
> The following changes since commit 2f0282922b2c458eea7f85c500a948a587437b63:
>
> Prepare v2024.01-rc4 (2023-12-04 13:46:56 -0500)
>
> are available in the git repository at:
>
>
On 1/9/24 05:27, Alexey Romanov wrote:
> Hello Sean!
>
> Thanks for you reply.
>
> On Thu, Dec 28, 2023 at 11:45:04AM -0500, Sean Anderson wrote:
>> On 12/28/23 10:25, Alexey Romanov wrote:
>> > Currently, fastboot protocol in U-Boot has no opportunity
>> > to execute vendor custom code with
Hi,
On Fri, 05 Jan 2024 09:22:05 +0200, Svyatoslav Ryhel wrote:
> Currently u-boot fastboot can only send one message back to host,
> so if there is a need to print more than one line messages must be
> kept sending until all the required data is obtained. This behavior
> can be adjusted using
Hi Robert,
On 1/9/24 14:16, Robert Marko wrote:
On Wed, Nov 29, 2023 at 11:11 AM Robert Marko wrote:
Currently, Esspresobin FDT is being fixed up directly in ft_board_setup()
which makes it hard to add support for any other board to be fixed up.
So, lets just move the FDT fixup code to a
Hi Grzegorz,
Thank you for the patch.
On sam., janv. 06, 2024 at 11:36, Grzegorz Szymaszek
wrote:
> The "Sending patches" and "Patman patch manager" documents refer to the
> three-dash, "---", that separates patch parts. The symbol is written in
> the documentation in the same form as it is
On 15:08-20240109, Roger Quadros wrote:
[..]
> > +/**
> > + * struct ti_fdt_map - mapping of device tree blob name to board name
> > + * @name_fdt: board_name up to TI_NAME_FDT_MAX long
> > + * @fdt_file_name: device tree blob name as described by kernel
> &g
On 14/12/2023 08.33, Masahiro Yamada wrote:
> On Thu, Dec 14, 2023 at 3:12 PM Masahiro Yamada wrote:
>>
> One more question to confirm if I can use this
> for my practical use-cases.
>
> Is U-Boot able to handle FIT (includes kernel + DTs)
> and a separate initrd?
>
> # bootm :
>
>
>
On Tue, Jan 09, 2024 at 11:01:42PM +0900, Masahiro Yamada wrote:
> Hi Simon,
>
>
> On Wed, Jan 3, 2024 at 8:47 AM Simon Glass wrote:
> >
> > Hi Masahiro,
> >
> > On Wed, Dec 13, 2023 at 5:14 AM Will Deacon wrote:
> > >
> > > On Fri, Dec 01, 2023 at 08:54:42PM -0700, Simon Glass wrote:
> > > >
Hi Svyatoslav,
On mar., janv. 09, 2024 at 15:57, Svyatoslav wrote:
> 9 січня 2024 р. 15:54:32 GMT+02:00, Mattijs Korpershoek
> написав(-ла):
>>Hi Svyatoslav,
>>
>>Thank you for the patch.
>>
>>On ven., janv. 05, 2024 at 09:22, Svyatoslav Ryhel wrote:
>>
>>> From: Ion Agorria
>>>
>>> The
Hi Manorit,
Thank you for the patch.
On lun., janv. 08, 2024 at 13:48, Manorit Chawdhry wrote:
> By default this variable is unset and this causes the test condition to
> fail on devices that don't have this defined. Set a default value for
> this.
>
>=> boot
>## Error:
On January 9, 2024 thus sayeth Sumit Garg:
> On Tue, 9 Jan 2024 at 07:24, Bryan Brattlof wrote:
> >
> > On January 8, 2024 thus sayeth Sumit Garg:
> > > Hi Bryan,
> > >
> > > On Sat, 6 Jan 2024 at 02:12, Bryan Brattlof wrote:
> > > >
> > > > Hi Sumit!
> > > >
> > > > On December 28, 2023 thus
On 15:08-20240109, Roger Quadros wrote:
[..]
> > #ifdef CONFIG_BOARD_LATE_INIT
> > +static struct ti_fdt_map ti_am64_evm_fdt_map[] = {
> > + {"am64x_gpevm", "k3-am642-evm.dtb"},
> > + {"am64x_skevm", "k3-am642-sk.dtb"},
>
On 14:15-20240109, Sekhar Nori wrote:
> Entry for physical address 0x5 in memory map table for MMU
> configuration is spilling over and inadvertently making DDR available at
> higher address (above 4GB address space) get mapped as device memory
> (nGnRnE).
>
> Fix this
On 20:48-20240108, Jon Humphreys wrote:
[..]
> > +
> > +#ifdef CONFIG_BOARD_LATE_INIT
> > +int board_late_init(void)
> > +{
> > + ti_set_fdt_env(NULL, NULL);
>
> If a board only has one FDT possible, why not just hard code the path
> here, rather than use the set_fdt_env() logic with NULLs and
On 20:24-20240108, Jon Humphreys wrote:
> Nishanth Menon writes:
>
> > Stop using the findfdt script and switch to setting the fdtfile from C
> > code.
> >
> > While at this, replace findfdt in environment with a warning as it is
> > no longer needed
> >
> > Signed-off-by: Nishanth Menon
> >
On 20:20-20240108, Jon Humphreys wrote:
[...]
> > +config TI_EVM_FDT_FOLDER_PATH
> > + string "Location of Folder path where dtb is present"
> > + default "ti/davinci" if ARCH_DAVINCI
> > + default "ti/keystone" if ARCH_KEYSTONE
> > + default "ti/omap" if ARCH_OMAP2PLUS
> > + default
Hi Manorit,
Thank you for the patch.
On lun., janv. 08, 2024 at 13:48, Manorit Chawdhry wrote:
> Fix a missing semicolon that leads to syntax error while booting j721s2.
>
> Importing environment from mmc1 ...
> syntax error at 'run'HUSH died!
>
> Fixes: 0d72b0f2f83b ("include: env:
Hi Simon,
On Wed, Jan 3, 2024 at 8:47 AM Simon Glass wrote:
>
> Hi Masahiro,
>
> On Wed, Dec 13, 2023 at 5:14 AM Will Deacon wrote:
> >
> > On Fri, Dec 01, 2023 at 08:54:42PM -0700, Simon Glass wrote:
> > > Add a script which produces a Flat Image Tree (FIT), a single file
> > > containing the
"#if" was used instead of "#ifdef"
Fixes: 01a701994b05 ("stm32mp2: initial support")
Signed-off-by: Patrice Chotard
---
arch/arm/mach-stm32mp/include/mach/stm32.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-stm32mp/include/mach/stm32.h
9 січня 2024 р. 15:54:32 GMT+02:00, Mattijs Korpershoek
написав(-ла):
>Hi Svyatoslav,
>
>Thank you for the patch.
>
>On ven., janv. 05, 2024 at 09:22, Svyatoslav Ryhel wrote:
>
>> From: Ion Agorria
>>
>> The dollar test was merged with bagous console behavior, and
>> instead of fixing it,
Hi Svyatoslav,
Thank you for the patch.
On ven., janv. 05, 2024 at 09:22, Svyatoslav Ryhel wrote:
> From: Ion Agorria
>
> The dollar test was merged with bagous console behavior, and
> instead of fixing it, this behavior was just workarounded.
>
> It seems like without the fix the
On Fri, Dec 29, 2023 at 3:39 PM Simon Glass wrote:
>
> Hi Masahiro,
>
> On Thu, Dec 14, 2023 at 7:34 AM Masahiro Yamada wrote:
> >
> > On Thu, Dec 14, 2023 at 3:12 PM Masahiro Yamada
> > wrote:
> > >
> > > On Thu, Dec 14, 2023 at 1:03 PM Chen-Yu Tsai wrote:
> > > >
> > > > On Sun, Dec 10,
Hi Ion,
On jeu., janv. 04, 2024 at 17:44, Ion Agorria wrote:
> Hello,
>
> It seems like without the fix the ut_assert_skipline(); didn't clear
> console and running ut_assert_skipline(); many times would give always
> OK. With my fix the line is cleared correctly and next assert fails
> because
On Wed, Nov 29, 2023 at 11:11 AM Robert Marko wrote:
>
> Currently, Esspresobin FDT is being fixed up directly in ft_board_setup()
> which makes it hard to add support for any other board to be fixed up.
>
> So, lets just move the FDT fixup code to a separate function and call it
> if compatible
On 08/01/2024 19:32, Nishanth Menon wrote:
> Introduce a common fdt operations library for basic device tree
> operations that are common between various boards.
>
> The first library to introduce here is the capability to set up
> fdtfile as a standard variable as part of board identification
On 08/01/2024 19:32, Nishanth Menon wrote:
> We now can provide a map and have the standard fdtfile variable set from
> code itself. This allows for bootstd to "just work".
>
> While at this, replace findfdt in environment with a warning as it is no
> longer needed.
>
> Signed-off-by:
On Tue, 9 Jan 2024 at 03:00, Masahisa Kojima wrote:
>
> Hi Ilias,
>
> On Thu, 28 Dec 2023 at 00:14, Ilias Apalodimas
> wrote:
> >
> > Kojima-san
> >
> > On Thu, Dec 21, 2023 at 06:52:58PM +0900, Masahisa Kojima wrote:
> > > This commit stores the firmware version into the array
> > > of
On 09/01/2024 11:49, MD Danish Anwar wrote:
>
>
> On 09/01/24 2:56 pm, Roger Quadros wrote:
>>
>>
>> On 08/01/2024 12:25, MD Danish Anwar wrote:
>>> On 08/01/24 3:00 pm, Roger Quadros wrote:
On 05/01/2024 12:15, Anwar, Md Danish wrote:
>
>
> On 1/5/2024 1:49 PM,
1 - 100 of 126 matches
Mail list logo
