On 9/13/2022 3:25 PM, Heiko Thiery wrote:
Hi Peng,
Am Di., 13. Sept. 2022 um 09:00 Uhr schrieb Peng Fan :
On 9/12/2022 3:48 PM, Heiko Thiery wrote:
Hi Peng,
Am Mo., 12. Sept. 2022 um 09:26 Uhr schrieb Peng Fan :
On 9/9/2022 5:12 PM, Heiko Thiery wrote:
HI,
I think on the imx8mq
Hi Peng,
Am Di., 13. Sept. 2022 um 09:00 Uhr schrieb Peng Fan :
>
>
>
> On 9/12/2022 3:48 PM, Heiko Thiery wrote:
> > Hi Peng,
> >
> > Am Mo., 12. Sept. 2022 um 09:26 Uhr schrieb Peng Fan :
> >>
> >>
> >>
> >> On 9/9/2022 5:12 PM, Heiko Thiery wrote:
> >>> HI,
> >>>
> >>> I think on the imx8mq
On 9/12/2022 3:48 PM, Heiko Thiery wrote:
Hi Peng,
Am Mo., 12. Sept. 2022 um 09:26 Uhr schrieb Peng Fan :
On 9/9/2022 5:12 PM, Heiko Thiery wrote:
HI,
I think on the imx8mq platform we have a problem with the introduction
of the clock driver. I tried to debug the problem that the
On 9/13/2022 2:43 PM, Peng Fan (OSS) wrote:
On 9/12/2022 3:48 PM, Heiko Thiery wrote:
Hi Peng,
Am Mo., 12. Sept. 2022 um 09:26 Uhr schrieb Peng Fan :
On 9/9/2022 5:12 PM, Heiko Thiery wrote:
HI,
I think on the imx8mq platform we have a problem with the introduction
of the clock
On 9/12/2022 3:48 PM, Heiko Thiery wrote:
Hi Peng,
Am Mo., 12. Sept. 2022 um 09:26 Uhr schrieb Peng Fan :
On 9/9/2022 5:12 PM, Heiko Thiery wrote:
HI,
I think on the imx8mq platform we have a problem with the introduction
of the clock driver. I tried to debug the problem that the
Hi Peng,
Am Mo., 12. Sept. 2022 um 09:26 Uhr schrieb Peng Fan :
>
>
>
> On 9/9/2022 5:12 PM, Heiko Thiery wrote:
> > HI,
> >
> > I think on the imx8mq platform we have a problem with the introduction
> > of the clock driver. I tried to debug the problem that the pitx-imx8m
> > board was not able
On 9/9/2022 5:12 PM, Heiko Thiery wrote:
HI,
I think on the imx8mq platform we have a problem with the introduction
of the clock driver. I tried to debug the problem that the pitx-imx8m
board was not able to start for some time. I was wondering why the
pitx-im8m doesn't work anymore although
Hi Angus,
Am Fr., 9. Sept. 2022 um 18:38 Uhr schrieb Angus Ainslie :
>
> Hi Heiko,
>
> On 2022-09-09 07:45, Heiko Thiery wrote:
> > Hi Angus,
> >
> > Am Fr., 9. Sept. 2022 um 16:43 Uhr schrieb Angus Ainslie
> > :
> >>
> >> Hi Heiko,
> >>
> >> The librem5 (imx8mq) is able to boot using these [1]
Hi Heiko,
On 2022-09-09 07:45, Heiko Thiery wrote:
Hi Angus,
Am Fr., 9. Sept. 2022 um 16:43 Uhr schrieb Angus Ainslie
:
Hi Heiko,
The librem5 (imx8mq) is able to boot using these [1] patches on top of
u-boot-imx-20220729.
I believe the change that fixed the allocation issue for me was
Hi Angus,
Am Fr., 9. Sept. 2022 um 16:43 Uhr schrieb Angus Ainslie :
>
> Hi Heiko,
>
> The librem5 (imx8mq) is able to boot using these [1] patches on top of
> u-boot-imx-20220729.
>
> I believe the change that fixed the allocation issue for me was
>
> CONFIG_SPL_MAX_SIZE=0x25000
The imx8mq_evk
Hi Heiko,
The librem5 (imx8mq) is able to boot using these [1] patches on top of
u-boot-imx-20220729.
I believe the change that fixed the allocation issue for me was
CONFIG_SPL_MAX_SIZE=0x25000
Cheers,
Angus
[1]
https://lore.kernel.org/u-boot/20220825134602.382775-1-an...@akkea.ca/
On
HI,
I think on the imx8mq platform we have a problem with the introduction
of the clock driver. I tried to debug the problem that the pitx-imx8m
board was not able to start for some time. I was wondering why the
pitx-im8m doesn't work anymore although the imx8mq_evk is running.
So I switched to
12 matches
Mail list logo