http://bugs.freedesktop.org/show_bug.cgi?id=24844
--- Comment #13 from Bruno <bonbon...@internet.lu> 2009-12-21 13:16:04 PST --- (In reply to comment #12) > If the monitor works now, can we consider this bug closed? I would say yes. > I'm not sure how to correct the connector type as your board has no unique > identifier, but it should work even if the names are wrong. The interesting question in this regard, is IF the newer version of the BIOS that failed resume by rebooting (and some more oddities triggered by suspend/resume-attempt - it might have been fixed on kernel side sine then as well) does also have the wrong connector types. At least that version does have proper unique identifiers. Unfortunately I currently don't have enough unfragmented time available to test that out. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
