All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Mike Lothian <mike@fireburn.co.uk>
Cc: "Christian König" <deathsimple@vodafone.de>,
	dri-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/6] HDMI clean & DCE32 support
Date: Sat, 6 Mar 2010 17:49:37 +0100	[thread overview]
Message-ID: <b170af451003060849g44b8ec1em3574704cdc5c2f22@mail.gmail.com> (raw)
In-Reply-To: <f3f71ab91003060846s2bab9639kb2c6448700214049@mail.gmail.com>

2010/3/6 Mike Lothian <mike@fireburn.co.uk>:
> 2010/3/6 Rafał Miłecki <zajec5@gmail.com>:
>> This patchset cleans our HDMI code and adds support for DCE32.
>>
>> It was tested on:
>> 1) RV620 with HDMI - no regressions
>> 2) RV635 with 2 DVI - no regressions
>> 3) RV730 with HDMI - made it work
>>
>> Would be more than great if we still could get this for 2.6.34.
>>
>> I could not do this work without help from Christian and Alex, so big thanks
>> for them :)
>>
>> Rafał Miłecki (6):
>>  drm/radeon/kms: clear HDMI definitions
>>  drm/radeon/kms: clean assigning HDMI blocks to encoders
>>  drm/radeon/kms: add HDMI code for pre-DCE3 R6xx GPUs
>>  drm/radeon/kms: enable audio engine on DCE32
>>  drm/radeon/kms: remove dead audio/HDMI code
>>  drm/radeon/kms: improve coding style a little
>>
>>  drivers/gpu/drm/radeon/r600_audio.c      |   57 +++-------
>>  drivers/gpu/drm/radeon/r600_hdmi.c       |  191 +++++++++++++++++++-----------
>>  drivers/gpu/drm/radeon/r600_reg.h        |   10 +-
>>  drivers/gpu/drm/radeon/radeon.h          |    3 +-
>>  drivers/gpu/drm/radeon/radeon_encoders.c |   10 +-
>>  drivers/gpu/drm/radeon/radeon_mode.h     |    1 +
>>  drivers/gpu/drm/radeon/rv770.c           |   15 +++
>>  7 files changed, 166 insertions(+), 121 deletions(-)
>>
>>
>
> Hi Rafal
>
> What kernel do these patches apply cleanly to? Or equally is there a
> git tree I could pull somewhere?

I do not have own tree, I based patches on drm-linus.

-- 
Rafał

------------------------------------------------------------------------------
Download Intel&#174; 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
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

  reply	other threads:[~2010-03-06 16:49 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 [this message]
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

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=b170af451003060849g44b8ec1em3574704cdc5c2f22@mail.gmail.com \
    --to=zajec5@gmail.com \
    --cc=deathsimple@vodafone.de \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=mike@fireburn.co.uk \
    /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.