search for: aeriksson

...Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: aeriksson at fastmail.fm QAContact: xorg-team at lists.x.org recent git and the screen freezes after launching X. When just running a few xterms, it works ok for a while then it freezes. The mouse continues to move ok, and you can still ssh to the box etc. It _seems_ the freeze can be triggered...

...Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: aeriksson at fastmail.fm QAContact: xorg-team at lists.x.org Afer an upgrade to xorg-server-1.7.0.902 and latest git for the kernel and xorg nouveau drivers I cannot start x with kms under wmaker. As root (just twm and an xterm) it's ok. Dmesg shows: [drm] DAC-6: set mode 1680x1050 1a [drm...

Hi, I once had nouveau working and stable back whem 2.6.29 was released. Nowadays, it hangs within less tahn an hours work. The symptom is that the mouse moves, but no other updates to the screen. The machine is otherwise working mostly ok so I can ssh to it. The "issue" I have is that there is nothing interesting (afaict) in any log. Nothing in Xog.0.log, nothing in dmesg. The one

...een corruption Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: aeriksson at fastmail.fm QAContact: xorg-team at lists.x.org Starting "mplayer -vo xv -hardframedrop anyfile.avi" cuases wmclock and wmcpuload to show garbled icons. Additonally, the video playback is unbearably slow, circa one frame every 5 seconds. Back when 2.6.29 was shipped (at whi...

Afer an upgrade to xorg-server-1.7.0.902 and latest git for the kernel and xorg nouveau drivers I cannot start x with kms under wmaker. As root (just twm and an xterm) it's ok. Dmesg shows: [drm] DAC-6: set mode 1680x1050 1a [drm] nouveau 0000:01:00.0: nv04_dac_mode_set called for encoder 0 [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on CRTC 0 [drm] nouveau 0000:01:00.0: Setting dpms

Ok, thanks for the reply. > In other words, the code generator needs improving to cope with a jump > to an address that is too far away for a PC-relative jump. Should I file this as a bug? If no one better suited is willing to look at this soon, I am willing to give it a try. Any suggestions? Look at the x86 llvm backend and how gcc does it? Regards, Andreas

> Why isn't llvm giving a name to the value returned by the allocas and > using it in the store instructions? Because you pass in an empty string for the name in the new AllocaInst calls below. Replace the empty strings with "argc_addr" or whatever you want. > AllocaInst* argc_alloca = new AllocaInst(argc->getType(), "", >

Hi, is it possible to build LLVM into shared (dynamic) libraries on MacOSX (or other platforms)? I tried "./configure --disable-static --enable-shared=yes" but without success; I still got only the .a-libraries. Regards, Andreas

Hi, This is a follow up to my previous email since I have now found out a bit more about what goes wrong. I am generating JIT code that calls a native function, but I get the following assertion telling me that the PC relative jump is too long: /llvm/lib/Target/PowerPC/PPCJITInfo.cpp:206: failed assertion `ResultPtr >= -(1 << 23) && ResultPtr < (1 << 23) &&

Hi, I am trying to generate LLVM code that calls a "native" function in the parent program (the program hosting the JIT). I think that I have figured out how to do this, but I get the following assertion failure when the LLVM code is executed: ../llvm/lib/Target/PowerPC/PPCJITInfo.cpp:206: failed assertion `ResultPtr >= -(1 << 23) && ResultPtr < (1 << 23)

Switching focus to a previously idle firefox and starting to type in the google bar, the screen locked up (and the display went black and showed 'no signal'). Ssh'ing into the machine, I found this in dmesg: [drm] nouveau 0000:01:00.0: Allocating FIFO number 1 [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 1 [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on