similar to: Older Nvidia hardware driver state

Op 15-07-13 08:05, Ben Skeggs schreef: > On Fri, Jul 12, 2013 at 10:45 PM, Maarten Lankhorst > <maarten.lankhorst at canonical.com> wrote: >> I have no idea what this bogus restriction on placement is, but it breaks decoding 1080p >> VDPAU at boot speed. With this patch applied I only need to bump the vdec clock to >> get real-time 1080p decoding. It prevents a lot of

Op 04-09-13 03:24, Ben Skeggs schreef: > On Mon, Jul 15, 2013 at 6:39 PM, Maarten Lankhorst > <maarten.lankhorst at canonical.com> wrote: >> Op 15-07-13 08:05, Ben Skeggs schreef: >>> On Fri, Jul 12, 2013 at 10:45 PM, Maarten Lankhorst >>> <maarten.lankhorst at canonical.com> wrote: >>>> I have no idea what this bogus restriction on placement

Hello all, First of all, let me apologize about the length of this message, but I suppose it was necessary to include the details. I've spent quite some time already trying to get the call transfer function to work on my Asterisk installation. Let me first describe the general situation of the setup I am using, so you might be able to pinpoint the cause of the problem. I'm currently

https://bugs.freedesktop.org/show_bug.cgi?id=58984 Priority: medium Bug ID: 58984 Assignee: nouveau at lists.freedesktop.org Summary: DRM NOUVEAU: probe of 0001:01:00.0 failed with error -12 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)

If you're designing a new high-level HDL, then it would be a good idea to familiarise yourself with the state of the art in this area (e.g. Bluespec System Verilog, Symbolics Processor Designer, and similar tools). Starting from comparisons to VHDL and Verilog is like designing a new high-level programming language today that is designed to be a better high-level programming language that is

Hi, For the synthesis backend which translate to VHDL or Verilog, I don't know if I will use LLVM. It will depend on how easy it is to play with concurrent statements with LLVM. For the simulation I will use LLVM because I can anyways artificially make the compiled code sequencial. It would allow me to benefit from all the nice things from LLVM like existing optimisations. I have never

Hello everyone, Thank you nouveau developers as it seems you may almost of a solution to my lack of good graphics options for my aging sun system. I saw here before back in early December of 2011 a most of someone saying that it seemed that the nouveau drivers almost worked with him and is Sun Ultra 10. I am someone who is very fond of my Sun systems, I have two "SunBlade 100"s,

Good Day! I have a fairly new user on my network that has, over about 10 months, created in root inbox and nested sub-folders totaling over 900 individual folders. In the past few weeks, newly created folders will be visible in Outlook 2013, but when an email is moved into that folder, it is no longer visible. I can ssh into the server, drill down to that

Hi all i read the thread on register allocation extensions for better balancing of the binding of variables to registers, especially regarding their concurrent availability through a (probably large) number of read ports. A similar problem would apply for commiting a large number of results (write operands) to the multi-port register file. I'm also interested in this problem since i'm

Hey, On 25-02-15 18:05, Ilia Mirkin wrote: > On Wed, Feb 25, 2015 at 11:59 AM, Patrick Baggett > <baggett.patrick at gmail.com> wrote: >>> If code like >>> >>> x = *a; >>> pthread_mutex_lock or unlock or __memory_barrier() >>> y = *a; >>> >>> doesn't cause a to get loaded twice, then the compiler's in serious

I'm wondering if anyone on the Samba mailing list has seen this problem with Vintela VAS and Samba. ---------- The problem I am having is that Vintela VAS knows about the groups in AD but Samba only seems to recognize a user's primary group in AD. So, if I chgrp a file or directory in Solaris to anything other than a user's primary group and share it out via samba, a user is not

> > Another take (and quite not a longshot although probably Fernando -- thanks for > the debugger, will try it -- has worked either alone or with NVK on the ILP > formulation) is to write-up constraints for an ILP (integer linear programming) > solution. I wouldn't mind to wait forever (for several minutes that is ^_^) for > a valid register allocation to complete. My

Jonas Baggett <jonasb at tranquille.ch> writes: > What are your feedbacks ? Hello Jonas, How is that related to LLVM? I see no references to LLVM on your announcement nor on your document.

I did a very quick pass at removing all the non-KMS support from the DDX. It's tested on G80 but nowhere else currently, I thought some discussion would be a good idea rather than just ripping it out :) The non-KMS paths are messy, and lets face it, rotting badly. IMO the KMS code is stable enough now that we can continue without the UMS crutch, and indeed, the KMS code supports a lot more

On Wed, Feb 25, 2015 at 9:07 AM, Maarten Lankhorst < maarten.lankhorst at ubuntu.com> wrote: > Op 25-02-15 om 16:04 schreef Patrick Baggett: > > On Wed, Feb 25, 2015 at 8:59 AM, Maarten Lankhorst < > > maarten.lankhorst at ubuntu.com> wrote: > > > >> Op 25-02-15 om 15:11 schreef Emil Velikov: > >>> On 24 February 2015 at 09:01, Maarten

On Mon, Jul 15, 2013 at 6:39 PM, Maarten Lankhorst <maarten.lankhorst at canonical.com> wrote: > Op 15-07-13 08:05, Ben Skeggs schreef: >> On Fri, Jul 12, 2013 at 10:45 PM, Maarten Lankhorst >> <maarten.lankhorst at canonical.com> wrote: >>> I have no idea what this bogus restriction on placement is, but it breaks decoding 1080p >>> VDPAU at boot speed.

I have no idea what this bogus restriction on placement is, but it breaks decoding 1080p VDPAU at boot speed. With this patch applied I only need to bump the vdec clock to get real-time 1080p decoding. It prevents a lot of VRAM <-> VRAM buffer moves. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- diff --git a/drivers/gpu/drm/nouveau/nouveau_bo.c

On 25-02-15 18:26, Patrick Baggett wrote: >> >> >> In general things don't get optimized across function calls, except in >> case of inlinable functions. >> >> And for compiler attributes it's the opposite,__attribute__((const)) and >> __attribute((pure)) can be used to indicate some kind of safety to optimize >> across functions. >>

This is admittedly a longshot, but Can you check whether you experience unusually long run times with LLDB? If there’s something strange about tge binaries we generate, maybe lldb will exhibit some strangeness too and we can more easily profile it. On Wed, Jan 9, 2019 at 2:48 PM Shoaib Meenai via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I don't know about the issues with

This is bit of a longshot, but can you try applying https://github.com/dovecot/core/commit/63a74b9.patch and see if this helps? Aki On 19.09.2018 10:33, Reuben Farrelly wrote: > glibc-2.28. > > There was a posting by Michael Marley on 31/08 saying he saw something > similar to this problem after upgrading to 2.28 as well with 'doveadm > purge'. > > Reuben > >