similar to: [TEST REQUEST] Implementation of INIT_COMPUTE_MEM.

For a long time the gallium pipe drivers for nvidia fixed function cards (nv0x, nv1x and, to some extent, nv2x) have remained unmaintained and godforsaken -- especially nv0x and nv1x had seen almost no progress since their creation. They've recently grown a classic mesa driver which implements many new features: texturing, hardware-accelerated tnl. However the killer feature is "it

Have the following problems: MBO USB-MultiCardREader 6-in-1 does not read 128MB CF-Card. Oct 3 13:49:23 katrin /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Oct 3 13:49:23 katrin /kernel: da0: <ICSI IC1100 CF 2.5B> Removable Direct Access SCSI-0 device Oct 3 13:49:23 katrin /kernel: da0: 650KB/s transfers Oct 3 13:49:23 katrin /kernel: da0: Attempt to query device size failed:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Good day! - From Nouveau feature matrix page: >SLI or even multicard setups are very rare among developers. >You should start hacking with us, if you have such a setup. I have two GTX 770 cards running in SLI[1] and would like to help bringing SLI capability into Nouveau. I would gladly write code for it and I am a competent C programmer

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c:584: warning: Function parameter or member 'init' not described in 'init_reserved' drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c:611: warning: expecting prototype for INIT_DONE(). Prototype was for init_done() instead [Snipped ~140 lines for brevity] Cc: Ben Skeggs <bskeggs at

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c:584: warning: Function parameter or member 'init' not described in 'init_reserved' drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c:611: warning: expecting prototype for INIT_DONE(). Prototype was for init_done() instead [Snipped ~140 lines for brevity] Signed-off-by: Lee Jones

From: Robin Mordasiewicz <robin at bullseye.tv> > I have an excellent nvidia graphics card, I get excellent fps, all agp > features are installed correctly etc. In Windows or Linux? And by "all agp features are installed correctly," what do you mean and how are you getting this? > When I drag windows around wit hthe opaque settings on it leaves traces > for a

http://bugs.freedesktop.org/show_bug.cgi?id=25685 Summary: Write access request to the mesa project. Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at lists.freedesktop.org

On Mon, Mar 3, 2014 at 5:41 PM, Nils Krafft <fehmarn-rund at ffti.de> wrote: > Hello, > > I have here a GeForce 2MX (NV10) with a Brooktree BT869 chip for the > TV-Out. http://nouveau.freedesktop.org/wiki/FeatureMatrix/ See note #4 -- nv0x-nv2x (nv17-nv19 excluded) need an external, third-party manufactured TV encoder. Only some Chrontel branded chips are currently supported.

From: Sukru TIKVES <sukru at cs.hacettepe.edu.tr> > Looks like I've complete misunderstood the issue. > Actually I've never thought it would still be problem. > I usually feel no difference between windows and linux. Correct. But in select operations, you are seeing this. That could be an application-specific setting, including the Window Manager which includes a number

I can't seem to find the info I'm looking for in google, hopefully someone has dealt with these sorts of issues in the past. I have a machine where my messages file keeps getting lines like: Mar 13 18:34:43 nemesis kernel: usb 2-6: reset high speed USB device number 2 using ehci_hcd Mar 13 18:34:57 nemesis kernel: usb 2-6: reset high speed USB device number 2 using ehci_hcd Mar 13

https://bugs.freedesktop.org/show_bug.cgi?id=39033 Summary: Second card not activated Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

http://bugs.freedesktop.org/show_bug.cgi?id=22763 Summary: suspend doesn't works Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

One of the new “feature” is that emails are HTML only right now. Not quite nice for the archive (or for interacting by email). See for instance: http://lists.llvm.org/pipermail/cfe-commits/Week-of-Mon-20160926/172081.html (Also the funky "[Changed Subscribers] “ in the title) Another issue is that we can’t delete unposted inline comment anymore. — Mehdi > On Sep 29, 2016, at 9:35 PM,

Full_Name: Andrew Piskorski Version: R 2.9.2 (Patched), 2009-09-24, svn.rev 49930, x86_64-unknown-linux-gnu OS: Linux, Ubuntu 8.04.3 LTS Submission from: (NULL) (66.31.65.247) I have a large memory test case which segaults R everytime in an fgets call from R's do_system (see below). This appears to be because R does not check the return value of the system popen, and I have a simple patch

Hi everyone. I'm trying nouveau on my dual 285GTX setup. The first card works fine, fast and smooth. But starting everything more than basic icewm (and sometimes even it doesn't work) on the second one either freezes the system or restarts xorg. I'm attaching dmesg, Xorg.0.log and xorg.conf Thanks for any help Alberto Mattea -------------- next part -------------- An embedded and

I have installed and configured the puppet client nodes to use LDAP to authenicate users. LDAP connection is OK and user can be authenicated via LDAP. I use nscd and with my ldap config setting specify on /etc/ldap.conf However, puppet is not happy; and in the /var/log/messages it gives tons of puppet-agent[27499]: nss_ldap: could not search LDAP server puppet-agent[27499]: nss_ldap:

Hi all, Can someone comment on SLI support in nouveau? I'm trying to run KMS (with Plymouth) and nouveau on dual 8800GTXs and not having much (any) luck, I think the message I get is "GPU deadlock". Thanks, -- -jp I bet the sparrow looks at the parrot and thinks, yes, you can talk, but LISTEN TO YOURSELF! deepthoughtsbyjackhandey.com -------------- next part -------------- An

Hi,   I developed a Loop Interchange pass. Please take a look. I have not incorporate data dependence analysis check. I can insert it when the LoopDependenceAnalysis is available.   Thank you Satya -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100713/654d5fd5/attachment.html> --------------

I'm trying to declare a few date-related global variables to ease my dialplan. When I declare the following in the [globals] context of extensions.conf, I get unexpected results: YEAR = ${STRFTIME(${EPOCH},,%Y)} MONTH = ${STRFTIME(${EPOCH},,%m)} DAY = ${STRFTIME(${EPOCH},,%d)} TIMESTAMP = ${STRFTIME(${EPOCH},,%Y%m%d-%H%M%S)} If I evaluate these variables in the dialplan later, using exten

Hi Patch "drm/nouveau: use drm_mm in preference to custom code doing the same thing" in nouveau tree introduced new deadlock possibility, for which lockdep complains loudly: [ 1541.070202] [drm] nouveau 0000:02:00.0: Allocating FIFO number 3 [ 1541.084772] [drm] nouveau 0000:02:00.0: nouveau_channel_alloc: initialised FIFO 3 [ 2417.733440] [drm] nouveau 0000:02:00.0: