On Thu, 13 Jun 2024 at 23:11, Heinrich Schuchardt wrote:
>
>
>
> Am 13. Juni 2024 21:05:58 MESZ schrieb Simon Glass :
> >Hi Heinrich,
> >
> >On Thu, 13 Jun 2024 at 11:32, Heinrich Schuchardt wrote:
> >>
> >> On 13.06.24 18:59, Simon Glass wrote:
> >> > Hi Tom,
> >> >
> >> > On Thu, 13 Jun 2024
On 6/13/24 4:13 PM, Claudius Heine wrote:
Hi,
I suspect the following patch to oe-core (or local.conf equivalent)
might also entirely mitigate the issue by providing https fallback
automatically, without the need to modify the legacy layer/recipe ?
If so, maybe this could be added to OE LTS
The dm_usb_gadget_handle_interrupts() is not implemented by any USB
gadget controller drivers which do enable DM_USB_GADGET anymore. Set
the symbol as non-weak.
Signed-off-by: Marek Vasut
---
Cc: Alexander Sverdlin
Cc: Felipe Balbi
Cc: Lukasz Majewski
Cc: Mattijs Korpershoek
Cc: Nishanth
Drop dm_usb_gadget_handle_interrupts() in favor of empty default
implementation of the same in drivers/usb/gadget/udc/udc-uclass.c .
Signed-off-by: Marek Vasut
---
Cc: Alexander Sverdlin
Cc: Felipe Balbi
Cc: Lukasz Majewski
Cc: Mattijs Korpershoek
Cc: Nishanth Menon
Cc: Simon Glass
Cc:
Implement .handle_interrupts callback as a replacement for deprecated
dm_usb_gadget_handle_interrupts() function. The new callback allows
for each DM capable USB gadget controller driver to define its own
IRQ handling implementation without colliding with other controller
drivers.
Signed-off-by:
Implement .handle_interrupts callback as a replacement for deprecated
dm_usb_gadget_handle_interrupts() function. The new callback allows
for each DM capable USB gadget controller driver to define its own
IRQ handling implementation without colliding with other controller
drivers.
Signed-off-by:
Implement .handle_interrupts callback as a replacement for deprecated
dm_usb_gadget_handle_interrupts() function. The new callback allows
for each DM capable USB gadget controller driver to define its own
IRQ handling implementation without colliding with other controller
drivers.
Signed-off-by:
Implement .handle_interrupts callback as a replacement for deprecated
dm_usb_gadget_handle_interrupts() function. The new callback allows
for each DM capable USB gadget controller driver to define its own
IRQ handling implementation without colliding with other controller
drivers.
Signed-off-by:
Implement .handle_interrupts callback as a replacement for deprecated
dm_usb_gadget_handle_interrupts() function. The new callback allows
for each DM capable USB gadget controller driver to define its own
IRQ handling implementation without colliding with other controller
drivers.
Signed-off-by:
Implement .handle_interrupts callback as a replacement for deprecated
dm_usb_gadget_handle_interrupts() function. The new callback allows
for each DM capable USB gadget controller driver to define its own
IRQ handling implementation without colliding with other controller
drivers.
Signed-off-by:
Implement .handle_interrupts callback as a replacement for deprecated
dm_usb_gadget_handle_interrupts() function. The new callback allows
for each DM capable USB gadget controller driver to define its own
IRQ handling implementation without colliding with other controller
drivers.
Signed-off-by:
Introduce .ops for USB_GADGET_GENERIC uclass. The first new ops is
.handle_interrupts which must be implemented by DM capable USB gadget
controller drivers and must implement interrupt handling similar to
dm_usb_gadget_handle_interrupts(). This patch currently provides weak
Implement .handle_interrupts callback as a replacement for deprecated
dm_usb_gadget_handle_interrupts() function. The new callback allows
for each DM capable USB gadget controller driver to define its own
IRQ handling implementation without colliding with other controller
drivers.
Keep the
Introduce .ops for USB_GADGET_GENERIC uclass. The first new ops is
.handle_interrupts which must be implemented by DM capable USB gadget
controller drivers and must implement interrupt handling similar to
dm_usb_gadget_handle_interrupts(). For DM USB gadget drivers this is
a replacement for
On Thu, May 30, 2024 at 03:06:31PM -0700, Tim Harvey wrote:
> This series will automatically add /chosen/kaslr-seed to the dt if DM_RNG is
> enabled
> during the boot process.
>
> If RANDOMIZE_BASE is enabled in the Linux kernel instructing it to
> randomize the virtual address at which the
Move to the new documentation style with rST formatting.
Signed-off-by: Vasileios Amoiridis
---
doc/README.bootcount | 53 ---
doc/api/bootcount.rst | 58 +++
2 files changed, 58 insertions(+), 53 deletions(-)
delete
Add support to save boot count variable in ANY filesystem. Tested with
FAT and EXT.
Reviewed-by: Tom Rini
Reviewed-by: Heiko Schocher
Reviewed-by: Philip Oberfichtner
Signed-off-by: Vasileios Amoiridis
---
doc/README.bootcount | 12 +++
drivers/bootcount/Kconfig
Changes in v3:
- Remove specific CONFIGs for filesystems
- Add message to prompt user to enable required write function
- Use tags from previous rounds
- Move documentation to rST
v2:
https://lore.kernel.org/u-boot/20240610185116.353604-1-vassilisa...@gmail.com
On Thu, Jun 13, 2024 at 4:47 PM Robert Nelson wrote:
>
> On Thu, Jun 13, 2024 at 3:06 AM Dhruva Gole wrote:
> >
> > The Kernel Image and DTB files are supposed to be picked from the rootfs
> > of the SD Card, this fails in legacy boot flow because bootpart is set
> > to 1:1. Fix it.
>
> and
On Thu, Jun 13, 2024 at 3:06 AM Dhruva Gole wrote:
>
> The Kernel Image and DTB files are supposed to be picked from the rootfs
> of the SD Card, this fails in legacy boot flow because bootpart is set
> to 1:1. Fix it.
and where is that rule defined?
Production boards ship with Kernel Image and
Le 13/06/2024 à 12:13, Mattijs Korpershoek a écrit :
Add a unit test for testing the Android bootmethod.
This requires another mmc image (mmc7) to contain the following partitions:
- misc: contains the Bootloader Control Block (BCB)
- boot_a: contains a fake generic kernel image
-
On Thu, 13 Jun 2024 at 22:57, Heinrich Schuchardt wrote:
>
> On 13.06.24 18:59, Simon Glass wrote:
> > Hi Tom,
> >
> > On Thu, 13 Jun 2024 at 09:42, Tom Rini wrote:
> >>
> >> On Thu, Jun 13, 2024 at 09:22:15AM -0600, Simon Glass wrote:
> >>> Hi Tom,
> >>>
> >>> On Wed, 12 Jun 2024 at 15:40, Tom
On Tue, 04 Jun 2024 11:39:09 +0530, Manorit Chawdhry wrote:
> The series enables ospi boot for j721s2.
>
> Test logs:
> https://gist.github.com/manorit2001/6bb91885c608e3a8cb0267ab2c614781
>
>
Applied to u-boot/next, thanks!
--
Tom
The EFI Capsule ESL file (EFI Signature List File) used for authentication
is a binary generated from the EFI Capsule public key certificate. Instead
of including it in the source repo, automatically generate it from the
certificate file during the build process.
Currently, sandbox is the only
Use the capsule's public key certificate rather than a prebuilt ESL
generated from the certificate. The ESL is now generated as part of the
build.
Changes from v1:
- Converted the single patch to a series to include a bug fix found during
development.
- Created an explicit rule for creating the
The call to cmd_capsule_esl_gen was made directly rather than using the
"cmd,xxx" syntax.
Fixes: c7d4dfcd ("scripts/Makefile.lib: Embed capsule public key in
platform's dtb")
Signed-off-by: Jonathan Humphreys
---
scripts/Makefile.lib | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Ilias Apalodimas writes:
> Hi Jon,
>
> On Sat, 8 Jun 2024 at 02:44, Jonathan Humphreys wrote:
>>
>> Add to the capsule update porting documentation that when capsule
>> authentication is enabled (via EFI_CAPSULE_AUTHENTICATE), a public key
>> certificate corresponding to the capsule signing key
Am 13. Juni 2024 21:05:58 MESZ schrieb Simon Glass :
>Hi Heinrich,
>
>On Thu, 13 Jun 2024 at 11:32, Heinrich Schuchardt wrote:
>>
>> On 13.06.24 18:59, Simon Glass wrote:
>> > Hi Tom,
>> >
>> > On Thu, 13 Jun 2024 at 09:42, Tom Rini wrote:
>> >>
>> >> On Thu, Jun 13, 2024 at 09:22:15AM -0600,
On Thu, Jun 13, 2024 at 10:59:48AM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Thu, 13 Jun 2024 at 09:42, Tom Rini wrote:
> >
> > On Thu, Jun 13, 2024 at 09:22:15AM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Wed, 12 Jun 2024 at 15:40, Tom Rini wrote:
> > > >
> > > > On Wed, Jun 12,
Hi,
Le 13/06/2024 à 12:13, Mattijs Korpershoek a écrit :
When calling android_image_get_dtb_by_index() using boot image v3+,
we should also pass the vendor_boot ramdisk address.
Use get_avendor_bootimg_addr() to do so.
Notes: on boot image v2, this is harmless since get_avendor_bootimg_addr()
Hi Sughosh,
On Thu, 13 Jun 2024 at 12:17, Sughosh Ganu wrote:
>
> On Thu, 13 Jun 2024 at 22:57, Heinrich Schuchardt wrote:
> >
> > On 13.06.24 18:59, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Thu, 13 Jun 2024 at 09:42, Tom Rini wrote:
> > >>
> > >> On Thu, Jun 13, 2024 at 09:22:15AM
Hi Heinrich,
On Thu, 13 Jun 2024 at 11:32, Heinrich Schuchardt wrote:
>
> On 13.06.24 18:59, Simon Glass wrote:
> > Hi Tom,
> >
> > On Thu, 13 Jun 2024 at 09:42, Tom Rini wrote:
> >>
> >> On Thu, Jun 13, 2024 at 09:22:15AM -0600, Simon Glass wrote:
> >>> Hi Tom,
> >>>
> >>> On Wed, 12 Jun 2024
On 13.06.24 18:59, Simon Glass wrote:
Hi Tom,
On Thu, 13 Jun 2024 at 09:42, Tom Rini wrote:
On Thu, Jun 13, 2024 at 09:22:15AM -0600, Simon Glass wrote:
Hi Tom,
On Wed, 12 Jun 2024 at 15:40, Tom Rini wrote:
On Wed, Jun 12, 2024 at 02:24:25PM -0600, Simon Glass wrote:
Hi Tom,
On Wed,
Le 13/06/2024 à 12:13, Mattijs Korpershoek a écrit :
The only way to configure the load addresses for both bootimg and
vendor_bootimg is by using the "abootimg" command.
If we want to use the C API, there is no equivalent.
Add set_abootimg_addr() and set_avendor_bootimg_addr() so that we can
Le 13/06/2024 à 12:13, Mattijs Korpershoek a écrit :
Some bootflows might be able to only boot from MMC devices.
Add a helper function these bootflows can use.
Reviewed-by: Igor Opaniuk
Signed-off-by: Mattijs Korpershoek
---
boot/bootflow.c| 12
include/bootflow.h | 9
On Fri, May 31, 2024 at 06:48:34AM +, Thomas Perl wrote:
> Foramt -> Format
>
> Signed-off-by: Thomas Perl
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
Hi Jonas,
On 6/13/24 09:16, Jonas Kvinge wrote:
> Hi,
>
> I'm running openSUSE Tumbleweed on an RPI CM4, I'm trying to silence u-
> boot boot messages, with the default configuration there is an u-boot
> logo on the top right corner and boot text, I'd like to get rid of the
> logo and all text
On Thu, Jun 13, 2024 at 12:13 PM Mattijs Korpershoek
wrote:
>
> When calling android_image_get_dtb_by_index() using boot image v3+,
> we should also pass the vendor_boot ramdisk address.
>
> Use get_avendor_bootimg_addr() to do so.
>
> Notes: on boot image v2, this is harmless since
On Thu 13 Jun 2024 at 17:42, Mattijs Korpershoek
wrote:
> When calling android_image_get_dtb_by_index() using boot image v3+,
> we should also pass the vendor_boot ramdisk address.
>
> Use get_avendor_bootimg_addr() to do so.
>
> Notes: on boot image v2, this is harmless since
Hi Tom,
On Thu, 13 Jun 2024 at 09:42, Tom Rini wrote:
>
> On Thu, Jun 13, 2024 at 09:22:15AM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Wed, 12 Jun 2024 at 15:40, Tom Rini wrote:
> > >
> > > On Wed, Jun 12, 2024 at 02:24:25PM -0600, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On
On Wed, Jun 12, 2024 at 02:24:24PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Wed, 12 Jun 2024 at 11:07, Tom Rini wrote:
> >
> > On Wed, Jun 12, 2024 at 05:14:46PM +0100, Jiaxun Yang wrote:
> > >
> > >
> > > 在2024年6月12日六月 下午5:01，Tom Rini写道：
> > > > On Tue, Jun 11, 2024 at 10:04:13PM +0100,
Hi Jon,
On Sat, 8 Jun 2024 at 02:44, Jonathan Humphreys wrote:
>
> Add to the capsule update porting documentation that when capsule
> authentication is enabled (via EFI_CAPSULE_AUTHENTICATE), a public key
> certificate corresponding to the capsule signing key must be specified.
>
> Also add a
On Mon, 10 Jun 2024 18:11:44 +0200, Quentin Schulz wrote:
> There's never been a -q or -s argument handled in the command, so let's
> remove it. This was highlighted during review[1] but somehow still got
> through.
>
> While at it, slightly "reword" in the help text how the len + freq
>
On Mon, Jun 10, 2024 at 02:43:17PM -0500, Sam Protsenko wrote:
> On Tue, May 14, 2024 at 3:26 PM Sam Protsenko
> wrote:
> >
> > On Wed, May 1, 2024 at 4:12 PM Sam Protsenko
> > wrote:
> > >
> > > On Wed, Apr 10, 2024 at 9:53 PM Sean Anderson wrote:
> > > >
> > > > On 3/7/24 19:04, Sam
On Thu, Jun 13, 2024 at 09:22:15AM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Wed, 12 Jun 2024 at 15:40, Tom Rini wrote:
> >
> > On Wed, Jun 12, 2024 at 02:24:25PM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Wed, 12 Jun 2024 at 11:22, Tom Rini wrote:
> > > >
> > > > On Tue, Jun 11,
On Sat, 08 Jun 2024 06:12:44 +0200, Heinrich Schuchardt wrote:
> %s/prbing/probing/
>
>
Applied to u-boot/master, thanks!
--
Tom
On Wed, Jun 12, 2024 at 07:15:11PM -0600, Simon Glass wrote:
> The top part of each of the u-boot-test-* files is common. Put it in
> a common script file to avoid duplication and to allow it to be
> replaced for the Labgrid integration.
>
> Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
On Thu, Jun 13, 2024 at 01:37:31PM +0200, Heinrich Schuchardt wrote:
> Dear Tom,
>
> The following changes since commit 1ebd659cf020843fd8e8ef90d85a66941cbab6ec:
>
> Merge tag 'u-boot-dfu-20240606' of
> https://source.denx.de/u-boot/custodians/u-boot-dfu (2024-06-06 08:24:15
> -0600)
>
> are
On Thu, 13 Jun 2024 at 04:13, Mattijs Korpershoek
wrote:
>
> When calling android_image_get_dtb_by_index() using boot image v3+,
> we should also pass the vendor_boot ramdisk address.
>
> Use get_avendor_bootimg_addr() to do so.
>
> Notes: on boot image v2, this is harmless since
Hi Tom,
On Wed, 12 Jun 2024 at 15:40, Tom Rini wrote:
>
> On Wed, Jun 12, 2024 at 02:24:25PM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Wed, 12 Jun 2024 at 11:22, Tom Rini wrote:
> > >
> > > On Tue, Jun 11, 2024 at 08:41:39PM -0600, Simon Glass wrote:
> > >
> > > [snip]
> > > > Also IMO
On Thu, 13 Jun 2024 at 04:13, Mattijs Korpershoek
wrote:
>
> The only way to configure the load addresses for both bootimg and
> vendor_bootimg is by using the "abootimg" command.
> If we want to use the C API, there is no equivalent.
>
> Add set_abootimg_addr() and set_avendor_bootimg_addr() so
On Thu 13 Jun 2024 at 16:16, Mattijs Korpershoek
wrote:
> The only way to configure the load addresses for both bootimg and
> vendor_bootimg is by using the "abootimg" command.
> If we want to use the C API, there is no equivalent.
>
> Add set_abootimg_addr() and set_avendor_bootimg_addr()
Hi Marek,
On 2024-06-13 3:12 pm, Marek Vasut wrote:
On 6/13/24 9:49 AM, Claudius Heine wrote:
Hi,
[...]
Also, while I checked OE-Core, other third party/community maintained
layer could be impacted. I assume this is the case of
meta-amarula-engicam[1] and meta-allwinner-hx[2] for example.
On Tue, May 28, 2024 at 01:43:01PM +0530, Manorit Chawdhry wrote:
> vd_data remains the same for most of the SoCs but there are some
> differences in power domains and clocks that don't need a change to
> compatible and can be handled at SoC level.
>
> Change the data population logic from
On Thu 13 Jun 2024 at 16:19, Mattijs Korpershoek
wrote:
> Add a unit test for testing the Android bootmethod.
>
> This requires another mmc image (mmc7) to contain the following partitions:
> - misc: contains the Bootloader Control Block (BCB)
> - boot_a: contains a fake generic kernel image
On Thu 13 Jun 2024 at 16:18, Mattijs Korpershoek
wrote:
> Android boot flow is a bit different than a regular Linux distro.
> Android relies on multiple partitions in order to boot.
>
> A typical boot flow would be:
> 1. Parse the Bootloader Control Block (BCB, misc partition)
> 2. If BCB
On Thu 13 Jun 2024 at 16:15, Mattijs Korpershoek
wrote:
> Some bootflows might be able to only boot from MMC devices.
>
> Add a helper function these bootflows can use.
>
> Reviewed-by: Igor Opaniuk
> Signed-off-by: Mattijs Korpershoek
> ---
> boot/bootflow.c| 12
>
On 6/13/24 9:49 AM, Claudius Heine wrote:
Hi,
[...]
Also, while I checked OE-Core, other third party/community maintained
layer could be impacted. I assume this is the case of
meta-amarula-engicam[1] and meta-allwinner-hx[2] for example.
I would suggest sending a mail to the different
Hi,
I'm running openSUSE Tumbleweed on an RPI CM4, I'm trying to silence u-
boot boot messages, with the default configuration there is an u-boot
logo on the top right corner and boot text, I'd like to get rid of the
logo and all text if possible.
The keyboard is not working before the Linux
Hi Dhruva,
On 13/06/24 13:36, Dhruva Gole wrote:
The Kernel Image and DTB files are supposed to be picked from the rootfs
of the SD Card, this fails in legacy boot flow because bootpart is set
to 1:1. Fix it.
Fixes: a200f428b5b21 ("board: ti: am62x: Add am62x_beagleplay_* defconfigs and env
Support alternative compatible for fixed-plls clocks used upstream with
the compatible mediatek,mt7986-apmixedsys.
Signed-off-by: Christian Marangi
---
drivers/clk/mediatek/clk-mt7986.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/mediatek/clk-mt7986.c
Support alternative compatible for fixed-plls clocks used upstream with
the compatible mediatek,mt7988-apmixedsys.
Signed-off-by: Christian Marangi
---
drivers/clk/mediatek/clk-mt7988.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/mediatek/clk-mt7988.c
Set pcie-phy optional for PCIe gen3. MT7988 doesn't require it and
making it mandatory prevent the driver to correctly probe.
Signed-off-by: Christian Marangi
---
drivers/pci/pcie_mediatek_gen3.c | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git
Upstream kernel linux define pinctrl for uart0, hence this pin group
and pinctrl driver is needed before relocation. Add DM_FLAG_PRE_RELOC
flag to init and mute mtk_serial error on early serial init.
Signed-off-by: Christian Marangi
---
drivers/pinctrl/mediatek/pinctrl-mt7981.c | 1 +
1 file
Add support for gpio-controller property in root pinctrl node.
This is to follow upstream linux DTSI that doesn't define the
gpio-controller and cells in dedicated nodes.
Signed-off-by: Christian Marangi
---
drivers/pinctrl/mediatek/pinctrl-mtk-common.c | 10 ++
1 file changed, 10
Support alternative compatible for fixed-plls clocks used upstream with
the compatible mediatek,mt7981-apmixedsys.
Signed-off-by: Christian Marangi
---
drivers/clk/mediatek/clk-mt7981.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/mediatek/clk-mt7981.c
Add support for upstream linux clock and map U-Boot property to the one
use in upstream linux where supported.
Also add handling for the use_internal_cd that on upstream is hardcoded
enabled on mt7620.
Signed-off-by: Christian Marangi
---
drivers/mmc/mtk-sd.c | 35
Upstream linux serial driver use a different logic to setup serial regs.
They have 2 interval:
- < 115200 we use lowspeed regs and 16 * baud
- >= 115200 we use highspeed
We currently use force_highspeed property to force usage of highspeed
regs even with low baud rate.
Add special handling if
Upstream linux also provide the additional optional bus clock.
Add support for it and also enable the baud and bus clock on probe.
Signed-off-by: Christian Marangi
---
drivers/serial/serial_mtk.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/serial/serial_mtk.c
Add support for optional arb and pmic clock for i2c provided in upstream
linux DTSI.
Signed-off-by: Christian Marangi
---
drivers/i2c/mtk_i2c.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/drivers/i2c/mtk_i2c.c b/drivers/i2c/mtk_i2c.c
index
Handle alternative name for pn_swap property as upstream linux use
mediatek,pnswap.
Signed-off-by: Christian Marangi
---
drivers/net/mtk_eth.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/mtk_eth.c b/drivers/net/mtk_eth.c
index 75e7bcf83b7..87e2e1d9cda
Upstream kernel linux use a different compatible mediatek,spi-ipm.
Add support for this compatible and add handling for the additional
clock similar to how it's done by the upstream driver and handling for
all the property enabled by default.
Signed-off-by: Christian Marangi
---
From: John Crispin
Add MediaTek GEN3 PCIe controller support for filogic silicon.
This is adapted from the Linux version of the driver.
Signed-off-by: John Crispin
[ fix minor problems, fix checkpatch errors ]
Signed-off-by: Christian Marangi
---
drivers/pci/Kconfig | 7 +
Add support for PHY type switch via the mediatek topmisc syscon.
This is needed on mt7981 to make the PCIe correctly work and display
LinkUp.
Follow the same implementation done on Linux kernel with the usage of
the mediatek,syscon-type property.
Example:
u3port0: usb-phy@11e10700 {
This is an initial series that have all the initial trivial
fixes required for usage of OF_UPSTREAM for the mediatek SoC
This also contains the pcie-gen3 driver and the required tphy
support driver to make it work.
Subsequent series will follow with conversion of the mtk-clk
to permit usage of
Some bootflows might be able to only boot from MMC devices.
Add a helper function these bootflows can use.
Reviewed-by: Igor Opaniuk
Signed-off-by: Mattijs Korpershoek
---
boot/bootflow.c| 12
include/bootflow.h | 9 +
2 files changed, 21 insertions(+)
diff --git
When calling android_image_get_dtb_by_index() using boot image v3+,
we should also pass the vendor_boot ramdisk address.
Use get_avendor_bootimg_addr() to do so.
Notes: on boot image v2, this is harmless since get_avendor_bootimg_addr()
returns -1.
for legacy implementations that
Android boot flow is a bit different than a regular Linux distro.
Android relies on multiple partitions in order to boot.
A typical boot flow would be:
1. Parse the Bootloader Control Block (BCB, misc partition)
2. If BCB requested bootonce-bootloader, start fastboot and wait.
3. If BCB requested
The only way to configure the load addresses for both bootimg and
vendor_bootimg is by using the "abootimg" command.
If we want to use the C API, there is no equivalent.
Add set_abootimg_addr() and set_avendor_bootimg_addr() so that we can
specify the load address from C.
This can be useful for
Dear Tom,
The following changes since commit 1ebd659cf020843fd8e8ef90d85a66941cbab6ec:
Merge tag 'u-boot-dfu-20240606' of
https://source.denx.de/u-boot/custodians/u-boot-dfu (2024-06-06 08:24:15
-0600)
are available in the Git repository at:
48b3ecbe replumbed the gpio-hog probing to use DM_FLAG_PROBE_AFTER_BIND.
Unfortunately gpio_post_bind is called after the non-preloc recursive
dm_probe_devices completes, so setting this flag does not have the intended
effect and the gpio-hogs never get probed. With instrumentation:
[...]
Migrate imx6ulz_bsh_smm_m2 board to OF_UPSTREAM.
Signed-off-by: Patrick Barsanti
---
This breaks compilation because upstream and local DTs are different.
The Makefile gives priority to the local DT headers, which are missing
a define, specifically in `imx6ul-clock.h`. As of now, upstreamed
Add a unit test for testing the Android bootmethod.
This requires another mmc image (mmc7) to contain the following partitions:
- misc: contains the Bootloader Control Block (BCB)
- boot_a: contains a fake generic kernel image
- vendor_boot_a: contains a fake vendor_boot image
Also add
Android boot flow is a bit different than a regular Linux distro.
Android relies on multiple partitions in order to boot.
A typical boot flow would be:
1. Parse the Bootloader Control Block (BCB, misc partition)
2. If BCB requested bootonce-bootloader, start fastboot and wait.
3. If BCB requested
On 13/06/2024 09.32, Claudius Heine wrote:
>> I'm just wondering if it's possible to have the server send some message
>> to the client when the git protocol is used, for some deprecation period
>> (6 months?), so a developer doing "git remote update" will get notified.
>> He would then also have
The Kernel Image and DTB files are supposed to be picked from the rootfs
of the SD Card, this fails in legacy boot flow because bootpart is set
to 1:1. Fix it.
Fixes: a200f428b5b21 ("board: ti: am62x: Add am62x_beagleplay_* defconfigs and
env file")
Signed-off-by: Dhruva Gole
---
Am 12.06.24 um 18:16 schrieb Daniel Schultz:
We moved our documentation to another hoster and therefore the URL
changed. Point to the latest documentation instead of release versions
to not link out-dated documentation.
Signed-off-by: Daniel Schultz
For all three patches,
Reviewed-by:
Hi Quentin,
On 2024-06-12 12:37 pm, Quentin Schulz wrote:
Hi Claudius,
On 6/12/24 12:20 PM, Claudius Heine wrote:
Hi everyone,
in the past we used cgit, which provided cloning the u-boot repo via
http, https, ssh and the git protocol.
When we migrated to gitlab, which doesn't support the
Hi Rasmus,
On 2024-06-12 1:18 pm, Rasmus Villemoes wrote:
On 12/06/2024 12.20, Claudius Heine wrote:
Hi everyone,
in the past we used cgit, which provided cloning the u-boot repo via
http, https, ssh and the git protocol.
When we migrated to gitlab, which doesn't support the git protocol, we
Hi Sumit
On Thu, Jun 13, 2024 at 9:02 AM Sumit Garg wrote:
>
> On Mon, 3 Jun 2024 at 20:38, Patrick Barsanti
> wrote:
> >
> > Always prioritizing u-boot includes causes problems when trying to migrate
> > boards to OF_UPSTREAM that have different local devicetree files with
> > respect to the
On Mon, 3 Jun 2024 at 20:38, Patrick Barsanti
wrote:
>
> Always prioritizing u-boot includes causes problems when trying to migrate
> boards to OF_UPSTREAM that have different local devicetree files with
> respect to the upstream ones, if local DT headers are not dropped.
> At the same time if
91 matches
Mail list logo
