From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Dave Airlie <airlied@gmail.com>
Cc: Matthew Auld <matthew.auld@intel.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm fixes + one missed next for 5.16-rc1
Date: Mon, 15 Nov 2021 08:18:53 +0100 [thread overview]
Message-ID: <1ff1389b-bf4c-cd09-8bfd-d4303d100eee@linux.intel.com> (raw)
In-Reply-To: <CAHk-=wjpPWyH5ff0LE8Mmt6OEiYbD3LwpvpD==FFZfTMTzL2FQ@mail.gmail.com>
On 11/14/21 22:19, Linus Torvalds wrote:
> On Sun, Nov 14, 2021 at 1:00 PM Dave Airlie <airlied@gmail.com> wrote:
>> i915 will no longer be x86-64 only in theory, since Intel now produces
>> PCIe graphics cards using the same hw designs.
> Well, at least in my tree, it still has the "depends on X86", along
> with several other x86-only things (like "select INTEL_GTT", which is
> also x86-only)
>
> So by the time that non-x86 theory becomes reality, hopefully the i915
> people will also have figured out how to do the cache flushing
> properly.
>
> And hopefully that "do it properly" ends up being simply that the
> particular configuration that ends up being portable simply doesn't
> need to do it at all and can statically just not build it,
> sidestepping the issue entirely.
>
> Fingers crossed.
For non-x86 / discrete graphics, plan is only coherent mappings,
although the "Just not build it" part hasn't been properly figured out
yet I guess. But point taken.
Thanks,
/Thomas
next prev parent reply other threads:[~2021-11-15 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 3:25 [git pull] drm fixes + one missed next for 5.16-rc1 Dave Airlie
2021-11-12 20:16 ` Linus Torvalds
2021-11-14 21:00 ` Dave Airlie
2021-11-14 21:19 ` Linus Torvalds
2021-11-15 7:18 ` Thomas Hellström [this message]
2021-11-15 14:29 ` Daniel Vetter
2021-11-12 20:42 ` pr-tracker-bot
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=1ff1389b-bf4c-cd09-8bfd-d4303d100eee@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=airlied@gmail.com \
--cc=ashutosh.dixit@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.auld@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=torvalds@linux-foundation.org \
/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