[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPM=9txnZaeUgYEauJF5eSidEsGS9DmT6M4O-PcTPtCFXL8adA@mail.gmail.com>
Date: Mon, 22 Oct 2018 10:26:07 +1000
From: Dave Airlie <airlied@...il.com>
To: mtirado418@...il.com
Cc: Dave Airlie <Airlied@...ux.ie>,
dri-devel <dri-devel@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>,
Gerd Hoffmann <kraxel@...hat.com>,
"Deucher, Alexander" <alexander.deucher@....com>,
"Koenig, Christian" <christian.koenig@....com>,
zhoucm1 <David1.zhou@....com>, Hongbo.He@....com,
Sean Paul <seanpaul@...omium.org>,
Gustavo Padovan <Gustavo@...ovan.org>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>
Subject: Re:
On Mon, 22 Oct 2018 at 07:22, Michael Tirado <mtirado418@...il.com> wrote:
>
> Mapping a drm "dumb" buffer fails on 32-bit system (i686) from what
> appears to be a truncated memory address that has been copied
> throughout several files. The bug manifests as an -EINVAL when calling
> mmap with the offset gathered from DRM_IOCTL_MODE_MAP_DUMB <--
> DRM_IOCTL_MODE_ADDFB <-- DRM_IOCTL_MODE_CREATE_DUMB. I can provide
> test code if needed.
>
> The following patch will apply to 4.18 though I've only been able to
> test through qemu bochs driver and nouveau. Intel driver worked
> without any issues. I'm not sure if everyone is going to want to
> share a constant, and the whitespace is screwed up from gmail's awful
> javascript client, so let me know if I should resend this with any
> specific changes. I have also attached the file with preserved
> whitespace.
>
This shouldn't be necessary, did someone misbackport the mmap changes without:
drm: set FMODE_UNSIGNED_OFFSET for drm files
Dave.
Powered by blists - more mailing lists