All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: "Bajjuri, Praneeth" <praneeth@ti.com>
Cc: Denys Dmytriyenko <denys@konsulko.com>,
	Lokesh Vutla <lokeshvutla@ti.com>,
	Nikhil Devshatwar <nikhil.nd@ti.com>,
	meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] [dunfell/master PATCH 0/6] am65x/j7*: Remove non-existent 5.10.y dtb*
Date: Thu, 15 Apr 2021 16:22:20 -0400	[thread overview]
Message-ID: <20210415202220.GX15937@denix.org> (raw)
In-Reply-To: <3d8c8160-aadc-5442-a38a-b5ff8b60d57c@ti.com>

On Thu, Apr 15, 2021 at 02:00:31PM -0500, Bajjuri, Praneeth wrote:
> 
> 
> On 4/15/2021 1:24 PM, Denys Dmytriyenko wrote:
> >On Thu, Apr 15, 2021 at 12:07:05PM -0500, praneeth via lists.yoctoproject.org wrote:
> >>Denys,
> >>
> >>On 4/15/2021 12:10 AM, praneeth@ti.com wrote:
> >>>From: Praneeth Bajjuri <praneeth@ti.com>
> >>>
> >>>The current ti-linux-5.10.y integration branch doesnt have support for
> >>>non base board dtb/o form the primary latest processor board on am65 and
> >>>j7* evms yet.
> >>>
> >>>Removing these dtb/o for enabling the builds to continue.
> >>>Plan to add these blob and overlays back once the equivalent support is
> >>>added in the integrated ti-linux-5.10.y kernel.
> >>>
> >>
> >>Need your recommendation if this is the right approach to enable the
> >>builds at this early stage of LTS migration (and re-enable the
> >>overlays once the support is added in kernel).
> >
> >That's kind of normal to start a new LTS with bare minimum of dtb/o support.
> >
> >But I have 2 concerns:
> >
> >1. Maybe better to just push commit with removal, instead of reverting old
> >commits - it may get quite confusing soon with reverts of reverts...
> 
> makes sense. will squash in v2.
> 
> >
> >2. Do you think it's still premature to make 5.10 as a default in meta-ti
> >dunfell branch? Since dunfell is kind of established stable (not a new LTS),
> >anyone who updates meta-ti will go from fully working 5.4 to a very minimal
> >and bare 5.10 - may be a bad user experience...
> 
> Was thinking in similar line.
> So, till the 5.10 baseline matures i will continue to use
> dunfell-next to stage the patches and keep dunfell branch untouched
> w.r.t merging 5.10 specific changes.
> 
> Let me know if this a good approach, The only problem in that case
> is the graphics update for 5.10 that i recently pulled to dunfell
> branch. Need to revert it to keep 5.4 dunfell experience retained.

Try those updates first with 5.4 before reverting them, mayve they'll work.


> Any other ideas?
> 
> >
> >
> >>>Praneeth Bajjuri (6):
> >>>   Revert "conf: j7-evm: Add jailhouse dtbo"
> >>>   Revert "j7-evm: add new k3-j721e-proc-board-tps65917.dtb"
> >>>   Revert "j7-evm: add new infotainment DTBO file"
> >>>   Revert "j7-evm: add k3-j721e-pcie-backplane.dtbo"
> >>>   Revert "conf: machine: j7200-evm: Add Jailhouse overlay"
> >>>   conf/machine: am65xx: Remove non-existent dtb* from 5.10
> >>>
> >>>  conf/machine/include/am65xx.inc | 11 -----------
> >>>  conf/machine/j7-evm.conf        |  4 ----
> >>>  conf/machine/j7200-evm.conf     |  1 -
> >>>  3 files changed, 16 deletions(-)
> >>>
> >
> 

-- 
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

  reply	other threads:[~2021-04-15 20:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15  5:10 [dunfell/master PATCH 0/6] am65x/j7*: Remove non-existent 5.10.y dtb* praneeth
2021-04-15  5:11 ` [dunfell/master PATCH 1/6] Revert "conf: j7-evm: Add jailhouse dtbo" praneeth
2021-04-15  5:11 ` [dunfell/master PATCH 2/6] Revert "j7-evm: add new k3-j721e-proc-board-tps65917.dtb" praneeth
2021-04-15  5:11 ` [dunfell/master PATCH 3/6] Revert "j7-evm: add new infotainment DTBO file" praneeth
2021-04-15  5:11 ` [dunfell/master PATCH 4/6] Revert "j7-evm: add k3-j721e-pcie-backplane.dtbo" praneeth
2021-04-15  5:11 ` [dunfell/master PATCH 5/6] Revert "conf: machine: j7200-evm: Add Jailhouse overlay" praneeth
2021-04-15  5:11 ` [dunfell/master PATCH 6/6] conf/machine: am65xx: Remove non-existent dtb* from 5.10 praneeth
2021-04-15 17:07 ` [dunfell/master PATCH 0/6] am65x/j7*: Remove non-existent 5.10.y dtb* praneeth
2021-04-15 18:24   ` [meta-ti] " Denys Dmytriyenko
2021-04-15 19:00     ` praneeth
2021-04-15 20:22       ` Denys Dmytriyenko [this message]
     [not found]       ` <167621ADFB287AF6.32252@lists.yoctoproject.org>
2021-04-16 17:35         ` Denys Dmytriyenko
2021-04-19  4:51           ` praneeth
2021-04-22 20:48             ` Denys Dmytriyenko
2021-04-22 22:28               ` praneeth
2021-04-23  1:59                 ` Denys Dmytriyenko
2021-04-15 17:11 ` praneeth

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=20210415202220.GX15937@denix.org \
    --to=denis@denix.org \
    --cc=denys@konsulko.com \
    --cc=lokeshvutla@ti.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=nikhil.nd@ti.com \
    --cc=praneeth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.