[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 --- Comment #12 from Alex Deucher 2011-05-26 23:43:54 --- Created an attachment (id=59642) --> (https://bugzilla.kernel.org/attachment.cgi?id=59642) additional patch If the patch in comment 11 doesn't work, you can try this one as well on top of the patch in comment 11. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 37652] [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 --- Comment #5 from Sven-Hendrik Haase 2011-05-26 23:05:34 PDT --- The warnings about libtxc_dxtn.so might be irritating so I installed the required library but to no avail. After all, it would be fairly strange if ogre's texture shadows used S3TC compression in memory. Further info: My distro is Arch Linux x86_64. The card is a Mobility Radeon X2100. The logs were taken from a very recent git revision. It is not a regression of r300g as I can't remember ever having texture shadows with this driver. They did work back then with r300c, though. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 37652] [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 --- Comment #5 from Sven-Hendrik Haase 2011-05-26 23:05:34 PDT --- The warnings about libtxc_dxtn.so might be irritating so I installed the required library but to no avail. After all, it would be fairly strange if ogre's texture shadows used S3TC compression in memory. Further info: My distro is Arch Linux x86_64. The card is a Mobility Radeon X2100. The logs were taken from a very recent git revision. It is not a regression of r300g as I can't remember ever having texture shadows with this driver. They did work back then with r300c, though. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 37652] [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 --- Comment #4 from Sven-Hendrik Haase 2011-05-26 22:58:35 PDT --- Created an attachment (id=47207) --> (https://bugs.freedesktop.org/attachment.cgi?id=47207) llvmpipe ogrelog -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 37652] [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 --- Comment #3 from Sven-Hendrik Haase 2011-05-26 22:58:18 PDT --- Created an attachment (id=47206) --> (https://bugs.freedesktop.org/attachment.cgi?id=47206) llvmpipe glxinfo -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 37652] [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 --- Comment #4 from Sven-Hendrik Haase 2011-05-26 22:58:35 PDT --- Created an attachment (id=47207) --> (https://bugs.freedesktop.org/attachment.cgi?id=47207) llvmpipe ogrelog -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 37652] [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 --- Comment #3 from Sven-Hendrik Haase 2011-05-26 22:58:18 PDT --- Created an attachment (id=47206) --> (https://bugs.freedesktop.org/attachment.cgi?id=47206) llvmpipe glxinfo -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 37652] [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 --- Comment #2 from Sven-Hendrik Haase 2011-05-26 22:56:03 PDT --- Created an attachment (id=47205) --> (https://bugs.freedesktop.org/attachment.cgi?id=47205) r300g ogrelog -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 37652] [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 --- Comment #2 from Sven-Hendrik Haase 2011-05-26 22:56:03 PDT --- Created an attachment (id=47205) --> (https://bugs.freedesktop.org/attachment.cgi?id=47205) r300g ogrelog -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 37652] [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 --- Comment #1 from Sven-Hendrik Haase 2011-05-26 22:55:05 PDT --- Created an attachment (id=47204) --> (https://bugs.freedesktop.org/attachment.cgi?id=47204) r300g glxinfo -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 37652] [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 --- Comment #1 from Sven-Hendrik Haase 2011-05-26 22:55:05 PDT --- Created an attachment (id=47204) --> (https://bugs.freedesktop.org/attachment.cgi?id=47204) r300g glxinfo -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 37652] New: [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 Summary: [r300g] No texture shadow in ogre3d Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: s...@lutzhaase.com Using r300g, I'm unable to get texture shadows using the ogre3d graphics engine. Mesa texture shadow demos work fine. In fact, in the ogre3d texture shadow showcase demo I can see a very distorted texture shadow on the side of the base plane. In my own scenes, I get no shadows at all. Stencil shadows work just fine. In order to pin down the problem, I ran a few tests. As it turns out, the problem really only exists in r300g (as far as I could test). It works fine in r600g and gallium3d llvmpipe. For reference, it also works in the NVIDIA and AMD proprietary drivers. I also reported the problem in the ogre3d forums (http://www.ogre3d.org/forums/viewtopic.php?f=4&t=64781) but it appears to be the wrong audience to post this issue in. Due to the abstract nature of ogre3d, it is hard for me to create a minimal case without ogre3d. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 37652] New: [r300g] No texture shadow in ogre3d
https://bugs.freedesktop.org/show_bug.cgi?id=37652 Summary: [r300g] No texture shadow in ogre3d Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: sh at lutzhaase.com Using r300g, I'm unable to get texture shadows using the ogre3d graphics engine. Mesa texture shadow demos work fine. In fact, in the ogre3d texture shadow showcase demo I can see a very distorted texture shadow on the side of the base plane. In my own scenes, I get no shadows at all. Stencil shadows work just fine. In order to pin down the problem, I ran a few tests. As it turns out, the problem really only exists in r300g (as far as I could test). It works fine in r600g and gallium3d llvmpipe. For reference, it also works in the NVIDIA and AMD proprietary drivers. I also reported the problem in the ogre3d forums (http://www.ogre3d.org/forums/viewtopic.php?f=4&t=64781) but it appears to be the wrong audience to post this issue in. Due to the abstract nature of ogre3d, it is hard for me to create a minimal case without ogre3d. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 --- Comment #11 from Alex Deucher 2011-05-26 22:19:20 --- Created an attachment (id=59622) --> (https://bugzilla.kernel.org/attachment.cgi?id=59622) fix handling of DP to LVDS bridges This patch on top of drm-radeon-testing should get you up and running. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 --- Comment #10 from Alex Deucher 2011-05-26 21:52:25 --- Can you attach your xorg log and the output of xrandr --verbose from the new kernel? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH v1] drivers: Use kzalloc instead of 'kmalloc+memset', where possible
A previous patch was sent to address this issue at,
https://lkml.org/lkml/2011/5/23/305. Joe Perches suggest that, its best to use
kcalloc for array allocation instead of kzalloc. This version addresses this
issue.
Changes since V0:
Use kcalloc instead of kzalloc for array allocation.
Signed-off-by: Rakib Mullick
---
diff --git a/drivers/ata/sata_dwc_460ex.c b/drivers/ata/sata_dwc_460ex.c
index 1c4b3aa..168b78f 100644
--- a/drivers/ata/sata_dwc_460ex.c
+++ b/drivers/ata/sata_dwc_460ex.c
@@ -1638,13 +1638,12 @@ static int sata_dwc_probe(struct platform_device *ofdev)
const struct ata_port_info *ppi[] = { &pi, NULL };
/* Allocate DWC SATA device */
- hsdev = kmalloc(sizeof(*hsdev), GFP_KERNEL);
+ hsdev = kzalloc(sizeof(*hsdev), GFP_KERNEL);
if (hsdev == NULL) {
dev_err(&ofdev->dev, "kmalloc failed for hsdev\n");
err = -ENOMEM;
goto error_out;
}
- memset(hsdev, 0, sizeof(*hsdev));
/* Ioremap SATA registers */
base = of_iomap(ofdev->dev.of_node, 0);
diff --git a/drivers/gpu/drm/drm_scatter.c b/drivers/gpu/drm/drm_scatter.c
index d15e09b..7525e03 100644
--- a/drivers/gpu/drm/drm_scatter.c
+++ b/drivers/gpu/drm/drm_scatter.c
@@ -83,30 +83,26 @@ int drm_sg_alloc(struct drm_device *dev, struct
drm_scatter_gather * request)
if (dev->sg)
return -EINVAL;
- entry = kmalloc(sizeof(*entry), GFP_KERNEL);
+ entry = kzalloc(sizeof(*entry), GFP_KERNEL);
if (!entry)
return -ENOMEM;
- memset(entry, 0, sizeof(*entry));
pages = (request->size + PAGE_SIZE - 1) / PAGE_SIZE;
DRM_DEBUG("size=%ld pages=%ld\n", request->size, pages);
entry->pages = pages;
- entry->pagelist = kmalloc(pages * sizeof(*entry->pagelist), GFP_KERNEL);
+ entry->pagelist = kcalloc(pages, sizeof(*entry->pagelist), GFP_KERNEL);
if (!entry->pagelist) {
kfree(entry);
return -ENOMEM;
}
- memset(entry->pagelist, 0, pages * sizeof(*entry->pagelist));
-
- entry->busaddr = kmalloc(pages * sizeof(*entry->busaddr), GFP_KERNEL);
+ entry->busaddr = kcalloc(pages, sizeof(*entry->busaddr), GFP_KERNEL);
if (!entry->busaddr) {
kfree(entry->pagelist);
kfree(entry);
return -ENOMEM;
}
- memset((void *)entry->busaddr, 0, pages * sizeof(*entry->busaddr));
entry->virtual = drm_vmalloc_dma(pages << PAGE_SHIFT);
if (!entry->virtual) {
diff --git a/drivers/gpu/drm/radeon/radeon_mem.c
b/drivers/gpu/drm/radeon/radeon_mem.c
index ed95155..988548e 100644
--- a/drivers/gpu/drm/radeon/radeon_mem.c
+++ b/drivers/gpu/drm/radeon/radeon_mem.c
@@ -139,7 +139,7 @@ static int init_heap(struct mem_block **heap, int start,
int size)
if (!blocks)
return -ENOMEM;
- *heap = kmalloc(sizeof(**heap), GFP_KERNEL);
+ *heap = kzalloc(sizeof(**heap), GFP_KERNEL);
if (!*heap) {
kfree(blocks);
return -ENOMEM;
@@ -150,7 +150,6 @@ static int init_heap(struct mem_block **heap, int start,
int size)
blocks->file_priv = NULL;
blocks->next = blocks->prev = *heap;
- memset(*heap, 0, sizeof(**heap));
(*heap)->file_priv = (struct drm_file *) - 1;
(*heap)->next = (*heap)->prev = blocks;
return 0;
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c
index f1a52f9..07ce02d 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c
@@ -585,11 +585,10 @@ int vmw_overlay_init(struct vmw_private *dev_priv)
return -ENOSYS;
}
- overlay = kmalloc(sizeof(*overlay), GFP_KERNEL);
+ overlay = kzalloc(sizeof(*overlay), GFP_KERNEL);
if (!overlay)
return -ENOMEM;
- memset(overlay, 0, sizeof(*overlay));
mutex_init(&overlay->mutex);
for (i = 0; i < VMW_MAX_NUM_STREAMS; i++) {
overlay->stream[i].buf = NULL;
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
index 5408b1b..bfe1bcc 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
@@ -612,11 +612,9 @@ int vmw_surface_define_ioctl(struct drm_device *dev, void
*data,
srf->sizes[0].height == 64 &&
srf->format == SVGA3D_A8R8G8B8) {
- srf->snooper.image = kmalloc(64 * 64 * 4, GFP_KERNEL);
- /* clear the image */
- if (srf->snooper.image) {
- memset(srf->snooper.image, 0x00, 64 * 64 * 4);
- } else {
+ /* allocate image area and clear it */
+ srf->snooper.image = kzalloc(64 * 64 * 4, GFP_KERNEL);
+ if (!srf->snooper.image) {
DRM_ERROR("Failed to alloc
[PATCH] drm/radeon/kms: fix thermal sensor reading on juniper
Am 26.05.2011 00:45, schrieb Alex Deucher: > Uses a different method than other evergreen asics. Strange the temps displayed always seemed to make sense here even with the wrong method :-). Roland
(Short?) merge window reminder
On Tue, 2011-05-24 at 11:07 -0400, jonsmirl at gmail.com wrote: > On Tue, May 24, 2011 at 10:43 AM, Alan Cox > wrote: > > Can we drop most of MCA, EISA and ISA bus if we are going to have a > big > > version change ? A driver spring clean is much overdue and it's all > in > > git in case someone wishes to sneak out at midnight and bring some > crawly > > horror back from the dead. > > 2.8 could mark the beginning of the great cleanup > --- work out the details of what needs to be cleaned and set a goal > --- remove old buses/driver, switch to device tree, graphics, 32/64 > merges, etc > 3.0 would mark its completion Here it go my opinion, Many people ask for beginning of 2.7 kernel series which will end on 2.8, by old numeration. Kernel 2.8 will mainly a major clean up, of support of the very old hardware, like "math co-processor" at only exist in 386 and before Pentium. If some one want put Linux on this very old hardware should use kernel 2.2. However a new numeration of kernel is independent of this, and I agree with new numeration of kernel on drop a number. Last but not least, I would like to see marked a hiper stable kernel , which will be used by Debian guys. Debian guys tend to stop in a kernel which is not the best one, so let we choose for them what is the stable of stables . Best regards, -- S?rgio M. B.
[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 --- Comment #9 from Alex Deucher 2011-05-26 17:10:03 --- (In reply to comment #8) > Would it be possible that the radeon_encoder->encoder_id information is wrong? > And that there is no DP bridge ? No it's correct. You can see the DPCD for the bridge printed and the link seems to train ok. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 Anisse Astier changed: What|Removed |Added Attachment #57162|0 |1 is obsolete|| --- Comment #8 from Anisse Astier 2011-05-26 16:57:21 --- Created an attachment (id=59612) --> (https://bugzilla.kernel.org/attachment.cgi?id=59612) Dmesg with drm-radeon-testing as of 05/26 Just tested drm-radeon-testing, unfortunately, it seems like there is no change, screen is still blank, no backlight. Would it be possible that the radeon_encoder->encoder_id information is wrong? And that there is no DP bridge ? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 --- Comment #12 from Alex Deucher 2011-05-26 23:43:54 --- Created an attachment (id=59642) --> (https://bugzilla.kernel.org/attachment.cgi?id=59642) additional patch If the patch in comment 11 doesn't work, you can try this one as well on top of the patch in comment 11. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 --- Comment #7 from Alex Deucher 2011-05-26 15:45:37 --- There is initial support for DP bridges in drm-radeon-testing: http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=shortlog;h=refs/heads/drm-radeon-testing -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 --- Comment #11 from Alex Deucher 2011-05-26 22:19:20 --- Created an attachment (id=59622) --> (https://bugzilla.kernel.org/attachment.cgi?id=59622) fix handling of DP to LVDS bridges This patch on top of drm-radeon-testing should get you up and running. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
BUG: unable to handle kernel paging request at 6b6b6b6b in radeon_read_ring_rptr()
On Wed, May 25, 2011 at 8:12 PM, Thierry Vignaud wrote: > On 25 May 2011 17:43, Alex Deucher wrote: >>> Xorg from FC14 plus linux kernel 2.6.37, 2.6.38 and 2.6.39 on x86 crashes >>> immediately upon start. >> >> Any reason you are not using kms? > > Any reason you are not respecting the netiquette ? > Quoting nearly 1000 lines unrelated to your one line answer is quite rude :-( So is being a troll.
[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 --- Comment #10 from Alex Deucher 2011-05-26 21:52:25 --- Can you attach your xorg log and the output of xrandr --verbose from the new kernel? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] drm/radeon/kms: remove duplicate reg from r600 safe regs
It got added twice by accident. Signed-off-by: Alex Deucher --- drivers/gpu/drm/radeon/reg_srcs/r600 |1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/radeon/reg_srcs/r600 b/drivers/gpu/drm/radeon/reg_srcs/r600 index a4b0aed..8337548 100644 --- a/drivers/gpu/drm/radeon/reg_srcs/r600 +++ b/drivers/gpu/drm/radeon/reg_srcs/r600 @@ -757,6 +757,5 @@ r600 0x9400 0x9714 VC_ENHANCE 0x9830 DB_DEBUG 0x9838 DB_WATERMARKS -0x00028D28 DB_SRESULTS_COMPARE_STATE0 0x00028D44 DB_ALPHA_TO_MASK 0x9700 VC_CNTL -- 1.7.1.1
[Bug 36563] Unity locks up with latest xorg/mesa/dri/drm
https://bugs.freedesktop.org/show_bug.cgi?id=36563 --- Comment #7 from Rune K. Svendsen 2011-05-26 12:35:15 PDT --- I have found a reliable way of reproducing this bug on this computer at least. Compiz must be enabled. 1. Go to CompizConfig Settings Manager (ccsm) 2. Under "Window Management"->"Resize Window" in the "General" tab, choose "Normal" as the Default Resize Mode. This will cause windows to resize real-time, as they are dragged by their corners/sides. 3. Open up gnome-terminal and start resizing the window quickly, it will lag a lot and eventually hang compiz. The output of gdb after attaching is similar to that of the "Second output" (https://bugs.freedesktop.org/attachment.cgi?id=47160) attached to this bug report. Ie. line #3 in Thread 1 is "radeon_bo_destroy" followed by "radeon_bo_reference" "r600_bo_destroy" "r600_bo_reference" etc. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36563] Unity locks up with latest xorg/mesa/dri/drm
https://bugs.freedesktop.org/show_bug.cgi?id=36563 --- Comment #7 from Rune K. Svendsen 2011-05-26 12:35:15 PDT --- I have found a reliable way of reproducing this bug on this computer at least. Compiz must be enabled. 1. Go to CompizConfig Settings Manager (ccsm) 2. Under "Window Management"->"Resize Window" in the "General" tab, choose "Normal" as the Default Resize Mode. This will cause windows to resize real-time, as they are dragged by their corners/sides. 3. Open up gnome-terminal and start resizing the window quickly, it will lag a lot and eventually hang compiz. The output of gdb after attaching is similar to that of the "Second output" (https://bugs.freedesktop.org/attachment.cgi?id=47160) attached to this bug report. Ie. line #3 in Thread 1 is "radeon_bo_destroy" followed by "radeon_bo_reference" "r600_bo_destroy" "r600_bo_reference" etc. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: BUG: unable to handle kernel paging request at 6b6b6b6b in radeon_read_ring_rptr()
On Wed, May 25, 2011 at 8:12 PM, Thierry Vignaud wrote: > On 25 May 2011 17:43, Alex Deucher wrote: >>> Xorg from FC14 plus linux kernel 2.6.37, 2.6.38 and 2.6.39 on x86 crashes >>> immediately upon start. >> >> Any reason you are not using kms? > > Any reason you are not respecting the netiquette ? > Quoting nearly 1000 lines unrelated to your one line answer is quite rude :-( So is being a troll. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] drm/radeon/kms: fix thermal sensor reading on juniper
On Thu, May 26, 2011 at 11:43 AM, Roland Scheidegger wrote: > Am 26.05.2011 00:45, schrieb Alex Deucher: >> Uses a different method than other evergreen asics. > > Strange the temps displayed always seemed to make sense here even with > the wrong method :-). Yeah, I got the same results from both, so it must just be some very specific cases or boards where it's problematic. Alex
BUG: unable to handle kernel paging request at 6b6b6b6b in radeon_read_ring_rptr()
After enabling CONFIG_DRM_RADEON_KMS in 2.6.39 the problem disappeared. -- Frank
[PATCH] drm/radeon/kms: remove duplicate reg from r600 safe regs
It got added twice by accident. Signed-off-by: Alex Deucher --- drivers/gpu/drm/radeon/reg_srcs/r600 |1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/radeon/reg_srcs/r600 b/drivers/gpu/drm/radeon/reg_srcs/r600 index a4b0aed..8337548 100644 --- a/drivers/gpu/drm/radeon/reg_srcs/r600 +++ b/drivers/gpu/drm/radeon/reg_srcs/r600 @@ -757,6 +757,5 @@ r600 0x9400 0x9714 VC_ENHANCE 0x9830 DB_DEBUG 0x9838 DB_WATERMARKS -0x00028D28 DB_SRESULTS_COMPARE_STATE0 0x00028D44 DB_ALPHA_TO_MASK 0x9700 VC_CNTL -- 1.7.1.1 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36602] Hierarchical Z support for R600
https://bugs.freedesktop.org/show_bug.cgi?id=36602 --- Comment #6 from Alex Deucher 2011-05-26 11:03:48 PDT --- The htile buffer needs to be bound for the life of the Z/S buffer(s) to be effective. I just put together a set of patches to allocate the htile buffer in the ddx along with the Z and stencil buffers. It seems to work ok, but I'm not seeing much change in performance. http://people.freedesktop.org/~agd5f/htile/ -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36602] Hierarchical Z support for R600
https://bugs.freedesktop.org/show_bug.cgi?id=36602 --- Comment #6 from Alex Deucher 2011-05-26 11:03:48 PDT --- The htile buffer needs to be bound for the life of the Z/S buffer(s) to be effective. I just put together a set of patches to allocate the htile buffer in the ddx along with the Z and stencil buffers. It seems to work ok, but I'm not seeing much change in performance. http://people.freedesktop.org/~agd5f/htile/ -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
BUG: unable to handle kernel paging request at 6b6b6b6b in radeon_read_ring_rptr()
>> Any reason you are not using kms? > > Any reason you are not respecting the netiquette ? > Quoting nearly 1000 lines unrelated to your one line answer is quite rude :-( Yeah we knows that only acceptable if you put, Pardon my ignorance I sent this from my phone at the top ;-) Sorry couldn't resist. Dave.
[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 --- Comment #9 from Alex Deucher 2011-05-26 17:10:03 --- (In reply to comment #8) > Would it be possible that the radeon_encoder->encoder_id information is wrong? > And that there is no DP bridge ? No it's correct. You can see the DPCD for the bridge printed and the link seems to train ok. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 Anisse Astier changed: What|Removed |Added Attachment #57162|0 |1 is obsolete|| --- Comment #8 from Anisse Astier 2011-05-26 16:57:21 --- Created an attachment (id=59612) --> (https://bugzilla.kernel.org/attachment.cgi?id=59612) Dmesg with drm-radeon-testing as of 05/26 Just tested drm-radeon-testing, unfortunately, it seems like there is no change, screen is still blank, no backlight. Would it be possible that the radeon_encoder->encoder_id information is wrong? And that there is no DP bridge ? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: (Short?) merge window reminder
On Tue, 2011-05-24 at 11:07 -0400, jonsm...@gmail.com wrote: > On Tue, May 24, 2011 at 10:43 AM, Alan Cox > wrote: > > Can we drop most of MCA, EISA and ISA bus if we are going to have a > big > > version change ? A driver spring clean is much overdue and it's all > in > > git in case someone wishes to sneak out at midnight and bring some > crawly > > horror back from the dead. > > 2.8 could mark the beginning of the great cleanup > --- work out the details of what needs to be cleaned and set a goal > --- remove old buses/driver, switch to device tree, graphics, 32/64 > merges, etc > 3.0 would mark its completion Here it go my opinion, Many people ask for beginning of 2.7 kernel series which will end on 2.8, by old numeration. Kernel 2.8 will mainly a major clean up, of support of the very old hardware, like "math co-processor" at only exist in 386 and before Pentium. If some one want put Linux on this very old hardware should use kernel 2.2. However a new numeration of kernel is independent of this, and I agree with new numeration of kernel on drop a number. Last but not least, I would like to see marked a hiper stable kernel , which will be used by Debian guys. Debian guys tend to stop in a kernel which is not the best one, so let we choose for them what is the stable of stables . Best regards, -- Sérgio M. B. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] drm/radeon/kms: fix thermal sensor reading on juniper
On Thu, May 26, 2011 at 11:43 AM, Roland Scheidegger wrote: > Am 26.05.2011 00:45, schrieb Alex Deucher: >> Uses a different method than other evergreen asics. > > Strange the temps displayed always seemed to make sense here even with > the wrong method :-). Yeah, I got the same results from both, so it must just be some very specific cases or boards where it's problematic. Alex ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] drm/radeon/kms: fix thermal sensor reading on juniper
Am 26.05.2011 00:45, schrieb Alex Deucher: > Uses a different method than other evergreen asics. Strange the temps displayed always seemed to make sense here even with the wrong method :-). Roland ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34822] Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
https://bugzilla.kernel.org/show_bug.cgi?id=34822 --- Comment #7 from Alex Deucher 2011-05-26 15:45:37 --- There is initial support for DP bridges in drm-radeon-testing: http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=shortlog;h=refs/heads/drm-radeon-testing -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 30901] Heroes of Newerth won't start when mesa is compiled with --enable-gallium-llvm
https://bugs.freedesktop.org/show_bug.cgi?id=30901 Damien Grassart changed: What|Removed |Added CC||dam...@grassart.com --- Comment #8 from Damien Grassart 2011-05-26 05:03:02 PDT --- *** Bug 37603 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 37603] r600g with LLVM enabled makes Heroes of Newerth game unplayable
https://bugs.freedesktop.org/show_bug.cgi?id=37603 Damien Grassart changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #3 from Damien Grassart 2011-05-26 05:03:02 PDT --- Yes, it seems that was the issue. Removing the libstdc++ bundled with the game fixed the problem as well. Thanks! *** This bug has been marked as a duplicate of bug 30901 *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 37603] r600g with LLVM enabled makes Heroes of Newerth game unplayable
https://bugs.freedesktop.org/show_bug.cgi?id=37603 Damien Grassart changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #3 from Damien Grassart 2011-05-26 05:03:02 PDT --- Yes, it seems that was the issue. Removing the libstdc++ bundled with the game fixed the problem as well. Thanks! *** This bug has been marked as a duplicate of bug 30901 *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 30901] Heroes of Newerth won't start when mesa is compiled with --enable-gallium-llvm
https://bugs.freedesktop.org/show_bug.cgi?id=30901 Damien Grassart changed: What|Removed |Added CC||damien at grassart.com --- Comment #8 from Damien Grassart 2011-05-26 05:03:02 PDT --- *** Bug 37603 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: BUG: unable to handle kernel paging request at 6b6b6b6b in radeon_read_ring_rptr()
After enabling CONFIG_DRM_RADEON_KMS in 2.6.39 the problem disappeared. -- Frank ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: (Short?) merge window reminder
On Wed, May 25, 2011 at 7:12 AM, Boaz Harrosh wrote: > So if you combine all the above: > > D. Y. N > D - Is the decade since birth (1991 not 1990) > Y - is the year in the decade so you have 3.1.x, 3.2.x, .. 3.10.x, 4.1.X and > so on > Nice incremental number. > N - The Linus release of this Year. So this 3rd one goes up to 4 most > probably. > > Linus always likes, and feels very poetic about the Christmas version release. > He hates it when once it slipped into the next year. So now he gets to > increment > the second digit as a bonus. > > The 2nd digit gets to start on a *one*, never zero and goes up to *10*, to > symbolize > the 1991 birth. And we never have .zero quality, right? > > The first Digit gets incremented on decade from 1991 so on 2011 and not 2010 This is clearly the best suggestion so far - small numbers, somewhat date related (but without stuffing a "2011." on the front). No ".0" releases, ever. But best of all it defines now when we will switch to 4.x.y and 5.x.y so we don't have to keep having this discussion whenever someone thinks that the numbers are getting "too big" (well perhaps when we get to the tenth decade or so :-) So the only thing left to argue is whether the upcoming release should be numbered "3.1.1" as the first release in the first year of the 3rd decade ... or whether we should count 2.6.37 .. 2.6.39 as the first three releases this year and thus we ought to start with "3.1.4" (so we start with "pi"!). Linus: If you go with this, you should let Boaz set the new "NAME" as a prize for such an inspired solution. -Tony ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 2/2] drm/radeon/kms: add blit support for cayman
>@@ -582,11 +588,17 @@ int evergreen_blit_init(struct radeon_device *rdev) > obj_size = ALIGN(obj_size, 256); > > rdev->r600_blit.vs_offset = obj_size; >- obj_size += evergreen_vs_size * 4; >+ if (rdev->family < CHIP_CAYMAN) >+ obj_size += evergreen_vs_size * 4; >+ else >+ obj_size += cayman_vs_size * 4; > obj_size = ALIGN(obj_size, 256); > > rdev->r600_blit.ps_offset = obj_size; >- obj_size += evergreen_ps_size * 4; >+ if (rdev->family < CHIP_CAYMAN) >+ obj_size += evergreen_ps_size * 4; >+ else >+ obj_size += evergreen_ps_size * 4; > obj_size = ALIGN(obj_size, 256); > > r = radeon_bo_create(rdev, obj_size, PAGE_SIZE, true, > RADEON_GEM_DOMAIN_VRAM, Hi, looks like a c&p error using evergreen_ps_size also for cayman ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: (Short?) merge window reminder
On Tue, 24 May 2011, Zimny Lech wrote: Hi, 2011/5/24 Lisa Milne : So I'm toying with 3.0 (and in that case, it really would be "3.0", not "3.0.0" - the stable team would get the third digit rather than the fourth one. How about stardates? This is a wonderful idea! :) I'd rather go for a gardensheduler, which can tell me the optimal color for any given moment *and* do the paint job. If it eventually ends this discussion, it could be renamed "completely fair gardensheduler". That'd make a release made now 64860.8 I really should sleep more... Or drink less coffee ... ;) -- Regards, Martin ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: (Short?) merge window reminder
On 05/23/2011 11:52 PM, Alexey Zaytsev wrote: > On Tue, May 24, 2011 at 00:33, Linus Torvalds > wrote: >> On Mon, May 23, 2011 at 12:20 PM, Ingo Molnar wrote: >>> >>> I really hope there's also a voice that tells you to wait until .42 before >>> cutting 3.0.0! :-) >> >> So I'm toying with 3.0 (and in that case, it really would be "3.0", >> not "3.0.0" - the stable team would get the third digit rather than >> the fourth one. >> >> But no, it wouldn't be for 42. Despite THHGTTG, I think "40" is a >> fairly nice round number. >> >> There's also the timing issue - since we no longer do version numbers >> based on features, but based on time, just saying "we're about to >> start the third decade" works as well as any other excuse. >> >> But we'll see. > > Maybe, 2011.x, or 11.x, x increasing for every merge window started this year? > This would better reflect the steady nature of the releases, but would > certainly break a lot of scripts. ;) My $0.017 on this. Clearly current process is time based. People have said. * Keep Three digit numbers to retain script compatibility * Make it clear from the version when it was released. * Linus said 3 as for 3rd decade * Nice single increment number progression * Please make it look like a nice version number sys-admins will feel at home with So if you combine all the above: D. Y. N D - Is the decade since birth (1991 not 1990) Y - is the year in the decade so you have 3.1.x, 3.2.x, .. 3.10.x, 4.1.X and so on Nice incremental number. N - The Linus release of this Year. So this 3rd one goes up to 4 most probably. Linus always likes, and feels very poetic about the Christmas version release. He hates it when once it slipped into the next year. So now he gets to increment the second digit as a bonus. The 2nd digit gets to start on a *one*, never zero and goes up to *10*, to symbolize the 1991 birth. And we never have .zero quality, right? The first Digit gets incremented on decade from 1991 so on 2011 and not 2010 So here you have it, who said we need to compromise? Free life Boaz ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
BUG: unable to handle kernel paging request at 6b6b6b6b in radeon_read_ring_rptr()
On 25 May 2011 17:43, Alex Deucher wrote: >> Xorg from FC14 plus linux kernel 2.6.37, 2.6.38 and 2.6.39 on x86 crashes >> immediately upon start. > > Any reason you are not using kms? Any reason you are not respecting the netiquette ? Quoting nearly 1000 lines unrelated to your one line answer is quite rude :-(
