All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Luca Ceresoli <luca@lucaceresoli.net>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
	<linux-omap@vger.kernel.org>,
	"Bajjuri, Praneeth" <praneeth@ti.com>,
	"Vutla, Lokesh" <lokeshvutla@ti.com>
Subject: Re: Status of ti/ti-linux-5.10.y development
Date: Fri, 14 May 2021 10:38:10 -0500	[thread overview]
Message-ID: <20210514153810.qv2kjdoy2ku2ss5d@unlearned> (raw)
In-Reply-To: <9cb5a7d4-bf01-7079-8556-f6de008872c9@lucaceresoli.net>

Luca,
On 12:20-20210514, Luca Ceresoli wrote:
> Hi Grygorii,
> 
> On 14/05/21 12:14, Grygorii Strashko wrote:
> > Hi
> > 
> > On 14/05/2021 11:30, Luca Ceresoli wrote:
> >> Hi,
> >>
> >> I hope this is the proper place for this question. If it isn't: my
> >> apologies, and I'd be glad to be redirected where appropriate.
> >>
> >> I currently have a prototype board based on AM5728 that is mostly
> >> working, using branch ti/ti-linux-4.19.y of the TI kernel [0].
> >>
> >> Now I need some non-TI-specific kernel features that appeared in
> >> mainline 5.10, so I tried to move to branch ti/ti-linux-5.10.y. But many
> >> components that I am using on the 4.19 branch seem absent on the 5.10
> >> branch, including VIDEO_TI_VIP, DRM_OMAP_WB and DRM_OMAP_CONNECTOR_HDMI.
> >>
> >> BTW they are not present even in mainline Linux.
> >>
> >> Are this drivers still absent and in progress of being added to
> >> ti/ti-linux-5.10.y, or are they present in a different form that I have
> >> been unable to find?
> >>
> >> Assuming they still have to be added, is there an estimate timing for
> >> their availability on the 5.10 branch?
> >>
> >> [0] git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
> >>
> > 
> > 
> > TI 5.10 migration is still work in progress.
> 
> Thanks for the feedback.
> 
> Any estimate of how long this is expected to take?

Nothing we will be able to share in a public forum :(

> 
> Is there any public list of drivers to be added and their status?

In public, No - Note: even though the git repo is public, and
internally we attempt to follow the same upstream rules, at the end,
it is still a vendor kernel :(. But, rest assure that internally, we
know precisely where we are and we are tracking towards completion.

While linux-omap is a public list, it might be better to answer
vendor kernel questions in the context of e2e.ti.com (The TI forums
- there are folks closely monitoring those and actively engaging
to help customers out and will be better positioned to answer your
specific queries). Do feel free to reach out to me on irc freenode.net
#linux-omap etc if you'd need anything specific to help with.

We usually prefer linux-omap mailing list to stick with upstream
discussions, one off vendor kernel discussions do take place from time
to time, however, most of our TI support folks are better equipped to
answer questions on TI forums.


The above "officialdom statement" said, we do actively encourage our
community (which we include ourselves and TI customers as well) to
participate in making upstream kernel complete and point out anything
we may have overlooked (yep, we are human) so that overall what vendor
kernel does or does'nt do should be inconsequential in the longer term
for the community and products derived from community.


-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

  reply	other threads:[~2021-05-14 15:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14  8:30 Status of ti/ti-linux-5.10.y development Luca Ceresoli
2021-05-14 10:14 ` Grygorii Strashko
2021-05-14 10:20   ` Luca Ceresoli
2021-05-14 15:38     ` Nishanth Menon [this message]
2021-05-17  8:39       ` Luca Ceresoli
2021-05-15 13:47 ` Andreas Kemnade
2021-05-17  8:43   ` Luca Ceresoli
2021-05-18  5:12     ` Tony Lindgren
2021-05-18 21:29       ` Luca Ceresoli

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=20210514153810.qv2kjdoy2ku2ss5d@unlearned \
    --to=nm@ti.com \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=luca@lucaceresoli.net \
    --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.