On Wed, 2009-08-26 at 11:58 +0800, Zhenyu Wang wrote: Hi From the config file it seems that the CONFIG_FRAMEBUFFER_CONSOLE is set as m. Will you please set it to y and see whether the black screen happens? Thanks. Yakui > On 2009.08.25 20:33:32 -0700, Linus Torvalds wrote: > > On Wed, 26 Aug 2009, Zhenyu Wang wrote: > > > > > > > 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. > > > > Umm. What's your guys point, exactly? > > > > We can't depend on any BIOS display config as you noted before our driver. > And our driver does more flexible config than VBIOS does. > > > The fact is, as-is, YOU DETECT THE WRONG OUTPUTS! > > > > If you actually detected things _right_, none of this would be an issue. > > But you don't. And you seem to have a really hard time even admitting > > that. You try to re-detect things, and you SCREW UP. > > > > We know we have problem on Mac mini, this issue has been known for a while. > And Keith also posted patch at > http://lists.freedesktop.org/archives/intel-gfx/2009-June/002843.html > but I don't know the status of this now. > > > > 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. > > > > Quite frankly, I've reported these things several times. I've been open to > > try patches. Nothing has ever come out of it. > > > > I have a Mac Mini that I reported as broken over a month ago. I have a > > Westemere I've reported as not doing any DDC probing - and that I have to > > disable the LVDS probing on entirely in order to not make KMS set up the > > display to go to a non-existent LVDS port. > > > > You claim that you "detect everything", but quite frankly, you don't. The > > KMS code seems to assume that if it's a mobile chipset, it should have an > > LVDS output - and whether anything is connected to that or not is totally > > immaterial. There's clearly _zero_ "detection" going on. > > > > We've tried many ways to detect LVDS, but none is stable or actually work for > every chip. But now we have DMI quirks for some known no LVDS machine > (including > Mac mini), and we detect through ACPI LID object for LVDS exist. >
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel