On Fri, Jan 25, 2013 at 1:50 AM, Andrew Morton
wrote:
> On Fri, 25 Jan 2013 00:42:37 + (GMT)
> Dave Airlie wrote:
>
>> These patches have been sailing around long enough, waiting for a maintainer
>> to reappear, so I've decided enough is enough, lockdep is kinda useful to
>> have.
>>
>> Than
This patch adds display-timing node parsing using video helper function
Signed-off-by: Leela Krishna Amudala
Signed-off-by: Vikas Sajjan
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 35 --
1 file changed, 33 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu
This patch adds display-timing node parsing to drm fimd, this depends on
the display helper patchset at
http://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg33354.html
It also adds pinctrl support for drm fimd.
patch is based on branch "exynos-drm-next" at
http://git.kernel.org/pub/scm/
On 2013/1/28 3:23, Yinghai Lu wrote:
> Replace that with hotplug-safe version.
>
> Signed-off-by: Yinghai Lu
> Cc: David Airlie
> Cc: dri-devel@lists.freedesktop.org
> ---
> drivers/gpu/drm/drm_fops.c | 10 +++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers
On Mon, Jan 28, 2013 at 1:16 AM, Sedat Dilek wrote:
> On Mon, Jan 28, 2013 at 12:52 AM, Sedat Dilek wrote:
>> Hi,
>>
>> From [1]:
>> ...
>> static struct intel_quirk intel_quirks[] = {
>> /* HP Mini needs pipe A force quirk (LP: #322104) */
>> { 0x27ae, 0x103c, 0x361a, quirk_pipea
On Mon, Jan 28, 2013 at 12:52 AM, Sedat Dilek wrote:
> Hi,
>
> From [1]:
> ...
> static struct intel_quirk intel_quirks[] = {
> /* HP Mini needs pipe A force quirk (LP: #322104) */
> { 0x27ae, 0x103c, 0x361a, quirk_pipea_force },
> ...
> }
>
> Triple - which value is what?
>
> 00:0
Hi,
>From [1]:
...
static struct intel_quirk intel_quirks[] = {
/* HP Mini needs pipe A force quirk (LP: #322104) */
{ 0x27ae, 0x103c, 0x361a, quirk_pipea_force },
...
}
Triple - which value is what?
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd
Generation Core
No user now, remove it.
That name is misleading as it only for root buses.
Signed-off-by: Yinghai Lu
Cc: Mauro Carvalho Chehab
Cc: Doug Thompson
Cc: linux-e...@vger.kernel.org
Cc: x...@kernel.org
Cc: David Airlie
Cc: dri-devel@lists.freedesktop.org
Cc: "David S. Miller"
Cc: sparcli...@vger.k
No user now, remove it.
Signed-off-by: Yinghai Lu
Cc: Mauro Carvalho Chehab
Cc: Doug Thompson
Cc: linux-e...@vger.kernel.org
Cc: x...@kernel.org
Cc: David Airlie
Cc: dri-devel@lists.freedesktop.org
Cc: "David S. Miller"
Cc: sparcli...@vger.kernel.org
Cc: Tony Luck
Cc: Fenghua Yu
Cc: linux-i
Now we have pci_root_buses list, and there is lots of iteration with
list_of_each of it, that is not safe after we add pci root bus hotplug
support after booting stage.
Add pci_get_next_host_bridge and use bus_find_device in driver core to
iterate host bridge and the same time get root bus.
We re
Now we have pci_root_buses list, and there is lots of iteration with
list_of_each of it, that is not safe after we add pci root bus hotplug
support after booting stage.
Also pci_find_next_bus is pretty misleading name, and it is only finding
next root bus instead of regular pci bus.
Add pci_get_n
Need to use it for looping registered host_bridge, and kill
pci_root_buses list.
Signed-off-by: Yinghai Lu
Cc: Mauro Carvalho Chehab
Cc: Doug Thompson
Cc: linux-e...@vger.kernel.org
Cc: x...@kernel.org
Cc: David Airlie
Cc: dri-devel@lists.freedesktop.org
Cc: "David S. Miller"
Cc: sparcli...@v
From: Alex Deucher
Hi Dave,
A couple of small fixes I picked up over the weekend.
The following changes since commit 483674325f64a37c7696edb12ce6ad3e535421bc:
Merge branch 'drm-intel-fixes' of
git://people.freedesktop.org/~danvet/drm-intel (2013-01-26 18:17:39 +1000)
are available in t
receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/5d34f426/attachment.html>
signee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/53441eb9/attachment-0001.html>
assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/4b52ac00/attachment.html>
xt part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/c9ecde40/attachment.html>
xt part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/9e8cdbeb/attachment.html>
part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/1ef78fe9/attachment.html>
.dumb_create = dvbe_dumb_create,
+ .dumb_map_offset = dvbe_dumb_map_offset,
+ .dumb_destroy = dvbe_dumb_destroy,
+
+ .name = "dvbe",
+ .desc = "DRM VESA BIOS Extension Driver",
+ .date = "20130127",
+ .major = 0,
+ .minor = 0,
+
From: Alex Deucher
Hi Dave,
A couple of small fixes I picked up over the weekend.
The following changes since commit 483674325f64a37c7696edb12ce6ad3e535421bc:
Merge branch 'drm-intel-fixes' of
git://people.freedesktop.org/~danvet/drm-intel (2013-01-26 18:17:39 +1000)
are available in t
On Sun, Jan 27, 2013 at 7:21 PM, Yijing Wang wrote:
> On 2013/1/28 3:23, Yinghai Lu wrote:
>> Replace that with hotplug-safe version.
>>
>> Signed-off-by: Yinghai Lu
>> Cc: David Airlie
>> Cc: dri-devel@lists.freedesktop.org
>> ---
>> drivers/gpu/drm/drm_fops.c | 10 +++---
>> 1 file chan
On Sun, Jan 27, 2013 at 7:21 PM, Yijing Wang wrote:
> On 2013/1/28 3:23, Yinghai Lu wrote:
>> Replace that with hotplug-safe version.
>>
>> Signed-off-by: Yinghai Lu
>> Cc: David Airlie
>> Cc: dri-devel at lists.freedesktop.org
>> ---
>> drivers/gpu/drm/drm_fops.c | 10 +++---
>> 1 file c
https://bugs.freedesktop.org/show_bug.cgi?id=59945
--- Comment #4 from Alex Deucher ---
Created attachment 73753
--> https://bugs.freedesktop.org/attachment.cgi?id=73753&action=edit
possible fix
The attached mesa patch should fix the issue.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=59945
Alex Deucher changed:
What|Removed |Added
Product|DRI |Mesa
Version|XOrg CVS
Otherwise the system will burn even brighter and worse, leave the user
wondering what's going on exactly.
Since we already have a panic handler which will (try) to restore the
entire fbdev console mode, we can just bail out. Inspired by a patch
from Konstantin Khlebnikov. The callchain leading to
Now that the fbdev helper interface for drivers is trimmed down,
update the kerneldoc for all the remaining exported functions.
I've tried to beat the DocBook a bit by reordering the function
references a bit into a more sensible ordering. But that didn't work
out at all. Hence just extend the in-
This should be done in the drivers for two reasons:
- it gets in the way of fastboot efforts
- it links the fb helpers with the crtc helpers instead of going
through the real interface vfuncs, forcing i915 to fake all the
->disable callbacks used by the crtc helper to avoid ugly Oopsen
v2: Res
On Fri, Jan 25, 2013 at 1:50 AM, Andrew Morton
wrote:
> On Fri, 25 Jan 2013 00:42:37 + (GMT)
> Dave Airlie wrote:
>
>> These patches have been sailing around long enough, waiting for a maintainer
>> to reappear, so I've decided enough is enough, lockdep is kinda useful to
>> have.
>>
>> Than
https://bugs.freedesktop.org/show_bug.cgi?id=59904
--- Comment #4 from Paul Heldens ---
Also OOM kills here, bisected:
68a097596efdf314ec60487a1761cac789ae2367 is the first bad commit
in Xonotic 64 bit and Spring 64 bit games after several minutes of play I run
out of my 8GB ram.
--
You are r
https://bugs.freedesktop.org/show_bug.cgi?id=59946
Priority: medium
Bug ID: 59946
Assignee: dri-devel@lists.freedesktop.org
Summary: [r600g] WoW crashed with "page allocation failure"
Severity: normal
Classification: Unclassified
https://bugs.freedesktop.org/show_bug.cgi?id=58033
--- Comment #17 from Chris Rankin ---
My RV790 (HD4890) is also unaffected by this bug. And this box is 64 bit too.
Could it just be a coincidence that both of my affected boxes are 32 bit?
--
You are receiving this mail because:
You are the as
https://bugzilla.kernel.org/show_bug.cgi?id=52491
--- Comment #17 from Bruno Jacquet 2013-01-27 14:04:31 ---
Indeed, linux 3.8-rc5 with no patch applied is working now, I see no
corruption.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=59945
--- Comment #2 from Martin Andersson ---
Created attachment 73744
--> https://bugs.freedesktop.org/attachment.cgi?id=73744&action=edit
weston
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=59945
--- Comment #1 from Martin Andersson ---
Created attachment 73743
--> https://bugs.freedesktop.org/attachment.cgi?id=73743&action=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=59945
Priority: medium
Bug ID: 59945
Assignee: dri-devel@lists.freedesktop.org
Summary: Launching weston fails with error "radeon
:01:00.0: forbidden register 0x8040 at 558"
ld be
causing some of the issues I'm seeing
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/c0cc10b9/attachment.html>
Replace that with hotplug-safe version.
Signed-off-by: Yinghai Lu
Cc: David Airlie
Cc: dri-devel@lists.freedesktop.org
---
drivers/gpu/drm/drm_fops.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_fops.c b/drivers/gpu/drm/drm_fops.c
index 13
No user now, remove it.
Signed-off-by: Yinghai Lu
Cc: Mauro Carvalho Chehab
Cc: Doug Thompson
Cc: linux-edac at vger.kernel.org
Cc: x86 at kernel.org
Cc: David Airlie
Cc: dri-devel at lists.freedesktop.org
Cc: "David S. Miller"
Cc: sparclinux at vger.kernel.org
Cc: Tony Luck
Cc: Fenghua Yu
No user now, remove it.
That name is misleading as it only for root buses.
Signed-off-by: Yinghai Lu
Cc: Mauro Carvalho Chehab
Cc: Doug Thompson
Cc: linux-edac at vger.kernel.org
Cc: x86 at kernel.org
Cc: David Airlie
Cc: dri-devel at lists.freedesktop.org
Cc: "David S. Miller"
Cc: sparclinu
Replace that with hotplug-safe version.
Signed-off-by: Yinghai Lu
Cc: David Airlie
Cc: dri-devel at lists.freedesktop.org
---
drivers/gpu/drm/drm_fops.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_fops.c b/drivers/gpu/drm/drm_fops.c
index
Now we have pci_root_buses list, and there is lots of iteration with
list_of_each of it, that is not safe after we add pci root bus hotplug
support after booting stage.
Also pci_find_next_bus is pretty misleading name, and it is only finding
next root bus instead of regular pci bus.
Add pci_get_n
Need to use it for looping registered host_bridge, and kill
pci_root_buses list.
Signed-off-by: Yinghai Lu
Cc: Mauro Carvalho Chehab
Cc: Doug Thompson
Cc: linux-edac at vger.kernel.org
Cc: x86 at kernel.org
Cc: David Airlie
Cc: dri-devel at lists.freedesktop.org
Cc: "David S. Miller"
Cc: spar
Now we have pci_root_buses list, and there is lots of iteration with
list_of_each of it, that is not safe after we add pci root bus hotplug
support after booting stage.
Add pci_get_next_host_bridge and use bus_find_device in driver core to
iterate host bridge and the same time get root bus.
We re
.dumb_create = dvbe_dumb_create,
+ .dumb_map_offset = dvbe_dumb_map_offset,
+ .dumb_destroy = dvbe_dumb_destroy,
+
+ .name = "dvbe",
+ .desc = "DRM VESA BIOS Extension Driver",
+ .date = "20130127",
+ .major = 0,
+ .minor = 0,
+
other 3d apps. I have
hd4330 (rv710)
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/2b19ff89/attachment.html>
Otherwise the system will burn even brighter and worse, leave the user
wondering what's going on exactly.
Since we already have a panic handler which will (try) to restore the
entire fbdev console mode, we can just bail out. Inspired by a patch
from Konstantin Khlebnikov. The callchain leading to
Now that the fbdev helper interface for drivers is trimmed down,
update the kerneldoc for all the remaining exported functions.
I've tried to beat the DocBook a bit by reordering the function
references a bit into a more sensible ordering. But that didn't work
out at all. Hence just extend the in-
This should be done in the drivers for two reasons:
- it gets in the way of fastboot efforts
- it links the fb helpers with the crtc helpers instead of going
through the real interface vfuncs, forcing i915 to fake all the
->disable callbacks used by the crtc helper to avoid ugly Oopsen
v2: Res
https://bugzilla.kernel.org/show_bug.cgi?id=52491
--- Comment #17 from Bruno Jacquet 2013-01-27 14:04:31 ---
Indeed, linux 3.8-rc5 with no patch applied is working now, I see no
corruption.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=59332
Mike Lothian changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |i...@freedesktop.org
|.
https://bugs.freedesktop.org/show_bug.cgi?id=59904
--- Comment #3 from Anton Petrov ---
I started to get regular OOM-kills after that commit when i try to play
minecraft. Memory usage with openarena was increased too. Looks like everything
is ok with just compositing desktop without running other
52 matches
Mail list logo
