mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kevin Winchester <kjwinchester@gmail.com>
To: Dave Airlie <airlied@linux.ie>
Cc: torvalds@linux-foundation.org, dri-devel@lists.sf.net,
	linux-kernel@vger.kernel.org
Subject: Re: [git pull] drm fixes queue
Date: Mon, 25 Jan 2010 20:40:45 -0400	[thread overview]
Message-ID: <1264466445.1510.5.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.1001250645040.2474@skynet.skynet.ie>

On Mon, 2010-01-25 at 06:46 +0000, 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
> 
> I was out last week for sick kid + LCA dash so stuff queued up behind me, 
> I've booted this across a few radeons.
> 
> core drm changes: one EDID parser fix - one slighty controversial revert
> 	a previous fix for FB blanking although correct, uncovered other
> 	bugs in Intel/radeon KMS drivers, so until fixes for them are available
> 	revert the part of the change the broke stuff.
> 
> nouveau: upstream fixes from F12 testing.
> radeon: fixes all over the place from F12 bugs and upstream AMD changes.
> 	DVI->DP convertors work again
> 	IRQ fixes that fix kexec regression
> 	atombios parser updates from AMD should fix s/r bugs on newer cards
> 	minor r100/r200 command stream parser fixes
> 
> Possible r600 local priv escalation fix, the r600 could be used to access
> system memory if someone was (a) really sneaky, (b) had a lot of time,
> however the commit msg covers it all.
> 
> TTM: fix race condition in object deletion handling
> vmware/staging: bunch of fixes from VMware for the staging driver
> 	
> 

I see that this has not been pulled yet - and of course it is likely due
to the fact that Linus is busy.  But just in case some user feedback
will make a difference, radeon KMS has been refusing to boot for me
since about -rc4 (panic in radeon_agp_init), and I am hoping that this
batch of fixes will correct the problem.

If, however, my hope is misplaced, feel free to let me know so that I
can write up a more formal bug report...

Thanks,

-- 
Kevin Winchester




      reply	other threads:[~2010-01-26  0:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25  6:46 Dave Airlie
2010-01-26  0:40 ` Kevin Winchester [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=1264466445.1510.5.camel@localhost.localdomain \
    --to=kjwinchester@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome