From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Eric Anholt <eric@anholt.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
mailing54 <mailing54@plzk.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@redhat.com>,
dri-devel@lists.sourceforge.net, Ma Ling <ling.ma@intel.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"Zhao, Yakui" <yakui.zhao@intel.com>
Subject: Re: Linux 2.6.31-rc7
Date: Wed, 26 Aug 2009 09:51:27 +0800 [thread overview]
Message-ID: <20090826015127.GA1402@zhen-devel.sh.intel.com> (raw)
In-Reply-To: <1251239637.26348.20.camel@gaiman.anholt.net>
[-- Attachment #1: Type: text/plain, Size: 2076 bytes --]
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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-08-26 1:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 1:26 Linux 2.6.31-rc7 Linus Torvalds
2009-08-22 3:09 ` Regression: Linux 2.6.31-rc7 lost sensors on asus mobo Gene Heskett
2009-08-22 3:47 ` Linus Torvalds
2009-08-22 12:56 ` Gene Heskett
2009-08-22 6:12 ` Robert Hancock
2009-08-22 10:54 ` Stefan Richter
2009-08-22 13:48 ` Gene Heskett
2009-08-22 14:38 ` Stefan Richter
2009-08-22 19:55 ` Gene Heskett
2009-08-22 13:40 ` Gene Heskett
2009-08-23 10:56 ` Linux 2.6.31-rc7 Geert Uytterhoeven
2009-08-26 5:06 ` KOSAKI Motohiro
2009-08-25 17:25 ` mailing54
2009-08-25 18:11 ` Linus Torvalds
2009-08-25 21:37 ` mailing54
2009-08-25 22:07 ` Linus Torvalds
[not found] ` <1251239637.26348.20.camel@gaiman.anholt.net>
2009-08-26 1:51 ` Zhenyu Wang [this message]
2009-08-26 3:33 ` Linus Torvalds
2009-08-26 3:47 ` Dave Airlie
2009-08-26 4:13 ` Linus Torvalds
2009-08-26 4:58 ` Dave Airlie
2009-08-26 17:12 ` Linus Torvalds
2009-08-26 17:18 ` Jesse Barnes
2009-08-26 6:26 ` Eric Anholt
2009-08-26 6:35 ` Dave Airlie
2009-08-26 3:58 ` Zhenyu Wang
2009-08-26 4:20 ` Linus Torvalds
2009-09-10 5:47 ` Zhenyu Wang
2009-08-26 10:09 ` ykzhao
2009-08-30 22:01 ` Tino Keitel
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=20090826015127.GA1402@zhen-devel.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--cc=ling.ma@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mailing54@plzk.org \
--cc=torvalds@linux-foundation.org \
--cc=yakui.zhao@intel.com \
/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