From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Parth Kamani <parthvipulkamani@gmail.com>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: Offering to take a TODO item in i915
Date: Tue, 4 Aug 2026 21:51:28 -0400 [thread overview]
Message-ID: <anKXIBhDWkYZs6dZ@intel.com> (raw)
In-Reply-To: <CACa-pC1wVczshOD0xE0oLMDa7q25Q2ibJzCOKyDs4vW6Ga2cCA@mail.gmail.com>
Hi Parth,
Sorry for the delay, response inline below:
On Mon, Aug 03, 2026 at 02:16:48AM +0530, Parth Kamani wrote:
> Hi Rodrigo,
>
> 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.
Oh, I believe this TODO list is so outdated.
I'd say that the core part of i915 is pretty much under maintenance mode.
We are focusing on adding new features on xe driver that supports the new
platforms.
>
> 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?
Honestly, one of the big reasons that we started the new driver was the
difficulty of this task :)
>
> 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.
That is mandatory! :)
Please always do this no matter what patch you are sending.
Perhaps a good and very easy initial patch is to remove this TODO file hehe :)
At least this might trigger a public discussion in our mailing list if we
have anything valid there or if we should kill it entirely.
>
> 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.
That is very exciting! I'm so glad to see students volunteering to take the
next steps and contributing to open source drivers. It is so refreshing to see!
Keep up with this great spirit!
What machine do you have? what is your integrated intel gpu? Something local
is always better.
If it is a not very old intel hardware perhaps it already has support
from our new driver and you could see if there's any issue that you could take:
https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/?sort=created_date&state=opened&first_page_size=20
or perhaps even i915 driver:
https://gitlab.freedesktop.org/drm/i915/kernel/-/work_items?sort=created_date&state=opened&first_page_size=20
>
> Thank you for your time, and I look forward to hearing from you.
I'm sorry for the delay and welcome to the community!
>
> Best regards,
>
> Parth Kamani
> Final-year B.Tech Computer Engineering
> K J Somaiya College of Engineering, Mumbai
> Email: [1]parthvipulkamani@gmail.com
> Phone: +91 9820081318
>
> References
>
> Visible links
> 1. mailto:parthvipulkamani@gmail.com
next parent reply other threads:[~2026-08-05 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACa-pC1wVczshOD0xE0oLMDa7q25Q2ibJzCOKyDs4vW6Ga2cCA@mail.gmail.com>
2026-08-05 1:51 ` Rodrigo Vivi [this message]
[not found] <CACa-pC3Z6KN247yJ9tnb9BZoqSHmXWOzo4LyBodGbQj7uCN=CQ@mail.gmail.com>
2026-08-03 11:24 ` Offering to take a TODO item in i915 Jani Nikula
2026-08-03 15:10 ` Parth Kamani
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=anKXIBhDWkYZs6dZ@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=parthvipulkamani@gmail.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