From: Boris Brezillon <boris.brezillon@collabora.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org,
Daniel Almeida <daniel.almeida@collabora.com>
Subject: Re: [PATCH i-g-t v2] panthor: Enable compilation on big-endian arch
Date: Mon, 2 Mar 2026 11:45:24 +0100 [thread overview]
Message-ID: <20260302114524.57fa1959@fedora> (raw)
In-Reply-To: <e863d999b0bc37aba10242c707320aabb6cffd4e@intel.com>
On Mon, 23 Feb 2026 12:49:38 +0200
Jani Nikula <jani.nikula@intel.com> wrote:
> On Thu, 19 Feb 2026, Kamil Konieczny <kamil.konieczny@linux.intel.com> wrote:
> > Compilation of Panthor was broken on big-endian due to a guard in
> > pathor lib against such arch. Fix this and create and use
> > function for skipping all panthor tests on such machines.
> >
> > Also while at it, init fd so it could be safely used at last
> > fixture.
>
> What about DRIVER_ANY tests?
>
> Seems like the cleaner option would be to amend drm_open_driver() with
> something like:
>
> if (chipset & DRIVER_PANTHOR)
> skip on big endian
>
> instead of sprinkling the skips everywhere.
FWIW, I'm fine with this approach too.
prev parent reply other threads:[~2026-03-02 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 15:05 [PATCH i-g-t v2] panthor: Enable compilation on big-endian arch Kamil Konieczny
2026-02-19 15:23 ` Boris Brezillon
2026-02-19 17:00 ` Daniel Almeida
2026-02-19 17:35 ` ✗ Fi.CI.BAT: failure for panthor: Enable compilation on big-endian arch (rev2) Patchwork
2026-02-23 10:49 ` [PATCH i-g-t v2] panthor: Enable compilation on big-endian arch Jani Nikula
2026-03-02 10:45 ` Boris Brezillon [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=20260302114524.57fa1959@fedora \
--to=boris.brezillon@collabora.com \
--cc=daniel.almeida@collabora.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=kamil.konieczny@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 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.