dri-devel January 2013

dri-devel@lists.freedesktop.org

147 participants
795 discussions

[Bug 52121] mgag200 driver does not work properly with Xen in new Intel Server Board
by bugzilla-daemon＠bugzilla.kernel.org 04 Jan '13

04 Jan '13

https://bugzilla.kernel.org/show_bug.cgi?id=52121 --- Comment #18 from Fernando Chaves <fernando(a)supergg.com.br> 2013-01-04 19:34:06 --- Yes, everything works at 100% without Xen, both CLI and Xorg, even in CentOS. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 0

[Bug 52121] mgag200 driver does not work properly with Xen in new Intel Server Board
by bugzilla-daemon＠bugzilla.kernel.org 04 Jan '13

04 Jan '13

https://bugzilla.kernel.org/show_bug.cgi?id=52121 --- Comment #17 from Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> 2013-01-04 19:26:35 --- (In reply to comment #16) > I'm sorry Konrad, but I don't know exactly what you mean when you say "run on > bare metal". without Xen. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 0

[PATCH 0/3] drm_pcie_get_speed_cap_mask() cleanups
by Bjorn Helgaas 04 Jan '13

04 Jan '13

These are minor cleanups for drm_pcie_get_speed_cap_mask() to use standard #defines and PCIe capability accessors. They depend on a pci_regs.h change (130f1b8f35) that appeared in v3.8-rc2. They don't address the issue of DRM devices directly below a host bridge that doesn't appear as a PCI device (the issue Lucas has been working on). I'm a little skeptical about the premise of drm_pcie_get_speed_cap_mask() to begin with. Link speed seems like something fairly generic that should be handled in the core, not in individual drivers. Sec 6.11, "Link Speed Management", in the PCIe 3.0 spec seems relevant and suggests that the hardware should automatically use the highest speed supported by both ends of the link unless software sets a lower maximum via Target Link Speed. But I can't match up the code, e.g., evergreen_pcie_gen2_enable(), to anything in the generic PCIe specs, so maybe this driver code is essentially quirks for misbehaving hardware? --- Bjorn Helgaas (3): drm/pci: Use the standard #defines for PCIe Link Capability bits drm/pci: Set all supported speeds in speed cap mask for pre-3.0 devices drm/pci: Use PCI Express Capability accessors drivers/gpu/drm/drm_pci.c | 27 ++++++++------------------- 1 files changed, 8 insertions(+), 19 deletions(-)

2 4

[Bug 50941] Kernel does not compile
by bugzilla-daemon＠bugzilla.kernel.org 04 Jan '13

04 Jan '13

https://bugzilla.kernel.org/show_bug.cgi?id=50941 --- Comment #3 from JP Pozzi <jp.pozzi(a)izzop.net> 2013-01-04 17:56:28 --- Hello, I try it but ACPI_VIDEO is reset to "m" whenever you "make menuconfig" or compile the kernel. I can't find what other parameters are to be set to "y". At least the kernel compile but I have some problems, after one or two hours the screen (or keyboard ?) get stuck and I have to connect from another machine to stop properly the system. I get the same kind of "screen blocked" with the 3.7.1 kernel. I try it but ACPI_VIDEO is reset to "m" whenever you "make menuconfig" or compile the kernel. I can't find what other parameters are to be set to "y". It is the same for 3.7.1 kernel. Regards JP P -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 0

[PATCH] drm/radeon: fix DMA CS parser for r6xx linear copy packet
by alexdeucher＠gmail.com 04 Jan '13

04 Jan '13

From: Alex Deucher <alexander.deucher(a)amd.com> Was using the r7xx format. Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> --- drivers/gpu/drm/radeon/r600_cs.c | 31 ++++++++++++++++++++++--------- 1 files changed, 22 insertions(+), 9 deletions(-) diff --git a/drivers/gpu/drm/radeon/r600_cs.c b/drivers/gpu/drm/radeon/r600_cs.c index 9ea13d0..03191a5 100644 --- a/drivers/gpu/drm/radeon/r600_cs.c +++ b/drivers/gpu/drm/radeon/r600_cs.c @@ -2677,16 +2677,29 @@ int r600_dma_cs_parse(struct radeon_cs_parser *p) } p->idx += 7; } else { - src_offset = ib[idx+2]; - src_offset |= ((u64)(ib[idx+4] & 0xff)) << 32; - dst_offset = ib[idx+1]; - dst_offset |= ((u64)(ib[idx+3] & 0xff)) << 32; + if (p->family >= CHIP_RV770) { + src_offset = ib[idx+2]; + src_offset |= ((u64)(ib[idx+4] & 0xff)) << 32; + dst_offset = ib[idx+1]; + dst_offset |= ((u64)(ib[idx+3] & 0xff)) << 32; - ib[idx+1] += (u32)(dst_reloc->lobj.gpu_offset & 0xfffffffc); - ib[idx+2] += (u32)(src_reloc->lobj.gpu_offset & 0xfffffffc); - ib[idx+3] += upper_32_bits(dst_reloc->lobj.gpu_offset) & 0xff; - ib[idx+4] += upper_32_bits(src_reloc->lobj.gpu_offset) & 0xff; - p->idx += 5; + ib[idx+1] += (u32)(dst_reloc->lobj.gpu_offset & 0xfffffffc); + ib[idx+2] += (u32)(src_reloc->lobj.gpu_offset & 0xfffffffc); + ib[idx+3] += upper_32_bits(dst_reloc->lobj.gpu_offset) & 0xff; + ib[idx+4] += upper_32_bits(src_reloc->lobj.gpu_offset) & 0xff; + p->idx += 5; + } else { + src_offset = ib[idx+2]; + src_offset |= ((u64)(ib[idx+3] & 0xff)) << 32; + dst_offset = ib[idx+1]; + dst_offset |= ((u64)(ib[idx+3] & 0xff0000)) << 16; + + ib[idx+1] += (u32)(dst_reloc->lobj.gpu_offset & 0xfffffffc); + ib[idx+2] += (u32)(src_reloc->lobj.gpu_offset & 0xfffffffc); + ib[idx+3] += upper_32_bits(src_reloc->lobj.gpu_offset) & 0xff; + ib[idx+3] += (upper_32_bits(dst_reloc->lobj.gpu_offset) & 0xff) << 16; + p->idx += 4; + } } if ((src_offset + (count * 4)) > radeon_bo_size(src_reloc->robj)) { dev_warn(p->dev, "DMA copy src buffer too small (%llu %lu)\n", -- 1.7.7.5

1 0

[Bug 42162] Display not enabled on resume (HP DV6)
by bugzilla-daemon＠freedesktop.org 04 Jan '13

04 Jan '13

https://bugs.freedesktop.org/show_bug.cgi?id=42162 --- Comment #12 from Johan Brannlund <freedesktop-bugs(a)nullinfinity.org> --- Correction: it's *not* a hard lockup - the laptop still responds to ping. It may just be that the keyboard is not working after resume (or even that I mistyped something when trying to reboot it by typing blind). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 42162] Display not enabled on resume (HP DV6)
by bugzilla-daemon＠freedesktop.org 04 Jan '13

04 Jan '13

https://bugs.freedesktop.org/show_bug.cgi?id=42162 --- Comment #11 from Johan Brannlund <freedesktop-bugs(a)nullinfinity.org> --- I'll try bisecting when I have some spare time, but it's probably going to be a few weeks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 42162] Display not enabled on resume (HP DV6)
by bugzilla-daemon＠freedesktop.org 04 Jan '13

04 Jan '13

https://bugs.freedesktop.org/show_bug.cgi?id=42162 --- Comment #10 from Alex Deucher <agd5f(a)yahoo.com> --- (In reply to comment #8) > Resume still doesn't work with kernel 3.8-rc2. However, I now get a hard > lockup on resume. Log attached. Can you bisect to see what caused the hard lock? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 42162] Display not enabled on resume (HP DV6)
by bugzilla-daemon＠freedesktop.org 04 Jan '13

04 Jan '13

https://bugs.freedesktop.org/show_bug.cgi?id=42162 --- Comment #9 from Johan Brannlund <freedesktop-bugs(a)nullinfinity.org> --- Created attachment 72514 --> https://bugs.freedesktop.org/attachment.cgi?id=72514&action=edit Suspend/resume log, kernel 3.8-rc2 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 42162] Display not enabled on resume (HP DV6)
by bugzilla-daemon＠freedesktop.org 04 Jan '13

04 Jan '13

https://bugs.freedesktop.org/show_bug.cgi?id=42162 --- Comment #8 from Johan Brannlund <freedesktop-bugs(a)nullinfinity.org> --- Resume still doesn't work with kernel 3.8-rc2. However, I now get a hard lockup on resume. Log attached. -- You are receiving this mail because: You are the assignee for the bug.

1 0

← Newer
1
...
71
72
73
74
75
76
77
...
80
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2013