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: <20090826015127.GA1402@zhen-devel.sh.intel.com>
Date:	Wed, 26 Aug 2009 09:51:27 +0800
From:	Zhenyu Wang <zhenyuw@...ux.intel.com>
To:	Eric Anholt <eric@...olt.net>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	mailing54 <mailing54@...k.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dave Airlie <airlied@...hat.com>,
	dri-devel@...ts.sourceforge.net, Ma Ling <ling.ma@...el.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	"Zhao, Yakui" <yakui.zhao@...el.com>
Subject: Re: Linux 2.6.31-rc7

On 2009.08.25 15:33:57 -0700, Eric Anholt wrote:
> > However, the problem remains that KMS gets the output wrong, in ways that 
> > clearly X does not. Eric - it's clearly not just Mac Mini and my 
> > experimental machine that have problems, but also a Macbook 2.1.
> > 
> > I wonder why the Intel KMS logic doesn't look at which output was driven 
> > before it got invoked. Instead, it seems to want to try to detect 
> > everything from scratch, even though we should be able to assume that if 
> > you boot from BIOS (or EFI, for that matter), the current state of the 
> > graphics pipeline is likely meaningful.
> 
> In my experience, the BIOS setup doesn't reflect what outputs should be
> used at runtime, and certainly not the correct configuration of the
> enabled outputs.  For example, if we went to this, the giant monitor
> attached to my laptop that I actually look at would go unused.
> 

yeah, normally VBIOS startup just needs or only can driver one pipe, so
we don't have any pre knowledge except detect everything.

> > And clearly distros are trying to enable this. Which means that this is 
> > getting way more important to solve.
> 
> Yes, please open a bug on bugs.freedesktop.org and set severity=critical
> -- the people working on modesetting should pick it up and take a look
> at it.
> 

we already have some mac relate bugs open, but please report on it so we
do have people with hardware to try and response. We have recently got a
MacBook, yakui is looking after the modesetting issue on it.

> For some of the DDC bugs, David Müller has an interesting-looking patch
> to parse the BIOS's tables describing what DDC pin is used for VGA on
> 852, though it looks like it should be usable on much more.  I was
> hoping the modesetting guys would review it and ack, but no response so
> far.
> 

We should also have floating patch on that, hope we'll prepare and cleanup
the patches for mac soon.

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ