From: Thomas Zimmermann <tzimmermann@suse.de>
To: lcwang <zaq14760@gmail.com>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
airlied@gmail.com, simona@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/tiny: pixpaper: add explicit dependency on MMU
Date: Thu, 30 Oct 2025 09:10:57 +0100 [thread overview]
Message-ID: <9be201bd-977e-48df-bb57-7ef1f532b26f@suse.de> (raw)
In-Reply-To: <20251030024329.482105-1-lcwang@ieiworld.com>
Hi
Am 30.10.25 um 03:43 schrieb lcwang:
> Hi Thomas,
>
> Thanks for the clarification.
>
> Just to confirm my understanding — are you suggesting that this issue
> should ideally be fixed in the RISC-V Kconfig (specifically the PORTABLE
> logic that ensures MMU is selected), rather than adding a local
> "depends on MMU" here in DRM_PIXPAPER?
>
> If that’s the case and the root cause will be addressed in the RISC-V
> side, I’m happy to drop this patch to avoid redundant dependencies.
After reconsidering, we can merge your patch. Here's probably no easier
solution to the problem.
Best regards
Thomas
>
> Best regards,
> LiangCheng
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2025-10-30 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 2:55 [PATCH] drm/tiny: pixpaper: add explicit dependency on MMU LiangCheng Wang
2025-10-29 9:49 ` Thomas Zimmermann
2025-10-30 2:43 ` lcwang
2025-10-30 8:10 ` Thomas Zimmermann [this message]
2025-10-30 8:11 ` Thomas Zimmermann
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=9be201bd-977e-48df-bb57-7ef1f532b26f@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=zaq14760@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