Re: Radeon support state in libkms

From: Jakob Bornecrantz <wallbraker@gmail.com>
To: nobled <nobled@dreamwidth.org>
Cc: dri-devel@lists.freedesktop.org, alexandre.f.demers@gmail.com
Subject: Re: Radeon support state in libkms
Date: Thu, 17 Feb 2011 15:51:45 +0100	[thread overview]
Message-ID: <AANLkTimiAXft12m3wS=0djvm08OHsJzrZant-L+5vngZ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikeL_cbfCP7np2j3vA2uEp91ZQz5qMjhcaQOJO9@mail.gmail.com>

On Wed, Feb 16, 2011 at 7:40 PM, nobled <nobled@dreamwidth.org> wrote:
> On Tue, Feb 15, 2011 at 9:17 AM, Alexandre Demers
> <alexandre.f.demers@gmail.com> wrote:
>> On 11-02-11 06:21 AM, Jakob Bornecrantz wrote:
>>> On Wed, Feb 9, 2011 at 7:35 PM, Corbin Simpson
>>> <mostawesomedude@gmail.com> wrote:
>>>> On Wed, Feb 9, 2011 at 6:49 AM, James Simmons <jsimmons@infradead.org> wrote:
>>>>>> I was looking at the radeon support state in libkms and I found out the
>>>>>> following patch was proposed back in September, but never commented nor
>>>>>> merged. The patch was submitted by nobled.
>>>>>>
>>>>>> http://lists.freedesktop.org/archives/dri-devel/2010-September/003740.html
>>>>>>
>>>>>> I applied it on the latest drm git version without any problem and
>>>>>> compilation looks fine. Is there a reason preventing it from being merged?
>>>>>>
>>>>>> If it needs testing, make your suggestion, I'll gladly make my best to
>>>>>> test it.
>>>>> Good point. Is KMS dead? Anyone?
>>>> I was seriously hoping that Dave's dumb buffer API would go upstream
>>>> and that libkms would be able to use that generic path for all KMS
>>>> drivers, rather than needing shim code for every driver it supports.
>>>>
>>>> That said, yeah, the libkms maintainer probably should pull that code
>>>> in. Who is that, anyway?
>>>>
>>>> ~ C.
>>> That would probably be me.
>>>
>>> The "core" libkms changes are rb/acked and the radeon changes looks
>>> good so just go ahead and commit them anyways. Nobled do you have
>>> commit access to the drm repo?
>>>
>>> Cheers Jakob.
>>
>> I don't think Nobled has commit access. But to be sure, I'm adding it to
>> the conversation. ;)
>>
>> --
>> Alexandre Demers
>>
>>
>>
>>
>
> Haha, no, no commit access. (not subscribed on dri-devel, either, so
> thanks for the CC)

Do I have your sob, for the patch?

>
> But while I'm here, is there any advice anywhere for getting patches
> noticed a little... sooner? 'Cause I have a whole bunch of *other*
> months-old mesa-dev patches nobody's committed yet.

Poke us more, sorry sometimes we are just bussy with work...

Cheers Jakob.