From: Jani Nikula <jani.nikula@intel.com>
To: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org, kamil.konieczny@intel.com,
katarzyna.piecielska@intel.com
Subject: Re: [PATCH i-g-t v4] tools/mk_detect_intel_gpu: add a tool to detect Intel GPUs from their PCI IDs
Date: Thu, 23 May 2024 10:26:01 +0300 [thread overview]
Message-ID: <87sey9oupi.fsf@intel.com> (raw)
In-Reply-To: <20240523070346.04def11b@maurocar-mobl2>
On Thu, 23 May 2024, Mauro Carvalho Chehab <mauro.chehab@linux.intel.com> wrote:
> On Wed, 22 May 2024 16:46:27 +0200
> Kamil Konieczny <kamil.konieczny@linux.intel.com> wrote:
>
>> Hi Jani,
>> On 2024-05-22 at 16:26:44 +0300, Jani Nikula wrote:
>> > On Wed, 22 May 2024, Jani Nikula <jani.nikula@intel.com> wrote:
>> > > On Wed, 22 May 2024, Mauro Carvalho Chehab <mauro.chehab@linux.intel.com> wrote:
>> > >> From: Mauro Carvalho Chehab <mchehab@kernel.org>
>> > >>
>> > >> Such tool parses the Kernel drivers for both i915 and Xe and
>> > >> generates a script that helps detecting Intel GPU models.
>> > >
>> > > I acknowledge the usefulness of such a tool, but to be brutally honest,
>> > > this implementation is horrible in so many levels.
>> > >
>> > > IGT uses meson and avoids perl.
>>
>> imho this could also be a python script.
>
> Converting the output to a python script should be trivial and can be done
> later on. The generated script has a a simple hash/dict lookup logic.
It should not be a generated script in the first place. It should not
grep the kernel or igt sources for certain patterns which will
change. It should not have to be this complicated.
If it's C, it should be a regular build (via meson). If it's Python, it
should do all it needs to do when running it.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-05-23 7:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 12:02 [PATCH i-g-t v4] tools/mk_detect_intel_gpu: add a tool to detect Intel GPUs from their PCI IDs Mauro Carvalho Chehab
2024-05-22 12:54 ` Jani Nikula
2024-05-22 13:26 ` Jani Nikula
2024-05-22 14:46 ` Kamil Konieczny
2024-05-23 5:03 ` Mauro Carvalho Chehab
2024-05-23 7:26 ` Jani Nikula [this message]
2024-05-23 7:30 ` Jani Nikula
2024-05-23 8:36 ` Mauro Carvalho Chehab
2024-05-23 9:10 ` Jani Nikula
2024-05-23 17:31 ` Kamil Konieczny
2024-05-24 8:49 ` Jani Nikula
2024-05-25 5:44 ` Mauro Carvalho Chehab
2024-06-03 7:35 ` Zbigniew Kempczyński
2024-06-04 8:05 ` Jani Nikula
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=87sey9oupi.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=katarzyna.piecielska@intel.com \
--cc=mauro.chehab@linux.intel.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