From: Jani Nikula <jani.nikula@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>,
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: Tue, 04 Jun 2024 11:05:47 +0300 [thread overview]
Message-ID: <87jzj5ceuc.fsf@intel.com> (raw)
In-Reply-To: <20240603073518.u37dkix3rxahhdbq@zkempczy-mobl2>
On Mon, 03 Jun 2024, Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> wrote:
> Currently igt_device_scan.c is limited to devices which have drm driver
> loaded (that was danvet requirement of udev scanning of drm devices, not
> pci). But if I'm not wrong it would be relatively simple to add
> scan_pci_devices() in which we would iterate over udev pci devices and
> filter out 300 class then add some switch to display it lsgpu. We would
> at least keep this simply in igt, without any additional scripting/tools
> needed.
Yes.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-06-04 8:05 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
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 [this message]
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=87jzj5ceuc.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 \
--cc=zbigniew.kempczynski@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