On 2010/07/22 23:49 (GMT+0200) david gastao composed:
> I've got a Fujistu/Siemens Amilo L6820 with one of the Intel video chipset,
> 82845G/GL.
> I'm with the Linux distribution Ubuntu 10.04 and i've got video issues
What make and model and size and type and resolution is your display?
> (blac
Hello,
I've got a Fujistu/Siemens Amilo L6820 with one of the Intel video chipset,
82845G/GL.
I'm with the Linux distribution Ubuntu 10.04 and i've got video issues (black
screen time by time, really bad video streaming).
Can you advice me which driver i should use to fix that pls? It would be
[resend b/c I used the wrong from address last time]
I have a 10 bit/channel monitor (DisplayPort) which works quite nicely
in 8 bit mode. I saw some patches from Peter Clifton related to 10
bit support go in awhile ago.
There are (at least) three modes that would be nice:
(1) 8bpp framebuffer,
On Wed, 14 Jul 2010 15:40:56 -0700
Jesse Barnes wrote:
> Fixes https://bugs.freedesktop.org/show_bug.cgi?id=28739. We need to
> enable power to the panel with the AUX VDD bit in order to properly
> detect the eDP attached panel, and we also need to turn the panel on in
> case it was off when we
When enabling the eDP port, we need to make sure the panel is turned on
after training the link. If we don't, it likely won't come back after
suspend or may not come up at all.
For unknown reasons, unlocking the panel regs before initiating a power
on sequence is necessary. There are known bugs
In some cases, unlocking the panel regs is safe and can help us avoid a
flickery, full mode set sequence. So define the unlock key and use it.
Signed-off-by: Jesse Barnes
---
drivers/gpu/drm/i915/i915_reg.h |1 +
drivers/gpu/drm/i915/intel_display.c |6 --
2 files changed, 5 in
We should only free the compressed llb if we allocated it in the first
place otherwise we'll panic at unload time.
Signed-off-by: Jesse Barnes
---
drivers/gpu/drm/i915/i915_dma.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/g
On Thursday 22 July 2010 12:18:36 Pedro Ribeiro wrote:
> That's not what I meant. It appears my dmesg buffer has a limit of
> around ~1200 lines, which fill up in 0.2s. Since the debug output is
> so much, when I hit the bug and go see dmesg, it is already gone.
Sorry about that, it just was the f
Hi Chris,
On Thu, 22 Jul 2010, Chris Wilson wrote:
On Wed, 21 Jul 2010 13:26:11 -0500 (CDT), "Gabriel M. Beddingfield"
wrote:
I'm needing to add a quirk to xf86-video-intel. It looks
like I can get the first two columns from lspci
(chipType, subsysVendor == [VEND:CHIP])...
I have to ask:
Any idea whether this will be applied or not? We find that it resolves
a bug for Ubuntu.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554569?comments=all
Thanks,
Steve Conklin
On Tue, Jul 6, 2010 at 3:21 AM, Zhenyu Wang wrote:
> On 2010.07.02 16:43:30 -0400, Adam Jackson wrote:
>> Fixe
On 22 July 2010 02:14, Marc Deop i Argemí wrote:
> On Thursday 22 July 2010 02:26:08 Pedro Ribeiro wrote:
>> Unfortunately there is so much output that dmesg does not show
>> anything useful - the log is so big that it gets cropped before I get
>> a chance to see it.
>
> dmesg | more
>
That's not
On Wed, 21 Jul 2010 13:26:11 -0500 (CDT), "Gabriel M. Beddingfield"
wrote:
> I'm needing to add a quirk to xf86-video-intel. It looks
> like I can get the first two columns from lspci
> (chipType, subsysVendor == [VEND:CHIP])...
I have to ask: why do you need a quirk in the userspace code? Mo
12 matches
Mail list logo
