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] [thread-next>] [day] [month] [year] [list]
Message-Id: <1212364575.15633.115.camel@pasglop>
Date:	Mon, 02 Jun 2008 09:56:15 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>,
	David Miller <davem@...emloft.net>,
	James.Bottomley@...senPartnership.com,
	ksummit-2008-discuss@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [Ksummit-2008-discuss] Fixing the Kernel Janitors project

On Sun, 2008-06-01 at 22:22 +0200, Thomas Gleixner wrote:
> On Sun, 1 Jun 2008, Matthew Garrett wrote:
> 
> > On Sun, Jun 01, 2008 at 04:11:01PM +0200, Thomas Gleixner wrote:
> > 
> > > Fix NOHZ/CPUIDLE along with suspend/resume on all participants
> > > laptops, which are probably 50+ different models. That'd be an odd
> > > enough mix of wreckaged hardware / BIOS / ACPI.
> > 
> > If we have in-kernel video reinit for the major vendors by then, sure. 
> > If not, I suspect the majority of issues we'd hit would just be "My 
> > screen doesn't come back".
> 
> And why wouldn't it be a good idea to spend time on adding the video
> reinit right there at the hacking session ?

You mean adding the right sequence of whacking 200+ non documented chip
registers in the right order with the right values that have to be
subtly different on each revision and each OEM implementation ? :-)

At least for ATI, we do have the necessary infos to do it actually. We
can parse tables in the BIOS, we know how to, we have the format and the
necessary interpreter, it's mostly a matter of doing it (and
re-implementing the interpreter in code that is acceptable to the
kernel, last I looked, the one in X isn't).

For nVidia, it's harder though the "nouveau" folks do have figured how
to run some of the BIOS foo too (same thing, BIOS contains magic
"scripts" that can be interpreted to bootstrap the card).

For others (VIA, XGI, ...) I don't know.

Cheers,
Ben.


--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ