similar to: nouveau on Linux/sparc64 SunBlade 100

Hey all, First off, I'd like to say many thanks to the nouveau developers! I've got a Sun Ultra 10 running Debian 6 (testing branch) with an onboard ATI card and a PCI GeForceMX 4000. So far X works fine on the ATI card, but I noticed that the DRM driver for the GF4 has a few unaligned accesses in it (see log). I can actually start X using that card, but all I get is a black screen

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 all! I read that the older Nvidia hardware (maybe < GF8) is in a different driver and no longer maintained. Is that the case? I have a GeForce 4000 MX that I'm trying to get to work on debian/sparc64, which I admit is a bit of longshot, but I was wondering how much effort it would take to even get the driver to build, and then to function. I'm very proficient in C but don't have

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

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)

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

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.

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. >>

I have a test cluster running HA-NFS that shares both ufs and zfs based file systems. However, the behavior that I am seeing is a little perplexing. The Setup: I have Sun Cluster 3.2 on a pair of SunBlade 1000''s connecting to two T3B partner groups through a QLogic switch. All four bricks of the T3B are configured as RAID-5 with a hot spare. One brick from each pair is mirrored with VxVM

Hi We have installed and configured Samba 2.2.8 on a Solaris (Sparc) 8 server recently. This server is to replace an existing member server in a NT4 domain and will act as a file server. We want to perform as little user maintenance on the Solaris side as possible so that most of the user setup and maintenance for the domain is controlled through a NT4 server using usrmgr and want to use NT

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

I myself am not that well-versed in c and opengl - especially opengl - I can read and write basic c code but that's my limit. The problem only appears when using an offset that's not zero.If you want to debug the issue you could very well use the dolphin-emu and apitrace. You can find one apitrace here http://markus.members.selfnet.de/dolphin/dolphin-emu.trace (~48M) The only 2 reasons I

On Wed, Jul 23, 2014 at 10:52 AM, Patrick Baggett <baggett.patrick at gmail.com> wrote: > On Wed, Jul 23, 2014 at 9:41 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> On Wed, Jul 23, 2014 at 10:32 AM, Clemens Eisserer <linuxhippy at gmail.com> >> wrote: >> > Hi again, >> > >> >> On my NV18 based laptop I experience artifacts

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 >> trouble. Basically functions like pthread_mutex_lock imply that all >>

Thomas, OK, thanks for the update. I don't have a working machine with NV graphics that supports UBOs. Could you compile and run a test program for me if I wrote it? Though it may appear to not work for UBO offsets other than 0, there may be another pattern here, such as multiple of page size or something crazy like that. If we can find more information, it may help other developers. Patrick

pthread_mutex_lock had *better* imply a compiler barrier across which code can't be moved... which is very different from the printf case where it might have done it due to register pressure or who knows what. 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 trouble. Basically

Op 25-02-15 om 16:28 schreef Patrick Baggett: > 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

On Sun, Oct 2, 2011 at 4:24 PM, Baggett Jonas <Jonas.Baggett at hefr.ch> wrote: > Hi, > > I am wondering if someone knows about a VHDL simulator (maybe still in early developpement) that use LLVM in its compilation process. > To summarize, VHDL is a hardware description language, which means that VHDL is like any other programming language except that the output of its synthesis

A simulator should be expecting the machine opcodes not macros. LD shouldn't care at all as long as the object format plays well. I would think it would be better to fix the simulator. Jack ________________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on behalf of llvmdev-request at cs.uiuc.edu [llvmdev-request at cs.uiuc.edu] Sent: Thursday,

I have upgraded my openssh version from 2.2.0.p1 to 3.0.2p1. 3.0.2 was compile on a sunblade 100 running Solaris 8. Is it possible for my to use my existing DSA key? Thanks, David Higdon UNIX System Administrator (503) 450-4800 (Office) (503) 701-5558 (Cell Phone) higdon.david at cnf.com