On 2024-02-26 02:47, Tom Rini wrote:
> On Mon, Feb 26, 2024 at 01:02:04AM +0100, Jonas Karlman wrote:
>> On 2024-02-25 23:01, Marek Vasut wrote:
>>> On 2/25/24 4:27 PM, Jonas Karlman wrote:
Build fail with the following error when DM_USB_GADGET is enabled and
USB_DWC3_GADGET is disabled:
Allow boards that use ti_spl_template to not use optee part in
configuration.
Vendor can have module with 256 Mb of memory and they try to optimize
the available memory just using the essential components.
This change allow to remove tee from configuration without binman
fail.
configurations {
This patch is to enable Agilex5 platform for Intel
product. Changes, modification and new files are
created for board, dts, configs and makefile to
create the base for Agilex5.
Signed-off-by: Jit Loon Lim
---
Changes v1 -> v2:
- fixed git auto merge issue
---
arch/arm/Kconfig
V1:
https://patchwork.ozlabs.org/project/uboot/patch/20240220143603.22091-1-jit.loon@intel.com/
V2: Fixed Git auto-merge causing misalignment of code and insert/delete
Jit Loon Lim (1):
arch:arm: Agilex5 enablement
arch/arm/Kconfig | 13 +-
Hi
On Mon, Feb 26, 2024 at 4:17 AM Neha Malcom Francis wrote:
>
> Hi Michael
>
> + Vignesh
>
> On 25/02/24 23:08, Michael Trimarchi wrote:
> > Boards can use the ti_spl_template but avoid to define a tee
> > node to be loaded. This is true form board with 512Mb or less
>
> s/form board/for
Thanks
Best Regards
JL Lim (Benjamin)
> -Original Message-
> From: Chee, Tien Fong
> Sent: Wednesday, February 21, 2024 2:25 PM
> To: Lim, Jit Loon ; u-boot@lists.denx.de
> Cc: Jagan Teki ; Marek ;
> Simon ; Hea, Kok Kiang
> ; Maniyam, Dinesh ;
> Ng, Boon Khai ; Yuslaimi, Alif Zakuan
[Ported to U-Boot from the Linux kernel, commit 78933218f5c, original
author Kamal Dasu ]
The following description is from that patch:
If both nand-ecc-strength and nand-ecc-step-size are not specified in
device tree node for NAND, raw NAND layer does detect ECC information by
reading ONFI
Set soc->ctrl so that the prepare_data_bus callback is used if it has
been specified by the soc.
Signed-off-by: Mark Tomlinson
Cc: Dario Binacchi
Cc: Michael Trimarchi
---
drivers/mtd/nand/raw/brcmnand/brcmnand.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
"Kumar, Udit" writes:
> Thanks Jon
>
> On 2/24/2024 5:53 AM, Jonathan Humphreys wrote:
>> The phy calibration pattern partition isn't needed as the Cadence driver
>> isn't
>> calibrating the phys.
>
>
> Please do mention Fixes tag here
>
> 58d61fb5a77e ("arm: dts: k3-j721e-sk: Add initial A72
Hi Michael
+ Vignesh
On 25/02/24 23:08, Michael Trimarchi wrote:
Boards can use the ti_spl_template but avoid to define a tee
node to be loaded. This is true form board with 512Mb or less
s/form board/for boards? I am guessing that is what was meant. I am not really
understanding the commit
On Mon, Feb 26, 2024 at 01:02:04AM +0100, Jonas Karlman wrote:
> On 2024-02-25 23:01, Marek Vasut wrote:
> > On 2/25/24 4:27 PM, Jonas Karlman wrote:
> >> Build fail with the following error when DM_USB_GADGET is enabled and
> >> USB_DWC3_GADGET is disabled:
> >>
> >>dwc3/dwc3-generic.o: in
Currently, if the environment is stored on an MMC device, the device
number is hardcoded by CONFIG_SYS_MMC_ENV_DEV. This is problematic
because many boards can choose between booting from an SD card or a
removable eMMC. For example, the Rock64 defconfig sets
CONFIG_SYS_MMC_ENV_DEV=1, which
On 2024-02-25 23:01, Marek Vasut wrote:
> On 2/25/24 4:27 PM, Jonas Karlman wrote:
>> Build fail with the following error when DM_USB_GADGET is enabled and
>> USB_DWC3_GADGET is disabled:
>>
>>dwc3/dwc3-generic.o: in function `dm_usb_gadget_handle_interrupts':
>>
On 2/25/24 4:27 PM, Jonas Karlman wrote:
Build fail with the following error when DM_USB_GADGET is enabled and
USB_DWC3_GADGET is disabled:
dwc3/dwc3-generic.o: in function `dm_usb_gadget_handle_interrupts':
dwc3/dwc3-generic.c:201:(.text.dm_usb_gadget_handle_interrupts+0x10):
On 2/25/24 5:07 PM, Janne Grunau wrote:
Hej,
On Wed, Feb 21, 2024, at 13:41, Marek Vasut wrote:
On 2/21/24 08:25, Janne Grunau via B4 Relay wrote:
From: Hector Martin
We currently only support one USB keyboard device, but some devices
emulate keyboards for other purposes. Most commonly,
On 2/25/24 4:28 PM, Janne Grunau wrote:
On Wed, Feb 21, 2024, at 13:39, Marek Vasut wrote:
On 2/21/24 08:25, Janne Grunau via B4 Relay wrote:
From: Janne Grunau
Apple USB keyboards carry the HID keyboard boot protocol on the second
interface. Using the second interface in the USB keyboard
On RK3399 the USB2PHY regs are located in the common GRF, remaining SoCs
that is supported by this driver have the USB2PHY regs in a different
GRF.
When support for RK356x, RK3588 and RK3328 was added this driver was
never updated to use correct GRF and have instead incorrectly written
to wrong
The USB2PHY regs already contain working default reset values for RK3328
and RK35xx as evidenced by the fact that this driver never has changed a
single value for these SoCs.
Reduce to only configure utmi_suspend_n and utmi_sel bits similar to
what is currently done on RK3399. Also add missing
This series fixes an issue where the rockchip-inno-usb2 driver is
writing to wrong GRF reg for RK3328, RK356x and RK3588.
The driver is currently always using the common GRF, something that is
only correct for RK3399. Remaining SoCs have USB2PHY regs in a different
or dedicated usb2phy GRF.
On Sun, Feb 25, 2024 at 01:05:28PM +0300, Matwey V. Kornilov wrote:
> As far as I remember not all Rock64 are supplied with soldered SPI.
That's unfortunate. I see that now too in the fine print on the product
page. I think I can come up with an alternate solution using
mmc_get_env_dev() as is
Boards can use the ti_spl_template but avoid to define a tee
node to be loaded. This is true form board with 512Mb or less
memory. We can limit this in configuation removing the tee
node
configurations {
default = "conf-0";
conf-0 {
description = "k3-am62_ccm_m3";
Hej,
On Wed, Feb 21, 2024, at 13:41, Marek Vasut wrote:
> On 2/21/24 08:25, Janne Grunau via B4 Relay wrote:
>> From: Hector Martin
>>
>> We currently only support one USB keyboard device, but some devices
>> emulate keyboards for other purposes. Most commonly, people run into
>> this with
On Sun, Feb 25, 2024 at 03:27:13PM +, Jonas Karlman wrote:
> Build fail with the following error when DM_USB_GADGET is enabled and
> USB_DWC3_GADGET is disabled:
>
> dwc3/dwc3-generic.o: in function `dm_usb_gadget_handle_interrupts':
>
Build fail with the following error when DM_USB_GADGET is enabled and
USB_DWC3_GADGET is disabled:
dwc3/dwc3-generic.o: in function `dm_usb_gadget_handle_interrupts':
dwc3/dwc3-generic.c:201:(.text.dm_usb_gadget_handle_interrupts+0x10):
undefined reference to
Hej,
On Wed, Feb 21, 2024, at 13:40, Marek Vasut wrote:
> On 2/21/24 08:25, Janne Grunau via B4 Relay wrote:
>> From: Janne Grunau
>>
>> Discovered while trying to use the second interface in the USB keyboard
>> driver necessary on Apple USB keyboards.
>>
>> Signed-off-by: Janne Grunau
>> ---
On Wed, Feb 21, 2024, at 13:39, Marek Vasut wrote:
> On 2/21/24 08:25, Janne Grunau via B4 Relay wrote:
>> From: Janne Grunau
>>
>> Apple USB keyboards carry the HID keyboard boot protocol on the second
>> interface. Using the second interface in the USB keyboard driver does
>> not work since
> From: Peter Robinson
> Date: Sun, 25 Feb 2024 14:14:55 +
>
> The EFI spec states that the ESP can be any of FAT12/16/32 but for
> compatibility doesn't necssarily require the partition to be the
> EFI partition table ID of 0xef. A number of arm devices will not
> find their firmware on a
The EFI spec states that the ESP can be any of FAT12/16/32 but for
compatibility doesn't necssarily require the partition to be the
EFI partition table ID of 0xef. A number of arm devices will not
find their firmware on a FAT partition with an ID of 0xef so also
allow the original FAT12/16/32
Hi Peter,
USB_ETHER_LAN78XX is already enabled in the defconfig for Pi 3b plus. But
the eth_get_ethaddr is returning null
https://github.com/u-boot/u-boot/blob/1a66a7768af7e8106c2cd93a19f4013877fb85ae/include/net.h#L199
Do you know why this is not handled?
On Sun, Feb 25, 2024, 14:49 Peter
Hi,
> I have a Raspberry Pi 3B Plus which I want to integrate with U-boot
> (v2023.10) .
>
> I am using rpi_3_32b_defconfig to generate u-boot.bin. But while booting I
> am getting below error
>
> Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
> In:serial,usbkbd
>
On Sat, Feb 24, 2024 at 01:51:46AM +0530, Apurva Nandan wrote:
> Add board files for J784S4 EVM.
>
> SYS_DISABLE_DCACHE_OPS is selected in the Kconfig because
> J784S4/AM69 are a coherent architecture at A72 level by
> MSMC support.
>
> Signed-off-by: Hari Nagalla
> Signed-off-by: Dasnavis
On Sun, Feb 25, 2024 at 10:17:06AM +0530, Kumar, Udit wrote:
> Thanks Jon
>
> On 2/24/2024 5:53 AM, Jonathan Humphreys wrote:
> > The phy calibration pattern partition isn't needed as the Cadence driver
> > isn't
> > calibrating the phys.
>
>
> Please do mention Fixes tag here
>
>
On Sat, Feb 24, 2024 at 07:21:17PM -0300, Fabio Estevam wrote:
> Hi Tom,
>
> Please pull from u-boot-imx, thanks.
>
> The following changes since commit bb9d6c7f4f6a598e8856b2e19e58c7de078a0d6e:
>
> Merge tag 'u-boot-amlogic-fixes-20240223' of
>
Hi,
On Sun, 25 Feb 2024 at 12:25, Sourabh Hegde Ramu
wrote:
>
> Hi Anand,
>
> Thanks for the update.
>
> Yes, I can set it manually. But this should be done by u-boot, right? Is
> there any reason why this is not happening on Pi 3b plus?
> I have other Raspberry Pi (4 & 3b) and they are working
As far as I remember not all Rock64 are supplied with soldered SPI.
вс, 25 февр. 2024 г. в 02:52, Ben Wolsieffer :
>
> Currently, U-Boot attempts to store the environment in MMC 0, which
> doesn't work when an eMMC is used without an SD card. There is an SPI
> flash chip on the board, so use that
35 matches
Mail list logo
