From: Tim Orling <ticotimo@gmail.com>
To: mlynch@hi-techniques.com, yocto@lists.yoctoproject.org
Cc: Steve Sakoman <steve@sakoman.com>
Subject: Re: [yocto] Final dunfell release build on April 15, 2024
Date: Fri, 22 Mar 2024 17:13:16 -0700 [thread overview]
Message-ID: <CANx9H-D6hJ9uCTknO2Y2dGeGOVYiyrZoB083yGapYx4ehtAv-A@mail.gmail.com> (raw)
In-Reply-To: <CANx9H-DnRaOrC_hHY5THrOCzc8taWb9ak3wX0Bs=23UCyCN+Eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]
On Fri, Mar 22, 2024 at 5:12 PM Tim Orling <ticotimo@gmail.com> wrote:
>
>
> On Fri, Mar 22, 2024 at 6:39 AM <mlynch@hi-techniques.com> wrote:
>
>> Does Dunfell EOL mean builds for TI platforms that actually build and
>> boot can be done using a newer branch? E.G. As of yet, I have been unable
>> to build for TI "beagle" platforms that will boot using any branch other
>> than Dunfell. I tried both master and kirkstone, a few weeks ago, and
>> neither produces anything bootable for the "beagle" platforms.
>>
>
> You should really ask on the meta-ti mailing list. Unless you mean the
> beagle-yocto BSP support in poky/meta-poky-bsp.
>
I meant meta-yocto-bsp
>
>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#62824):
>> https://lists.yoctoproject.org/g/yocto/message/62824
>> Mute This Topic: https://lists.yoctoproject.org/mt/105069080/924729
>> Group Owner: yocto+owner@lists.yoctoproject.org
>> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
>> ticotimo@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>>
[-- Attachment #2: Type: text/html, Size: 2797 bytes --]
prev parent reply other threads:[~2024-03-23 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 16:37 Final dunfell release build on April 15, 2024 Steve Sakoman
2024-03-22 13:39 ` [yocto] " mlynch
2024-03-23 0:12 ` Tim Orling
2024-03-23 0:13 ` Tim Orling [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=CANx9H-D6hJ9uCTknO2Y2dGeGOVYiyrZoB083yGapYx4ehtAv-A@mail.gmail.com \
--to=ticotimo@gmail.com \
--cc=mlynch@hi-techniques.com \
--cc=steve@sakoman.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).