linux-kernel - Re: [PATCH 0/5]: ATI/RADEON DRM bug fixes...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 12 Feb 2009 14:19:05 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	airlied@...il.com
Cc:	airlied@...ux.ie, benh@...nel.crashing.org,
	dri-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5]: ATI/RADEON DRM bug fixes...

From: Dave Airlie <airlied@...il.com>
Date: Thu, 12 Feb 2009 21:26:51 +1000

> On Thu, Feb 12, 2009 at 8:15 PM, David Miller <davem@...emloft.net> wrote:
> >
> > David, this work is against your drm-next branch.
> >
> > Here are a collection of bug fixes for the Radeon DRM support.  Most
> > of them have to do with trying to access kernel virtual addresses
> > using DRM_READ32() and DRM_WRITE32().
> >
> > With these patches at least the writeback test works on sparc64 and
> > the CP is able to process commands in the ring.  I'm now diagnosing
> > some further problem that's preventing Xorg from functioning fully but
> > I should be able to diagnose that soon.
> >
> > You'll probably love patch #4 in this series, and it probably explains
> > all kinds of weird problems people run into with DRM on radeon cards.
> 
> Thanks Dave,
> 
> These all look great, the EMITED one has potential to regress
> something by fixing it,
> but I think it might actually make things better, I'll push all of
> these to Linus asap as
> they all fix real bugs. I've put them into my drm-fixes branch and I'll try and
> re-review and get some testing tomorrow when I'm more awake.

Note that these depend upon Ben's drm_addmap and resource fixed in
your drm-next branch, sparc64 was also broken by those problems.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/