Re: Offering to take a TODO item in i915

Parth Kamani <[email protected]>
Newsgroups org.freedesktop.lists.intel-gfx
Message-ID <CACa-pC2rUDWn343s9UMdhJC1BVFFFvAxmWS2KgzwnBbPYiia2A@mail.gmail.com>
Hi Jani,

Thank you for the explanation and for pointing me in the right direction.
That makes sense, and I appreciate the advice.

I'll shift my focus to the xe driver and the shared display code instead of
the older GEM/GT TODO items. I'll spend some time getting familiar with the
codebase and look for smaller issues that would make suitable first
contributions.

I also wanted to ask one additional question. I'm currently looking for a
paid internship or a student opportunity where I can contribute to Linux
kernel development while continuing to work upstream.

Would you happen to know of any teams, companies, or programs working on
the xe or DRM subsystem that are open to hiring or mentoring students? If
there's someone else I should reach out to, I'd be grateful for any
recommendations.

Thank you again for your guidance.

Best regards,

Parth Kamani
Final-year B.Tech Computer Engineering
K J Somaiya College of Engineering, Mumbai
Email: [email protected]
Phone: +91 9820081318

On Mon, Aug 3, 2026 at 5:11 PM Jani Nikula <[email protected]>
wrote:

> On Mon, 03 Aug 2026, Parth Kamani <[email protected]> wrote:
> > Hi Jani,
> >
> > I was looking through drivers/gpu/drm/i915/TODO.txt and noticed that
> there
> > are still a number of outstanding items. One that caught my attention
> was *"for
> > discrete memory manager, merge enough dg1 to be able to refactor it to
> ..."*.
> > I also saw items such as *"Come up with a plan what to do with
> > drm/scheduler and how to get there"* and *"Roll out dma_fence critical
> > section annotations"*, so it looks like there are several areas that
> still
> > need work.
> >
> > From the TODO, some of these items appear more involved than others, so
> > before I dive in I wanted to check with you. Is the discrete memory
> manager
> > item still something that would be appropriate to work on, or would you
> > recommend a different task for someone making a first contribution to
> i915?
> >
> > My preference is to keep patches small enough to review comfortably,
> > run checkpatch
> > --strict, test against current mainline, and submit them via git
> send-email.
> >
> > I'm currently in my final year of B.Tech in Computer Engineering at K J
> > Somaiya College of Engineering, Mumbai (graduating mid-2027), and I have
> a
> > meaningful amount of time to contribute before graduation. I'd much
> rather
> > spend that time contributing to a live upstream codebase than working
> only
> > on coursework. If there's a better first task than the TODO item above,
> I'd
> > really appreciate your recommendation and would be happy to work on that
> > instead.
>
> Thanks for your interest!
>
> The TODO was added in commit 6ab61ad5c1d8 ("drm/i915: add gem/gt TODO")
> and has barely been touched since. The primary reason is migrating to
> the xe driver for new platforms. If you're looking to work on a "live
> upstream codebase", seeking tasks in the xe driver, or the display
> driver under i915/display, shared between the xe and i915 drivers, is
> probably more rewarding.
>
>
> HTH,
> Jani.
>
>
> --
> Jani Nikula, Intel
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.