From: Brian Paul <brianp-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
To: Pekka Paalanen <pq-X3B1VOXEql0@public.gmane.org>
Cc: mesa-dev
<mesa-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [Mesa-dev] RFC: ctx->Driver.Map/UnmapTextureImage() hooks
Date: Mon, 18 Jul 2011 13:03:43 -0600 [thread overview]
Message-ID: <4E24838F.4030805@vmware.com> (raw)
In-Reply-To: <20110718220022.4231f6ac@farn>
On 07/18/2011 01:00 PM, Pekka Paalanen wrote:
> On Mon, 18 Jul 2011 08:09:17 -0600
> Brian Paul<brianp-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org> wrote:
>
>> On 07/15/2011 02:59 PM, Pekka Paalanen wrote:
>>> On Fri, 15 Jul 2011 12:22:41 -0600
>>> Brian Paul<brianp-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org> wrote:
>>>
>>>> On 07/15/2011 10:07 AM, Dave Airlie wrote:
>>>>> On Fri, Jul 15, 2011 at 4:10 AM, Brian
>>>>> Paul<brian.e.paul-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>>>>>
>>>>>>
>>>>>> The map-texture-image-v4 branch that I just pushed implements
>>>>>> this change. It really cleaned things up for the better and
>>>>>> will lead to a few more follow-on improvements.
>>>>>>
>>>>>> There's no obvious regressions with swrast or the gallium
>>>>>> drivers. I updated the intel driver code and tested i915 and
>>>>>> it seems OK too, but I didn't do a full piglit run on it. I
>>>>>> also updated the legacy r600 driver in case anyone cares but
>>>>>> didn't do any testing of it.
>>>>>>
>>>>>> I didn't update any of the other legacy DRI drivers. Would
>>>>>> anyone object if we simply stop building mach64, r128,
>>>>>> unichrome, sis, etc? I'd be happy to remove those drivers
>>>>>> altogether for that matter.
>>>>>
>>>>> we could EOL those in 7.11, and if anyone wants to ship them,
>>>>> they can just build 7.11 for them.
>>>>
>>>> Sounds good to me. I think we'd only keep the swrast, intel
>>>> and maybe r300/r600 drivers. Opinions?
>>>
>>> Um, don't kill nouveau_vieux, please.
>>
>> Does the old nouveau driver support some GPUs that the gallium
>> nv50/nvc0 drivers don't support?
>
> Yes. Like Corbin said, 'nouveau_vieux' is for NV04-NV2x, while
> the gallium driver 'nouveau' supports NV30 and later.
> http://nouveau.freedesktop.org/wiki/MesaDrivers
>
>> If we want to keep the older driver someone will need to
>> volunteer to update the code to support the new driver hooks.
>
> Sorry, I cannot promise that.
> Nouveau_vieux seems to have been missing a maintainer for
> some time now.
Any of the older DRI drivers that get dropped could easily be revived
later if someone wants to do the work.
-Brian
next prev parent reply other threads:[~2011-07-18 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E03E3A3.8060903@vmware.com>
[not found] ` <CAEUUzO-6YH3YmtzWxfM=Sn3YT+ndDHJxy1bjff0+f_qd8yj_jA@mail.gmail.com>
[not found] ` <CAPM=9twbNrhH+5CFO38UvVOTgMHzMHEfBfRosPGo0=NCN-HaOg@mail.gmail.com>
[not found] ` <4E208571.90805@vmware.com>
[not found] ` <20110715235911.6d2ff4f0@farn.lan>
[not found] ` <4E243E8D.2030605@vmware.com>
2011-07-18 19:00 ` RFC: ctx->Driver.Map/UnmapTextureImage() hooks Pekka Paalanen
2011-07-18 19:03 ` Brian Paul [this message]
2011-07-19 15:12 ` [Nouveau] " Francisco Jerez
2011-07-19 16:04 ` Matt Turner
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=4E24838F.4030805@vmware.com \
--to=brianp-pghwnbhtmq7qt0dzr+alfa@public.gmane.org \
--cc=mesa-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=pq-X3B1VOXEql0@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.