From: Chirag Shilwant <c-shilwant@ti.com>
To: "Bajjuri, Praneeth" <praneeth@ti.com>,
Devarsh Thakkar <devarsht@ti.com>, Ryan Eatmon <reatmon@ti.com>,
<meta-ti@lists.yoctoproject.org>, <denys@konsulko.com>
Cc: <vigneshr@ti.com>, <a-bhatia1@ti.com>, <j-luthra@ti.com>,
Gyan Gupta <g-gupta@ti.com>, Khasim <khasim@ti.com>
Subject: Re: [EXTERNAL] Re: [meta-ti] [kirkstone] [PATCH v2] meta-ti-bsp: Add bootsplash image file for AM62P
Date: Thu, 8 Feb 2024 15:39:24 +0530 [thread overview]
Message-ID: <a2778449-6c21-4bd2-b667-9dc22ad15b21@ti.com> (raw)
In-Reply-To: <17B183A9980B38E6.2925@lists.yoctoproject.org>
On 07/02/24 12:51, Chirag Shilwant via lists.yoctoproject.org wrote:
> On 06/02/24 03: 20, Bajjuri, Praneeth wrote: > > > On 2/5/2024 10: 06
> AM, Chirag Shilwant wrote: >> >> On 05/02/24 21: 13, Devarsh Thakkar
> wrote: >>> >>> >>> On 05/02/24 20: 44, Ryan Eatmon wrote:
> ZjQcmQRYFpfptBannerStart
> This message was sent from outside of Texas Instruments.
> Do not click links or open attachments unless you recognize the source
> of this email and know the content is safe.
> ZjQcmQRYFpfptBannerEnd
> On 06/02/24 03:20, Bajjuri, Praneeth wrote:
> >
> >
> > On 2/5/2024 10:06 AM, Chirag Shilwant wrote:
> >>
> >> On 05/02/24 21:13, Devarsh Thakkar wrote:
> >>>
> >>>
> >>> On 05/02/24 20:44, Ryan Eatmon wrote:
> >>>>
> >>>>
> >>>> On 2/3/2024 1:05 AM, Devarsh Thakkar wrote:
> >>>>> Add TI logo image as bootsplash image file for AM62P and install
> >>>>> it in
> >>>>> boot directory from where u-boot can read from and display during
> >>>>> boot-up time.
> >>>>
> >>>>
> >>>> Thank you for the rebase. Was the config fragment that Chirag
> >>>> asked about ever sent to uboot to avoid an issue with the recipe in
> >>>> the processor-sdk?
> >>>>
> >>>
> >>> Yes, I had submitted a patch to ti-u-boot.
> >
> > pulled the patch in -next branch.
> > https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2023.04-next&id=e7d2df2ecfb3591938087335d81ebf0498dc8ece
> >
> >
> >
>
> Thanks Praneeth.
>
>
> Hi Ryan,
>
> As the ti-u-boot config dependencies are pulled in next branches, we can
> go ahead and integrate this patch.
> I will send out a patch soon to update the am62pxx-evm.conf to include
> the config fragment which is needed
> for the tisdk-display-cluster wic image.
Well, we can handle this in processor sdk builds. So, no follow up patch
is needed on meta-ti to handle tisdk-display-cluster image.
We can go ahead & integrate this patch.
Thanks Chirag.
>
>
> > I have sent you the link
> >>> offline.
> >>>
> >>> Regards
> >>> Devarsh
> >>
> >>
> >> Thanks Devarsh for sending a v2. What's the status on the config
> >> fragment patch in ti-u-boot as well as upstream?
> >>
> >
> > Devarsh, can you comment on this one .
> >
> >
> >>
> >>>
> >>>>
> >>>>
> >>>>> Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
>
>
> Acked-by: Chirag Shilwant <c-shilwant@ti.com>
>
>
> >>>>>
> >>>>> ---
> >>>>> V2: Rebase to updated uboot recipes
> >>>>> ---
> >>>>> meta-ti-bsp/conf/machine/include/am62pxx.inc | 3 +++
> >>>>> meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 10 ++++++++++
> >>>>> 2 files changed, 13 insertions(+)
> >>>>>
> >>>>> diff --git a/meta-ti-bsp/conf/machine/include/am62pxx.inc
> >>>>> b/meta-ti-bsp/conf/machine/include/am62pxx.inc
> >>>>> index bac68253..38e35851 100644
> >>>>> --- a/meta-ti-bsp/conf/machine/include/am62pxx.inc
> >>>>> +++ b/meta-ti-bsp/conf/machine/include/am62pxx.inc
> >>>>> @@ -17,3 +17,6 @@ OPTEEMACHINE = "k3-am62x"
> >>>>> MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "cnm-wave-fw"
> >>>>> SERIAL_CONSOLES = "115200;ttyS2"
> >>>>> +
> >>>>> +# Bitmap image tarball for early splashscreen
> >>>>> +IMAGE_BOOT_FILES += "ti_logo_414x97_32bpp.bmp.gz"
> >>>>> diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> >>>>> b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> >>>>> index 493c1c31..42ddf40f 100644
> >>>>> --- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> >>>>> +++ b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> >>>>> @@ -341,4 +341,14 @@ do_deploy:append:am62xx() {
> >>>>> install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz
> >>>>> ${DEPLOYDIR}
> >>>>> }
> >>>>> +do_install:append:am62pxx() {
> >>>>> + install -d ${D}/boot
> >>>>> + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz
> >>>>> ${D}/boot
> >>>>> +}
> >>>>> +
> >>>>> +do_deploy:append:am62pxx() {
> >>>>> + install -d ${DEPLOYDIR}
> >>>>> + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz
> >>>>> ${DEPLOYDIR}
> >>>>> +}
> >>>>> +
> >>>>> TOOLCHAIN = "gcc"
> >>>>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#17451): https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-ti/message/17451__;!!G3vK!V6suywddREI9UgEzo-aB2xsTy8h2XljYIjm8Stf_B_vxWFGidif6toctt3P3Rde3zleaK0iPXf8TEEj4LPC6S_21q8-DC5ocjjqV$
> Mute This Topic: https://urldefense.com/v3/__https://lists.yoctoproject.org/mt/104135441/7030289__;!!G3vK!V6suywddREI9UgEzo-aB2xsTy8h2XljYIjm8Stf_B_vxWFGidif6toctt3P3Rde3zleaK0iPXf8TEEj4LPC6S_21q8-DCwmdOIc_$
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-ti/unsub__;!!G3vK!V6suywddREI9UgEzo-aB2xsTy8h2XljYIjm8Stf_B_vxWFGidif6toctt3P3Rde3zleaK0iPXf8TEEj4LPC6S_21q8-DC_OPa7UF$ [c-shilwant@ti.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2024-02-08 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 7:05 [meta-ti] [kirkstone] [PATCH v2] meta-ti-bsp: Add bootsplash image file for AM62P Devarsh Thakkar
2024-02-05 15:14 ` Ryan Eatmon
2024-02-05 15:43 ` Devarsh Thakkar
2024-02-05 16:06 ` Chirag Shilwant
2024-02-05 21:50 ` Bajjuri, Praneeth
2024-02-07 7:21 ` Chirag Shilwant
[not found] ` <17B183A9980B38E6.2925@lists.yoctoproject.org>
2024-02-08 10:09 ` Chirag Shilwant [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=a2778449-6c21-4bd2-b667-9dc22ad15b21@ti.com \
--to=c-shilwant@ti.com \
--cc=a-bhatia1@ti.com \
--cc=denys@konsulko.com \
--cc=devarsht@ti.com \
--cc=g-gupta@ti.com \
--cc=j-luthra@ti.com \
--cc=khasim@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
--cc=vigneshr@ti.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).