On Sun, Mar 30, 2025 at 04:38:12PM +0200, Caleb Connolly wrote:
> Hi Heinrich,
>
> On 3/28/25 15:18, Heinrich Schuchardt wrote:
> > On 28.03.25 14:00, Caleb Connolly wrote:
> > >
> > >
> > > On 3/28/25 13:01, Simon Glass wrote:
> > > > Hi Caleb,
> > > >
> > > > On Sun, 23 Mar 2025 at 12:39, Cal
Hi all,
Reviving this as it is still very much an issue, and especially relevant
for Qualcomm platforms.
On 11/3/23 20:44, Simon Glass wrote:
Hi Heinrich,
On Wed, 25 Oct 2023 at 15:22, Heinrich Schuchardt
wrote:
On 10/25/23 23:13, Tom Rini wrote:
On Wed, Oct 25, 2023 at 10:28:05PM +0200,
Hi Caleb,
On Mon, 31 Mar 2025 at 03:38, Caleb Connolly wrote:
>
> Hi Heinrich,
>
> On 3/28/25 15:18, Heinrich Schuchardt wrote:
> > On 28.03.25 14:00, Caleb Connolly wrote:
> >>
> >>
> >> On 3/28/25 13:01, Simon Glass wrote:
> >>> Hi Caleb,
> >>>
> >>> On Sun, 23 Mar 2025 at 12:39, Caleb Connolly
On 31.03.25 18:30, Tom Rini wrote:
On Sun, Mar 30, 2025 at 04:38:12PM +0200, Caleb Connolly wrote:
Hi Heinrich,
On 3/28/25 15:18, Heinrich Schuchardt wrote:
On 28.03.25 14:00, Caleb Connolly wrote:
On 3/28/25 13:01, Simon Glass wrote:
Hi Caleb,
On Sun, 23 Mar 2025 at 12:39, Caleb Connolly
Hi Heinrich,
On 3/28/25 15:18, Heinrich Schuchardt wrote:
On 28.03.25 14:00, Caleb Connolly wrote:
On 3/28/25 13:01, Simon Glass wrote:
Hi Caleb,
On Sun, 23 Mar 2025 at 12:39, Caleb Connolly
wrote:
Hi all,
Reviving this as it is still very much an issue, and especially
relevant
for Q
On 28.03.25 14:00, Caleb Connolly wrote:
On 3/28/25 13:01, Simon Glass wrote:
Hi Caleb,
On Sun, 23 Mar 2025 at 12:39, Caleb Connolly
wrote:
Hi all,
Reviving this as it is still very much an issue, and especially relevant
for Qualcomm platforms.
On 11/3/23 20:44, Simon Glass wrote:
Hi H
Hi Caleb,
On Sun, 23 Mar 2025 at 12:39, Caleb Connolly wrote:
>
> Hi all,
>
> Reviving this as it is still very much an issue, and especially relevant
> for Qualcomm platforms.
>
> On 11/3/23 20:44, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Wed, 25 Oct 2023 at 15:22, Heinrich Schuchardt
> >
On 3/28/25 13:01, Simon Glass wrote:
Hi Caleb,
On Sun, 23 Mar 2025 at 12:39, Caleb Connolly wrote:
Hi all,
Reviving this as it is still very much an issue, and especially relevant
for Qualcomm platforms.
On 11/3/23 20:44, Simon Glass wrote:
Hi Heinrich,
On Wed, 25 Oct 2023 at 15:22, He
Hi Heinrich,
On Wed, 25 Oct 2023 at 15:22, Heinrich Schuchardt
wrote:
>
> On 10/25/23 23:13, Tom Rini wrote:
> > On Wed, Oct 25, 2023 at 10:28:05PM +0200, Mark Kettenis wrote:
> >>> Date: Wed, 25 Oct 2023 21:57:44 +0200
> >>> From: Heinrich Schuchardt
> >>>
> >>> On 10/25/23 20:23, Simon Glass w
On 10/25/23 23:13, Tom Rini wrote:
On Wed, Oct 25, 2023 at 10:28:05PM +0200, Mark Kettenis wrote:
Date: Wed, 25 Oct 2023 21:57:44 +0200
From: Heinrich Schuchardt
On 10/25/23 20:23, Simon Glass wrote:
Hi Heinrich,
On Tue, 24 Oct 2023 at 18:02, Simon Glass wrote:
Hi Heinrich,
On Mon, 23 Oc
On Wed, Oct 25, 2023 at 10:28:05PM +0200, Mark Kettenis wrote:
> > Date: Wed, 25 Oct 2023 21:57:44 +0200
> > From: Heinrich Schuchardt
> >
> > On 10/25/23 20:23, Simon Glass wrote:
> > > Hi Heinrich,
> > >
> > > On Tue, 24 Oct 2023 at 18:02, Simon Glass wrote:
> > >>
> > >> Hi Heinrich,
> > >>
Hi Heinrich,
On Wed, 25 Oct 2023 at 20:51, Heinrich Schuchardt
wrote:
>
> On 10/25/23 22:28, Mark Kettenis wrote:
> >> Date: Wed, 25 Oct 2023 21:57:44 +0200
> >> From: Heinrich Schuchardt
> >>
> >> On 10/25/23 20:23, Simon Glass wrote:
> >>> Hi Heinrich,
> >>>
> >>> On Tue, 24 Oct 2023 at 18:02,
On 10/25/23 22:28, Mark Kettenis wrote:
Date: Wed, 25 Oct 2023 21:57:44 +0200
From: Heinrich Schuchardt
On 10/25/23 20:23, Simon Glass wrote:
Hi Heinrich,
On Tue, 24 Oct 2023 at 18:02, Simon Glass wrote:
Hi Heinrich,
On Mon, 23 Oct 2023 at 23:20, Heinrich Schuchardt
wrote:
Forward and
> Date: Wed, 25 Oct 2023 21:57:44 +0200
> From: Heinrich Schuchardt
>
> On 10/25/23 20:23, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Tue, 24 Oct 2023 at 18:02, Simon Glass wrote:
> >>
> >> Hi Heinrich,
> >>
> >> On Mon, 23 Oct 2023 at 23:20, Heinrich Schuchardt
> >> wrote:
> >>>
> >>> For
On Wed, Oct 25, 2023 at 09:57:44PM +0200, Heinrich Schuchardt wrote:
> On 10/25/23 20:23, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Tue, 24 Oct 2023 at 18:02, Simon Glass wrote:
> > >
> > > Hi Heinrich,
> > >
> > > On Mon, 23 Oct 2023 at 23:20, Heinrich Schuchardt
> > > wrote:
> > > >
>
On 10/25/23 20:23, Simon Glass wrote:
Hi Heinrich,
On Tue, 24 Oct 2023 at 18:02, Simon Glass wrote:
Hi Heinrich,
On Mon, 23 Oct 2023 at 23:20, Heinrich Schuchardt
wrote:
Forward and backward compatibility of Linux kernel device-trees is
sometimes missing. One solution approach is to load
Hi Heinrich,
On Tue, 24 Oct 2023 at 18:02, Simon Glass wrote:
>
> Hi Heinrich,
>
> On Mon, 23 Oct 2023 at 23:20, Heinrich Schuchardt
> wrote:
> >
> > Forward and backward compatibility of Linux kernel device-trees is
> > sometimes missing. One solution approach is to load a kernel specific
> > d
On Tue, 24 Oct 2023 at 09:20, Heinrich Schuchardt
wrote:
>
> Forward and backward compatibility of Linux kernel device-trees is
> sometimes missing. One solution approach is to load a kernel specific
> device-tree. This can either be done via a U-Boot scripts (like the one
> generated by Debian pa
On Tue, 24 Oct 2023 at 09:20, Heinrich Schuchardt
wrote:
>
> Forward and backward compatibility of Linux kernel device-trees is
> sometimes missing. One solution approach is to load a kernel specific
> device-tree. This can either be done via a U-Boot scripts (like the one
> generated by Debian pa
On Tue, Oct 24, 2023 at 08:20:32AM +0200, Heinrich Schuchardt wrote:
> Forward and backward compatibility of Linux kernel device-trees is
> sometimes missing. One solution approach is to load a kernel specific
> device-tree. This can either be done via a U-Boot scripts (like the one
> generated by
Hi Heinrich,
On Mon, 23 Oct 2023 at 23:20, Heinrich Schuchardt
wrote:
>
> Forward and backward compatibility of Linux kernel device-trees is
> sometimes missing. One solution approach is to load a kernel specific
> device-tree. This can either be done via a U-Boot scripts (like the one
> generate
Forward and backward compatibility of Linux kernel device-trees is
sometimes missing. One solution approach is to load a kernel specific
device-tree. This can either be done via a U-Boot scripts (like the one
generated by Debian package flash-kernel or by a boot loader like GRUB.
The boot loader ap
22 matches
Mail list logo