From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: David Airlie <airlied@linux.ie>,
YueHaibing <yuehaibing@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Maxime Ripard <maxime@cerno.tech>
Subject: Re: [PATCH -next] drm/solomon: Make DRM_SSD130X depends on MMU
Date: Mon, 11 Apr 2022 15:49:38 +0200 [thread overview]
Message-ID: <CAMuHMdVYtV9KHYqjcXS05XM+QqbCgPKB_uZCCAN0eAqHUmoeTg@mail.gmail.com> (raw)
In-Reply-To: <08e81f07-99d2-62a3-8eea-b2c0432b4d18@redhat.com>
Hi Javier,
On Tue, Mar 15, 2022 at 12:28 PM Javier Martinez Canillas
<javierm@redhat.com> wrote:
> On 3/12/22 07:34, YueHaibing wrote:
> > WARNING: unmet direct dependencies detected for DRM_GEM_SHMEM_HELPER
> > Depends on [n]: HAS_IOMEM [=y] && DRM [=m] && MMU [=n]
> > Selected by [m]:
> > - DRM_SSD130X [=m] && HAS_IOMEM [=y] && DRM [=m]
> >
> > DRM_GEM_SHMEM_HELPER depends on MMU, DRM_SSD130X should also depends on MMU.
> >
> > Fixes: a61732e80867 ("drm: Add driver for Solomon SSD130x OLED displays")
> > Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> > ---
>
> Indeed. All the DRM drivers that select DRM_GEM_SHMEM_HELPER depend on MMU.
That's very unfortunate. Is there no way around this?
Else fbdev can never be deprecated in favor of DRM.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2022-04-11 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 6:34 [PATCH -next] drm/solomon: Make DRM_SSD130X depends on MMU YueHaibing
2022-03-15 9:18 ` Javier Martinez Canillas
2022-03-16 15:18 ` Javier Martinez Canillas
2022-04-11 13:49 ` Geert Uytterhoeven [this message]
2022-04-13 7:57 ` Daniel Vetter
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=CAMuHMdVYtV9KHYqjcXS05XM+QqbCgPKB_uZCCAN0eAqHUmoeTg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).