From: Tormod Volden <lists.tormod@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Airlie <airlied@redhat.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH resend] drm/savage: Do not add framebuffer and aperture maps
Date: Sat, 28 May 2011 01:44:16 +0200 [thread overview]
Message-ID: <BANLkTim76K-84NKF4GpStG6XtYe+61gKKw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinmJqq+G0apE=8Abydm0MEjtEzU0A@mail.gmail.com>
On Fri, May 27, 2011 at 10:48 PM, Dave Airlie <airlied@gmail.com> wrote:
> On Sat, May 28, 2011 at 4:19 AM, Tormod Volden <lists.tormod@gmail.com> wrote:
>> From: Tormod Volden <debian.tormod@gmail.com>
>>
>> Since multiple framebuffer maps are not supported any longer (commit
>> 41c2e75e60200a860a74b7c84a6375c105e7437f) these maps would be broken,
>> and they are not used by the drm anyway.
>>
>> Leave it to userspace to create one working map instead.
>
> Sorry Tormod, I'm really failing to get this far down my todo list.
> I'll try and get some
> time next week. I think I preferred the patch to make things work with
> current userspace.
> and undo the regression.
>
> Dave.
Thanks, I am glad to hear that. I would really prefer to not rewrite
userspace, which seems rather painful.
Cheers,
Tormod
next prev parent reply other threads:[~2011-05-27 23:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 21:54 multiple framebuffer drm maps Tormod Volden
2011-05-03 21:20 ` Tormod Volden
2011-05-03 21:54 ` Tormod Volden
2011-05-22 19:27 ` [PATCH] drm/savage: Do not add framebuffer and aperture maps Tormod Volden
2011-05-27 18:19 ` [PATCH resend] " Tormod Volden
2011-05-27 20:48 ` Dave Airlie
2011-05-27 23:44 ` Tormod Volden [this message]
2011-05-29 23:12 ` [PATCH] drm: Compare only lower 32 bits of framebuffer map offsets Tormod Volden
2011-05-29 23:29 ` Dave Airlie
2011-05-30 19:45 ` [PATCH v2] " Tormod Volden
2011-05-31 22:04 ` Tormod Volden
2011-06-10 22:59 ` Tormod Volden
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=BANLkTim76K-84NKF4GpStG6XtYe+61gKKw@mail.gmail.com \
--to=lists.tormod@gmail.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).