linux-kernel - RE: 2.6.19-rc4-mm2

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-next>] [day] [month] [year] [list]

Message-ID: <1C68BCE03F80CD46A821B5B9C5F2163E01D7A05C@EXNA.corp.stratus.com>
Date:	Wed, 8 Nov 2006 09:01:16 -0500
From:	"Richardson, Charlotte" <Charlotte.Richardson@...atus.com>
To:	<ajwade@...mni.uwaterloo.ca>, <andrew.j.wade@...il.com>
Cc:	"Andrew Morton" <akpm@...l.org>, <linux-kernel@...r.kernel.org>,
	"Kimball Murray" <kimball.murray@...il.com>,
	<linux-fbdev-devel@...ts.sourceforge.net>
Subject: RE: 2.6.19-rc4-mm2

Hi, Andrew -

I messed around with trying to recreate the workaround for the 24bpp
Radeon stuff for chips that have the problem (like yours does) all
afternoon yesterday, but I never did get it to work. I can't spend any
more time on this right now (boss is after me!) but I will try to do
some more poking around later or next week. Do you think I should submit
a patch that at least enables 24bpp for the chip I have where it
definitely does work? I'm sure that is overly restrictive, but I don't
know which ones work and which are broken at this point. I tried going
to the ATI web site (we have an OEM agreement with them, so I can get
more data that way) but their documents are no better now that they are
part of AMD than they ever were, and I didn't find anything useful.
Grumble! Actually, as more people use linux and Xfree86, they may have
to do a bit better with the specs. One can hope!

If you get a chance before I do, you might look at what Xfree86 does -
they might have the workaround.

/Charlotte

PS - You have your reply-to email address set to
ajwade@...mni.uwaterloo.ca
which evidently is stale, 'cause replying to that bounces.

> -----Original Message-----
> From: Andrew Wade [mailto:andrew.j.wade@...il.com]
> Sent: Tuesday, November 07, 2006 10:58 AM
> To: Richardson, Charlotte
> Cc: Andrew Morton; linux-kernel@...r.kernel.org; Kimball Murray;
linux-
> fbdev-devel@...ts.sourceforge.net
> Subject: Re: 2.6.19-rc4-mm2
> 
> Hello Charlotte,
> 
> > (Sorry, I don't know what timezone you're in, but I went home,
cooked
> > supper, ate supper, did two loads of laundry, slept for about seven
> > hours, ate breakfast, did another load of laundry, and voted, and
now
> > I'm back!)
> 
> I'm EST (GMT-5). But the hours I'm online are somewhat erratic.
> 
> ...
> > If I can't repro it with this chip, if you want to mess around with
it
> > on yours, here's what I think we had to do... I believe the trick
was
> > to use 16bpp mode as far as what mode you write to the chip, and
then
> > double all the x coordinate values for things like offset, width,
and
> > pitch. You would have to do that to the accelerated routines also.
> 
> I'd be happy to mess around with the driver, but I won't have much
> time to do so until tomorrow. I'll let you know if I find anything,
> and of course I'll be happy to test patches.
> 
> -ajw
-
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/