On Mon, 14 Jan 2013, lawsonlu wrote:
> Hi,
>
> I use kernel 3.8-rc2 with haswell support in currently linux os, but the
> kernel will cause black screen on LVDS panel, and the eDP panel is right.
> Another word, the haswell patch in kernel 3.8 can not turn on LVDS panel on
> some sample. Can any
Hi Ville Syrjälä,
> -Original Message-
> From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
> Sent: Friday, January 18, 2013 9:14 PM
> To: Wang, Xingchao
> Cc: intel-gfx@lists.freedesktop.org; daniel.vet...@ffwll.ch; Zanoni, Paulo R
> Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: H
On Sun, Jan 20, 2013 at 04:33:32PM +, Chris Wilson wrote:
> On SNB, if bit 13 of GFX_MODE, Flush TLB Invalidate Mode, is not set to 1,
> the hardware can not program the scanline values. Those scanline values
> then control when the signal is sent from the display engine to the render
> ring fo
On Sun, Jan 20, 2013 at 2:39 PM, Sedat Dilek wrote:
> On Sun, Jan 20, 2013 at 2:30 PM, Sedat Dilek wrote:
>> Hi,
>>
>> I am here on Ubuntu/precise AMD64.
>>
>> With the attached scripts I can't use a i965_dri.so for example from
>> gles3 GIT tree.
>>
>> First, I have built libdrm-2.4.41, installe
On Sun, Jan 20, 2013 at 10:52 PM, Mihai Moldovan wrote:
> the patch does work, i.e., it turns off DMAR for the graphics card and
> alleviates the freezes when loading i915/kms.
>
> However, still seeing random machine freezes with it (being consistent with
> the
> behavior I've experienced with i
DMAR support on g4x/gm45 integrated gpus seems to be totally busted.
So don't bother, but instead disable it by default to allow distros to
unconditionally enable DMAR support.
v2: Actually wire up the right quirk entry, spotted by Adam Jackson.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?
Hi Daniel,
the patch does work, i.e., it turns off DMAR for the graphics card and
alleviates the freezes when loading i915/kms.
However, still seeing random machine freezes with it (being consistent with the
behavior I've experienced with intel_iommu=igfx_off).
The patch + forcing RWBF is workin
On Sun, Jan 20, 2013 at 4:32 PM, Daniel Vetter wrote:
> Changes since the patchbomb on dri-devel:
> - Added a patch to adjust the new omapdrm code in 3.8-rc4, reviewed by Rob
> Clark on irc (hence also why the baseline of this pull is 3.8-rc4).
> - Slightly fixed/clarified some commit messages a
Yanking and re-plugging the DP cable did work when I tried it. My
recollection is that there have been times when it hasn't worked, though
it's possible there was something else going on (user error, etc...)
Regarding the "hotplug interrupt for DP" message: that /does not/ fire when
the screen goe
During the initial bringup of IVB, we set the invalidation control to
the pre-IVB default of always invalidating TLBs on every flush:
commit b095cd0a0ccdbc00c9fd99d90b22f8563687971f
Author: Jesse Barnes
Date: Fri Aug 12 15:28:32 2011 -0700
drm/i915: set GFX_MODE to pre-Ivybridge default va
On SNB, if bit 13 of GFX_MODE, Flush TLB Invalidate Mode, is not set to 1,
the hardware can not program the scanline values. Those scanline values
then control when the signal is sent from the display engine to the render
ring for MI_WAIT_FOR_EVENTs. Note setting this bit means that TLB
invalidatio
This is a required workarounds for all products, especially on gen6+
where it causes the command streamer to fail to parse instructions
following a WAIT_FOR_EVENT. We use WAIT_FOR_EVENT for synchronising
between the GPU and the display engines, and so this bit being unset may
cause hangs.
Referenc
Hi Dave,
I've figured a pull request is easier ;-)
Changes since the patchbomb on dri-devel:
- Added a patch to adjust the new omapdrm code in 3.8-rc4, reviewed by Rob
Clark on irc (hence also why the baseline of this pull is 3.8-rc4).
- Slightly fixed/clarified some commit messages and fixed o
On Sun, Jan 20, 2013 at 2:30 PM, Sedat Dilek wrote:
> Hi,
>
> I am here on Ubuntu/precise AMD64.
>
> With the attached scripts I can't use a i965_dri.so for example from
> gles3 GIT tree.
>
> First, I have built libdrm-2.4.41, installed and ldconfig-ed it before
> building mesa.
>
> I have chosen
Hi,
I am here on Ubuntu/precise AMD64.
With the attached scripts I can't use a i965_dri.so for example from
gles3 GIT tree.
First, I have built libdrm-2.4.41, installed and ldconfig-ed it before
building mesa.
I have chosen a classic XORG prefix!
[ /etc/ld.so.conf.d/xorg.conf ]
# Xorg lib con
A quick release as the last broke USB DisplayLink slave outputs badly. The
performance of those displays was unusable due to a inadvertent change that
caused us to flush the entire scanout over the USB for every drawing
operation.
* Implement the GNOME Build API. A couple of minor changes to make
Hm, it's a DP screen which I've suspected (those are the kind who can
lose sync and go black). But somehow we don't get any hotplug event
when this happens - so the driver has no idea that the link went bad
and that we need to retrain. Can you please test this with this
snippet:
diff --git a/drive
17 matches
Mail list logo