From: Angus Ainslie <angus@akkea.ca>
To: Stefano Babic <sbabic@denx.de>
Cc: u-boot@lists.denx.de, uboot-imx@nxp.com, festevam@gmail.com,
peng.fan@nxp.com, marcel.ziswiler@toradex.com,
t.remmet@phytec.de, tharvey@gateworks.com,
jagan@amarulasolutions.com, iliev@ronetix.at, kernel@puri.sm,
alpernebiyasak@gmail.com,
Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>
Subject: Re: [PATCH v6] board: purism: add the Purism Librem5 phone
Date: Thu, 28 Jul 2022 06:33:40 -0700 [thread overview]
Message-ID: <8c66988912ffa69f96d47ce9bf029b49@akkea.ca> (raw)
In-Reply-To: <f678bf2e-b7c1-59dc-39ce-b14fbba2837e@denx.de>
On 2022-07-26 00:35, Stefano Babic wrote:
> On 30.06.22 21:29, Angus Ainslie wrote:
>> Hi Stefano,
>>
>> On 2022-06-30 12:09, Stefano Babic wrote:
>>> Hi Angus,
>>>
>>> On 30.06.22 19:30, Angus Ainslie wrote:
>>>> Hi All,
>>>>
>>>> Are there any remaining issues with this patch ?
>>>>
>>>
>>> Rather yes, it was supposed that issues with dwc3 was already fixed,
>>> maybe another patch is missing - can you check this ?
>>>
>>> https://source.denx.de/u-boot/custodians/u-boot-imx/-/jobs/457089
>>>
>>
>> It needs the patch mentioned down below in the description.
>
> Next attempt...
>
> There are several CONFIG_ in include/configs/librem5.h that should be
> really set in the config file, causing build error, see:
>
> https://source.denx.de/u-boot/custodians/u-boot-imx/-/jobs/472302
>
> Can you fix them ? Thanks !
>
Unfortunately rebasing on the latest u-boot-imx the board doesn't boot
anymore so I'll need to bisect that first
Regards
Angus
> Best regards,
> Stefano
prev parent reply other threads:[~2022-07-28 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 20:58 [PATCH v6] board: purism: add the Purism Librem5 phone Angus Ainslie
2022-06-30 17:30 ` Angus Ainslie
2022-06-30 19:09 ` Stefano Babic
2022-06-30 19:29 ` Angus Ainslie
2022-07-26 7:35 ` Stefano Babic
2022-07-28 13:33 ` Angus Ainslie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8c66988912ffa69f96d47ce9bf029b49@akkea.ca \
--to=angus@akkea.ca \
--cc=alpernebiyasak@gmail.com \
--cc=festevam@gmail.com \
--cc=iliev@ronetix.at \
--cc=jagan@amarulasolutions.com \
--cc=kernel@puri.sm \
--cc=marcel.ziswiler@toradex.com \
--cc=peng.fan@nxp.com \
--cc=sbabic@denx.de \
--cc=sebastian.krzyszkowiak@puri.sm \
--cc=t.remmet@phytec.de \
--cc=tharvey@gateworks.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox