From: Trevor Woerner <twoerner@gmail.com>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] [meta-rockchip][PATCH] KERNEL_DEVICETREE: 32-bit re-org
Date: Tue, 3 Oct 2023 09:38:05 -0400 [thread overview]
Message-ID: <20231003133805.GA2234@localhost> (raw)
In-Reply-To: <0d15a99f-549f-af9d-5f6b-e7712bbf62ff@theobroma-systems.com>
On Tue 2023-10-03 @ 12:32:08 PM, Quentin Schulz wrote:
> Hi Trevor,
>
> On 10/3/23 06:19, Trevor Woerner via lists.yoctoproject.org wrote:
> > The upstream kernel reorganized the 32-bit arch/arm device-tree directory structure
> > to separate out the device-trees by manufacturer (similar to the organization
> > of the arch/arm64 device-trees). Update the references to 32-bit arm
> > device-trees to match.
> >
>
> Does this work with linux-yocto and linux-yocto-dev from master or do we
> need to add some logic to support both (do you want to?).
This doesn't work at all. I figured this was an easy one, made the tweak,
submitted it, then added it to my jenkins builder to verify overnight. Woke up
to find the do_image_wic() tasks failed. It's the same layout as the 64-bit
machines but I'll have to dig in to figure out why it didn't work.
As for the linux-yocto vs linux-yocto-dev question I'll take a look. This
happened with linux-yocto, so I would assume it is already the case with
linux-yocto-dev. But if oe-core supports multiple versions of linux-yocto,
that might be the tricky bit and yes, I would look into supporting both for
the time-being until the transition period ends.
Although... any BSP layer supporting 32-bit machines will have similar issues,
so perhaps there's a better way to solve this in oe-core?
Best regards,
Trevor
next prev parent reply other threads:[~2023-10-03 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 4:19 [meta-rockchip][PATCH] KERNEL_DEVICETREE: 32-bit re-org Trevor Woerner
2023-10-03 10:32 ` [yocto] " Quentin Schulz
2023-10-03 13:38 ` Trevor Woerner [this message]
2023-10-04 13:45 ` Quentin Schulz
2023-10-04 13:46 ` Quentin Schulz
2023-10-04 14:39 ` Bruce Ashfield
2023-10-04 19:21 ` Trevor Woerner
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=20231003133805.GA2234@localhost \
--to=twoerner@gmail.com \
--cc=quentin.schulz@theobroma-systems.com \
--cc=yocto@lists.yoctoproject.org \
/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