All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Dave Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, dri-devel@lists.sf.net
Subject: Re: [git pull] drm tree.
Date: Mon, 21 Sep 2009 18:40:50 -0400	[thread overview]
Message-ID: <200909211840.51414.edt@aei.ca> (raw)
In-Reply-To: <a728f9f90909210717j11bfa6f3s395e078ed7ac62dd@mail.gmail.com>

On Monday 21 September 2009 10:17:59 Alex Deucher wrote:
> On Mon, Sep 21, 2009 at 7:59 AM, Ed Tomlinson <edt@aei.ca> wrote:
> > On Monday 21 September 2009 01:12:54 Dave Airlie wrote:
> >>
> >> Hi Linus,
> >>
> >> Please pull the 'drm-linus' branch from
> >> ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-linus
> >>
> >> This contains the main chunk of the drm changes for 2.6.32, I think Eric
> >> has been on holidays for a week so I'd expect some more Intel changes
> >> incoming in the merge window. It also contains a few merges for things
> >> that were conflicting with things I sent to you via the drm-fixes tree,
> >> but they weren't always trivial.
> >>
> >> Major highlights core drm/non-kms:
> >> move mga/r128/radeon to firmware loader - major LOC churn,
> >> decreases in-memory radeon module footprint quite a bit.
> >> r600 3D support in non-kms mode.
> >
> > Dave,
> >
> > What user space stuff (xorg/mesa) is required to use the R300 3D?
> >
> 
> r300 3D has been available for years.  If you mean r600 3D, you need
> xf86-video-ati 6.12.4 or newer and mesa from git master.

Alex

Thanks, I did mean R600.

Ed

> >
> >> VGA arbitration support for core drm and kms (was waiting for
> >> jbarnes tree to land).
> >>
> >> core KMS:
> >> add support for GTF/CVT/DMT modes, gets us a long way towards X
> >> merge intel and radeon kms framebuffer implementations for sanity.
> >>
> >> radeon KMS:
> >> R600 KMS support + acceleration support.
> >> move to generating the safe register tables with a script.
> >> radeon tv-out supported ported from userspace
> >> rn50/r100/r200 command submission trackers added
> >>
> >> intel:
> >> some IGDNG fixes
> >> important fix for wrapping at end of ring
> >> more SDVO tv-out support
> >> dynamic clocking support
> >>
> >
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart your
> > developing skills, take BlackBerry mobile applications to market and stay
> > ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> > http://p.sf.net/sfu/devconf
> > --
> > _______________________________________________
> > Dri-devel mailing list
> > Dri-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/dri-devel
> >
> 
> 

  reply	other threads:[~2009-09-21 22:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21  5:12 [git pull] drm tree Dave Airlie
2009-09-21 11:59 ` Ed Tomlinson
2009-09-21 14:17   ` Alex Deucher
2009-09-21 22:40     ` Ed Tomlinson [this message]
2009-09-21 16:12 ` [origin tree build failure] [PATCH] " Ingo Molnar
2009-09-21 16:50   ` [PATCH] drm: Fix build failure in radeon and i915 drivers Ingo Molnar
2009-09-22  3:56   ` [origin tree build failure] [PATCH] Re: [git pull] drm tree Dave Airlie
2009-09-22  9:36     ` Ingo Molnar
2009-09-22 10:27     ` Ingo Molnar
2009-09-22 10:31       ` Dave Airlie
2009-09-22 10:33       ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2010-04-01  7:32 Dave Airlie
2010-04-01  7:32 Dave Airlie
2010-04-01  7:44 ` Rafał Miłecki
2010-04-01  7:44 ` Rafał Miłecki
2010-08-05 10:48 Dave Airlie

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=200909211840.51414.edt@aei.ca \
    --to=edt@aei.ca \
    --cc=airlied@linux.ie \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.sf.net \
    --cc=linux-kernel@vger.kernel.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.