From: Corbin Simpson <mostawesomedude@gmail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: dri-devel@lists.freedesktop.org,
Alexandre Demers <alexandre.f.demers@gmail.com>
Subject: Re: Radeon support state in libkms
Date: Wed, 9 Feb 2011 10:35:51 -0800 [thread overview]
Message-ID: <AANLkTi=VxEqLE1GzSSxazrX1AbUiQTOoF7X7fJ9mbMf-@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1102091448550.5673@casper.infradead.org>
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.
--
When the facts change, I change my mind. What do you do, sir? ~ Keynes
Corbin Simpson
<MostAwesomeDude@gmail.com>
next prev parent reply other threads:[~2011-02-09 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 15:56 Radeon support state in libkms Alexandre Demers
2011-02-09 14:49 ` James Simmons
2011-02-09 18:35 ` Corbin Simpson [this message]
2011-02-11 11:21 ` Jakob Bornecrantz
2011-02-15 14:17 ` Alexandre Demers
2011-02-16 18:40 ` nobled
2011-02-17 14:51 ` Jakob Bornecrantz
2011-02-17 17:13 ` James Simmons
2011-02-17 16:24 ` James Simmons
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='AANLkTi=VxEqLE1GzSSxazrX1AbUiQTOoF7X7fJ9mbMf-@mail.gmail.com' \
--to=mostawesomedude@gmail.com \
--cc=alexandre.f.demers@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsimmons@infradead.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.