similar to: [PATCH] nv50/accel: Fix mangled A8+A8 shader.

From: Ben Skeggs <bskeggs at redhat.com> --- src/nv50_accel.c | 38 ++++++++------------------------------ src/nv50_accel.h | 1 - src/nv50_exa.c | 45 ++++++++++++++++++++------------------------- 3 files changed, 28 insertions(+), 56 deletions(-) diff --git a/src/nv50_accel.c b/src/nv50_accel.c index 1218e18..db8c744 100644 --- a/src/nv50_accel.c +++ b/src/nv50_accel.c @@

Regression from "WIP: port to new libdrm". --- src/nv50_accel.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/src/nv50_accel.c b/src/nv50_accel.c index 66d6cb8..7c640f2 100644 --- a/src/nv50_accel.c +++ b/src/nv50_accel.c @@ -44,6 +44,9 @@ NV50SyncToVBlank(PixmapPtr ppix, BoxPtr box) if (!crtcs) return; + if (!PUSH_SPACE(push, 10)) + return; +

https://bugs.freedesktop.org/show_bug.cgi?id=89730 Bug ID: 89730 Summary: NV50: LightDM GTK+ Greeter Background - inconsistent display Product: xorg Version: git Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Would be nice if someone could glance at this... I suppose I could also compare object files. Yeah, I should probably do that. src/nv10_exa.c | 8 ++++---- src/nv30_exa.c | 20 ++++++++++---------- src/nv40_exa.c | 8 ++++---- src/nv50_accel.c | 6 +++--- src/nv50_accel.h | 1 + src/nv50_exa.c

Add proper flushes for TIC and TSC and remove the costly 2D.0110 flush in nv50_flush. Correct TIC and TSC bo sizes. --- src/gallium/drivers/nv50/nv50_context.c | 7 --- src/gallium/drivers/nv50/nv50_context.h | 5 ++ src/gallium/drivers/nv50/nv50_screen.c | 25 ++--------- src/gallium/drivers/nv50/nv50_state_validate.c | 53 +++++++++++++++++++++---

The current code for primitive splitting and emission on pre-nv50 is severely broken. In particular: 1. Quads and lines are totally broken because "&= 3" should be "&= ~3" and similar for lines 2. Triangle fans and polygons are broken because the first vertex must be repeated for each split chunk 3. Line loops are broken because the must be converted to a line strip,

- This avoids problematic "reloc'ed while mapped" messages and some associated corruption as well. Signed-off-by: Maarten Maathuis <madman2003 at gmail.com> --- src/gallium/drivers/nouveau/nouveau_screen.c | 21 +++++++++++++++++++++ src/gallium/drivers/nouveau/nouveau_screen.h | 3 +++ src/gallium/drivers/nouveau/nouveau_stateobj.h | 13 +++++++++++++

http://bugs.freedesktop.org/show_bug.cgi?id=23198 Summary: nv50/NVS135M: video hangs/flickers when fullscreen Product: xorg Version: 7.3 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

I have same problem described in earlier thread: http://lists.xen.org/archives/html/xen-devel/2013-08/msg01395.html Trying to start HVM domain leads to dom0 crash (simple cold reboot). My system is openSUSE 13.1 RC2 with Xen 4.3.0 My hardware is ASRock FM2A75 Pro4 AMD A8-6600K APU Gigabyte Radeon 7850 8 Gb DDR3 1600Mhz I have setup serial console and could provide logs your requested.

嬥堜桪巕偲怽偟傑偡丅 撍慠偺儊乕儖憲怣丄怽偟栿偛偞偄傑偣傫丅 僗億儞僒乕僒僀僩條傛傝擇恖偺彈惈偺徯夘埶棅傪庴偗傑偟偨偺偱丄 偛埬撪偝偣偰偔偩偝偄丅丅 堦愗椏嬥柍偟偺偛徯夘偲側傝傑偡丅 儊乕儖偺憲庴怣傪娷傔丄偳傟偩偗棙梡偟偰捀偄偰傕柍椏偱偡丅 姰慡柍椏偱偺偛徯夘偱偡偺偱憗婜掲傔愗傝偺応崌偑偛偞偄傑偡丅 傑偨丄掲傔愗傝偲側偭偨偲偒偼梊崘側偔彈惈偺曄峏傪偡傞応崌傕偛偞偄傑偡偑丄 偛梕幫偔偩偝偄丅 僋儕僢僋佀丂http://chestnut.happydeeds.com/a12/

On 2013-10-18 7:11 AM, Sebastian Reimers wrote: > Hello!, > > i've just compared the 1.0.3 release with the master branch > on a BeagleBone Black (AM335x 1GHz ARM Cortex-A8 with NEON > floating-point accelerator) and Arch Linux ARM. > > At the moment I dont no why, but I see that 1.1 is much slower > in encoding. Are there any default changes, that I missed and could

I wrote: > In a floating point build > it's enabled only at complexity setting 10 Sorry. I meant that in a _fixed_point_ build the new analysis code is enabled only at complexity setting 10. It's currently enabled for floating point builds at complexity 7 or higher. Both fixed and float builds default to complexity 9 in 1.1. -r

On Fri, Oct 18, 2013 at 2:21 PM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > Just to clear things up... So 1.1 has some new analysis code that > increases the amount of CPU. When building as floating point (which you > appear to be doing, right?), the new code is enabled at complexity 7 and > up (opusenc defaults to complexity 10 IIRC). This is why you've been >

hi all I saw that llvm-2.7 support arm cortex-a8 now, but I didn't find how to cross build it. thank you all -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100505/976c140e/attachment.html>

hi all I use --enable-targets=arm configure LLVM, build it with Clang, but when I using Clang, it say: #clang -triple /root/a.c error: unable to create target: 'No available targets are compatible with this triple, see -version for the available targets.' 1 diagnostic generated. How can I use Clang generate code for ARM Cortex-A8? thank you -------------- next part

Hello > My host is Linux on x86, and I want llvm-gcc generate code for Arm > Cortex-A8. > I saw that in LLVM 2.7 Release Notes, but I can't find step to build > it. Anyone tell me? Build llvm-gcc exactly the same way you're building the cross gcc for your target. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State

Based on the original patch by Christoph Bumiller, but since it depends on kernel support patched I cannot push it yet. The changes are that I enable vblank by default, and offset takes OFFSET_HIGH/LOW instead of something relative to notifier_bo. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- diff --git a/man/nouveau.man b/man/nouveau.man index 7c72907..8765569

Hi, Just to clear things up... So 1.1 has some new analysis code that increases the amount of CPU. When building as floating point (which you appear to be doing, right?), the new code is enabled at complexity 7 and up (opusenc defaults to complexity 10 IIRC). This is why you've been seeing an increase in the CPU time. In version 1.0.x, complexity 5-10 are the exactly the same for music.

Hi. Red Hat is saying that AMD Liano A8 CPU's are not supported by RHEL/CentOS 6: https://access.redhat.com/knowledge/articles/65431 Is that true? What can I expect if I try to install CentOS 6.3 on PC with that CPU? -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe Google is the Mother, Google is the Father, and traceroute is your trusty Spiderman... StarOS,

hi My host is Linux on x86, and I want llvm-gcc generate code for Arm Cortex-A8. I saw that in LLVM 2.7 Release Notes, but I can't find step to build it. Anyone tell me? llvm-gcc now has complete support for the ARM v7 NEON instruction set. This support differs slightly from the GCC implementation. Please see the ARM Advanced SIMD (NEON) Intrinsics and Types in LLVM Blog