Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, t
Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, t
Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, t
Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, t
Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, t
Upstream DTS added explicit ranges to the fss node. It did not include
the 32 bit memory space needed by the R5 to access OSPI. With the
upstream DTS sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, the
On Fri, Aug 09, 2024 at 09:56:00PM +0300, Ilias Apalodimas wrote:
> Hi Tom,
>
> The following changes since commit 6f4c31c2b658358628b5b0fa801f55c7477c7585:
>
> Prepare v2024.10-rc2 (2024-08-05 18:13:42 -0600)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/cu
On Fri, Aug 09, 2024 at 08:57:03AM +0300, Svyatoslav Ryhel wrote:
> пт, 9 серп. 2024 р. о 08:49 Heinrich Schuchardt пише:
> >
> >
> >
> > Am 7. August 2024 14:10:24 MESZ schrieb Svyatoslav Ryhel
> > :
> > >TegraPT is compatible with EFI part but it can't pass Protective MBR check.
> > >Skip this
On Fri, Aug 09, 2024 at 06:29:34PM +0200, Richard Weinberger wrote:
> Heinrich,
>
> Am Freitag, 9. August 2024, 18:13:27 CEST schrieb 'Heinrich Schuchardt' via
> upstream:
> > Thank you for pointing at the problematic code.
> >
> > You are calling __builtin_add_overflow(int, int, size_t *).
> >
On Fri, Aug 09, 2024 at 07:23:42PM +0200, Caleb Connolly wrote:
>
>
> On 09/08/2024 08:18, Heinrich Schuchardt wrote:
> >
> >
> > Am 8. August 2024 18:24:24 MESZ schrieb Caleb Connolly
> > :
> > > While U-Boot does a pretty good job at printing information at startup
> > > about what hardware
On 8/9/24 4:17 PM, Jonathan Humphreys wrote:
Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstr
Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, t
Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, t
Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, t
Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, t
Upstream DTS added explicit ranges to the fss node. It did not include
the 32 bit memory space needed by the R5 to access OSPI. With the
upstream DTS sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, the
Upstream DTS added explicit ranges to the fss node. It did not include the
32 bit memory space needed by the R5 to access OSPI. With the upstream DTS
sync, OSPI boot no longer works.
Adding the missing range here. It is also being added in the upstream DTS,
so after the next upstream DTS sync, t
Hi Henrik,
On Fri, 2024-08-09 at 23:08 +0200, Henrik Grimler wrote:
> Hi David,
>
> Thinking about this a bit more...
>
> On Fri, Aug 02, 2024 at 09:19:16PM +0200, David Virag wrote:
[snip]
> > @@ -9,11 +9,15 @@
> > #include
> > #include
> > #include
> > +#if IS_ENABLED(CONFIG_ARCH_EXYNOS4
Hi,
On 7/30/24 23:51, Jonas Karlman wrote:
Add LED=y and LED_GPIO=y to support the onboard leds.
Add ROCKCHIP_IODOMAIN=y to configure correct io voltage domains.
Add DM_MDIO=y now that the DT contain a Ethernet phy node.
Signed-off-by: Jonas Karlman
Reviewed-by: Kever Yang
for the whole s
Hello Alexander,
Thanks for fast response!
On Fri, Aug 09, 2024 at 02:25:04PM +0200, Alexander Dahl wrote:
> Hello Marcus,
>
> Am Fri, Aug 09, 2024 at 02:15:43PM +0200 schrieb Marcus Folkesson:
> > The condition 'ret' is always true as it is never set to other than
> > -EIO.
>
> Technically, yo
Hello all,
We (Eden and I) have been assigned a summer project exploring the possibility
of verified boot for Linux with a view to experiment with a TEE, and would like
to share our outcomes from the project so far.
We've been working on condensing all the information and documentation on TF-A,
сб, 10 серп. 2024 р. о 01:02 Tom Rini пише:
>
> On Fri, Aug 09, 2024 at 08:57:03AM +0300, Svyatoslav Ryhel wrote:
> > пт, 9 серп. 2024 р. о 08:49 Heinrich Schuchardt пише:
> > >
> > >
> > >
> > > Am 7. August 2024 14:10:24 MESZ schrieb Svyatoslav Ryhel
> > > :
> > > >TegraPT is compatible with E
101 - 122 of 122 matches
Mail list logo
