Re: [Intel-gfx] Time to wrap up -next

2010-09-29 Thread Chris Wilson 
On Wed, 29 Sep 2010 10:19:00 +0800, Zhenyu Wang zhen...@linux.intel.com wrote:
 No new stuff for now, but FYI current -next has kms regression for me
 and haihao on sandybridge's LVDS and VGA, -fixes works fine.
 
 I haven't done bisect yet.

Hopefully will be simple enough to fix... Thanks for the warning.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] [ANNOUNCE] xf86-video-intel 2.12.902

2010-09-29 Thread Marc Deop i Argemí 
On Wednesday 29 September 2010 05:53:53 Carl Worth wrote:
 This is the second release candidate in preparation for the upcoming
 2.13.0 release. This comes exactly one week after 2.12.902 and includes
 only a handful of changes.
 
 One significant change is that the driver now requires libdrm 2.4.22
 (or newer), as several people reported compilation failures of
 xf86-video-intel 2.12.901 with libdrm 2.4.21.

Compiled fine here on libdrm2.4.22 :)

 
 Other changes include a fix to compile for the 1.6 series X server, a
 fix to retry framebuffer allocation after an initial failure, and a
 fix to disable dri2 after fallbacks are forced on.

Got some errors though:

Xorg.log reports:

(EE) intel(0): Failed to submit batch buffer, expect rendering corruption or 
even a frozen display: Bad file descriptor.

Dmesg:

[drm:i915_gem_do_execbuffer] *ERROR* Object c49c0600 appears more than once in 
object list

It seems to run fine except for the KDE4 effects which do not work  correctly 
(as it also happened on the 901)

Anywhere else I can get more information that would be usefull for you 
developers?

Regards
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] [PATCH v3] CHROMIUM: i915: Added function to initialize VBT settings

2010-09-29 Thread Paul Menzel 
Am Mittwoch, den 29.09.2010, 10:34 +0100 schrieb Chris Wilson:
 On Tue, 28 Sep 2010 16:12:16 -0700, Simon Que s...@chromium.org wrote:
  Hi all,
  
  I have updated the patch containing the dither bit change and VBT
  default settings.  This time, all default values have been moved to a
  single function, init_vbt_defaults.  This function is called from
  intel_init_bios before checking for VBT.  Hence, it is used in both
  the VBT found and VBT not found cases.
  
  The parse functions previously contained VBT default values for the
  case where VBT was found -- those have been moved to the new function
  init_vbt_defaults.  This new arrangement reduces code redundancy (no
  need to set dither bit in two places) and consolidates all default
  settings into one place.
 
 Looks very good. Just one minor niggle... It makes life much easier if
 the patch is in a format digestible by git am.

Christ, Simon attached the patch too.

Simon, I think you can sent the patch inline with your message in the
beginng by using a scissors line.

$ git help mailinfo
[…]
   --scissors
   Remove everything in body before a scissors line. A line that
   mainly consists of scissors (either 8 or 8) and perforation
   (dash -) marks is called a scissors line, and is used to request
   the reader to cut the message at that line. If such a line appears
   in the body of the message before the patch, everything before it
   (including the scissors line itself) is ignored when this option is
   used.

   This is useful if you want to begin your message in a discussion
   thread with comments and suggestions on the message you are
   responding to, and to conclude it with a patch submission,
   separating the discussion and the beginning of the proposed commit
   log message with a scissors line.

   This can enabled by default with the configuration option
   mailinfo.scissors.

   --no-scissors
   Ignore scissors lines. Useful for overriding mailinfo.scissors
   settings.
[…]

And Chris can use `git am -c …` to apply the patch (`git help am`).

[…]


Thanks,

Paul


signature.asc
Description: This is a digitally signed message part
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx