From: "Christian König" <deathsimple@vodafone.de>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/6] HDMI clean & DCE32 support
Date: Sat, 20 Mar 2010 17:25:57 +0100 [thread overview]
Message-ID: <1269102357.5144.20.camel@zweiundvierzig> (raw)
In-Reply-To: <21d7e9971003181736g5ae9c6bev828f68822f5efd2@mail.gmail.com>
Am Freitag, den 19.03.2010, 10:36 +1000 schrieb Dave Airlie:
> On Fri, Mar 19, 2010 at 10:14 AM, Mike Lothian <mike@fireburn.co.uk> wrote:
> > Is there any chance we could get these updates included in the
> > drm-radeon-testing branch?
> >
>
> Should all be in there for a week or so.
I can confirm that's working very well, even on my RV710.
And having a nearly standard ubuntu karmic (the kernel is self compiled,
and xorg, mesa etc... updated) on an usb stick with KMS, multihead, HDMI
audio and accelerated 3D working flawlessly is definitely a big step
forward.
Regards,
Christian.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
prev parent reply other threads:[~2010-03-20 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1267880618-9909-1-git-send-email-zajec5@gmail.com>
2010-03-06 13:03 ` [PATCH 2/6] drm/radeon/kms: clean assigning HDMI blocks to encoders Rafał Miłecki
2010-03-06 16:26 ` Christian König
2010-03-06 16:48 ` Rafał Miłecki
2010-03-07 20:59 ` Christian König
2010-03-06 13:03 ` [PATCH 3/6] drm/radeon/kms: add HDMI code for pre-DCE3 R6xx GPUs Rafał Miłecki
2010-03-06 16:46 ` [PATCH 0/6] HDMI clean & DCE32 support Mike Lothian
2010-03-06 16:49 ` Rafał Miłecki
2010-03-06 17:14 ` Mike Lothian
2010-03-19 0:14 ` Mike Lothian
2010-03-19 0:36 ` Dave Airlie
2010-03-20 16:25 ` Christian König [this message]
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=1269102357.5144.20.camel@zweiundvierzig \
--to=deathsimple@vodafone.de \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
/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.