search for: pram

Hi Is it possible to combine multiple LLVM with PRAM /XMT? Prof. Uzi Vishkin (Univ. of Maryland) had created 64 cores PRAM: Parallel Random Access Memory / Explicit Multi Threading. Example: 1. The programmer can create multiple LLVM and run the same instruction on different LLVM, or create a pipeline on multiple LLVM (different instruction on diff...

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2775 bytes Desc: image001.gif Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20070417/437dacf8/attachment-0001.gif

...OpenSolaris (sol-nv-b75-sparc-...iso), created an empty image for the hard disk, and tried to start qemu in a linux x64bit-host: qemu-system-sparc -hda test.img -cdrom sol-nv-b75-sparc-v1.iso -boot d -nographic The output says: Nvram id QEMU_BIOS, version 1 CPUs: 1 nvram error detected, zapping pram Welcome to OpenBIOS v1.0RC1 built on Sep 21 2006 18:03 Type ''help'' for detailed information Nvram id QEMU_BIOS, version 1 CPUs: 1 nvram error detected, zapping pram Welcome to OpenBIOS v1.0RC1 built on Sep 21 2006 18:03 Type ''help'' for detailed information [...

A quick look over the memory reclocking part inside the maxwell mmiotraces kind of reminded me of the kepler memory reclocking, it looks for most parts the same. I didn't do a deep inspection so treat this with great care, but it seems to work at least on those maxwell gpus this was tested on. It depends on the PMU fixes for the fuc5 though, otherwise the PMU might not work as expected and

...crashes in strange places which looks like its caused by stack overflow or data corruption. question is; are there any clean way of reducing memory usage? the stack at the end of the state object, is it only accessed through the PUSH macros? perhaps I could write some wrappers to use Program RAM (PRAM) instead, which is not directly accessible. thanks. -- Alfred E. Heggestad <alfredh@sxdesign.com>

...;>>". Pressing them does nothing. When the TRANSFER button is pressed again, CallA is connected to CallB (the original caller is now talking to the previously unanswered party) not what one wanted to happen! It's not difficult to see why my client is throwing their toys out of the pram and I'm going to have to replace the Snoms at my expense :-( -- Regards, Russell -------------------------------------------------------------------- | Russell Brown | MAIL: russell at lls.com PHONE: 01780 471800 | | Lady Lodge Systems | WWW Work: http://www.lls.com...

...nouveau/nvkm/subdev/fb/ramgt215.c b/drivers/gpu/drm/nouveau/nvkm/subdev/fb/ramgt215.c index cb50539..edbe8e4 100644 --- a/drivers/gpu/drm/nouveau/nvkm/subdev/fb/ramgt215.c +++ b/drivers/gpu/drm/nouveau/nvkm/subdev/fb/ramgt215.c @@ -940,7 +940,8 @@ gt215_ram_new(struct nvkm_fb *fb, struct nvkm_ram **pram) struct gt215_ram *ram; int ret, i; - if (!(ram = kzalloc(sizeof(*ram), GFP_KERNEL))) + ram = kzalloc(sizeof(*ram), GFP_KERNEL); + if (!ram) return -ENOMEM; *pram = &ram->base; -- 2.10.0

...d: 30.0 ups.mfr: Mustek ups.model: PowerMust ups.serial: unknown ups.status: OL I have been google'ing a lot, but haven't been able to find at solution to the problem. Is it at all possible with the PowerMust driver? Any help I very much appreciated. Thank you Regards, Johan Pramming -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20060817/35ca5d6a/attachment.html

.../ACE.DOC ./README ./README.ACE ./README .avas ./README~1.AVA ./WS_FTP.LOG /R/rw1000/library/acepack/ /R/TOOLS/MAKE.EXE -C ./src RHOME=/R/rw1000 \ -f /R/rw1000/src/gnuwin32/MakeDll DLLNAME=acepack g77 -O2 -Wall -c ace.f -o ace.o ace.f: In subroutine `mace': ace.f:89: warning: common /prams/ itape,maxit,nterm,span,alpha,big ^ Initial padding for common block `prams' is 4 bytes at (^) -- consider reorderin g members, largest-type-size first ace.f:206: warning: 310 call scale (p,n,w,sw,ty(1,is),tx(1,1,is),delrsq,p,z(1,5),z(1,6)) ^ Reference to un...

In platform i386-pc-linux-gnu arch i386 os linux-gnu system i386, linux-gnu status major 1 minor 7.1 year 2003 month 06 day 16 language R using debian testing (latest Knoppix) I get an error when installing acepack: gcc

...34 // 0x0000000b + ram_wr32(fuc, 0x100b0c, 0x00080028); + ram_wr32(fuc, 0x611200, 0x00003330); + } else { ram_wr32(fuc, 0x10f200, 0x00ce0000); ram_wr32(fuc, 0x10f614, 0x60044e77); ram_wr32(fuc, 0x10f610, 0x60044e77); @@ -630,7 +670,7 @@ gf100_ram_new(struct nvkm_fb *fb, struct nvkm_ram **pram) struct nvkm_subdev *subdev = &fb->subdev; struct nvkm_bios *bios = subdev->device->bios; struct gf100_ram *ram; - int ret; + int i, ret; if (!(ram = kzalloc(sizeof(*ram), GFP_KERNEL))) return -ENOMEM; @@ -663,11 +703,8 @@ gf100_ram_new(struct nvkm_fb *fb, struct nvkm_ram...

I?m having a strange issue with nested routes though, and was wondering if anyone could shed some light on this? If I have: map.resources :users do |users| users.resources :items end When I try to call <%= link_to_remote ''Delete'', :url => item_url(@item), :with => "''_method=delete''", :confirm => ''Are you sure?''

I've splitted my big series between the part which actually fixes the engine reclocking bits and the part handling voltage/clock updates on temperature change, so that the more reviewed parts can be merged in faster. This series fixes a lot of Engine reclocking issues found on Fermi, Kepler and all Maxwell generation GPUs. It does _not_ fix memory reclocking on Fermi. It mostly contains of

From: Markus Elfring <elfring at users.sourceforge.net> Date: Wed, 21 Sep 2016 09:09:09 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (5): Use kmalloc_array() in nvbios_iccsense_parse() Use kmalloc_array() in gt215_link_train() Delete unnecessary braces Adjust a kzalloc() call in gt215_ram_new() Add space after an

...ch > looks like its caused by stack overflow or data corruption. > > question is; are there any clean way of reducing memory usage? > the stack at the end of the state object, is it only accessed > through the PUSH macros? perhaps I could write some wrappers > to use Program RAM (PRAM) instead, which is not directly accessible. > > > thanks. > > -- Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca> Universit? de Sherbrooke

In bulletpoints: - Add some support for G94 and G96 reclocking. Has been tested on literally two cards, which is hardly adequate as "full coverage". On the other hand, the changes were small enough to make me confident this might work for others as well. - Fix NV50 wait for VBLANK when no monitor is plugged in. - Voltage related inprovements for GT21x. - Slightly improve Keplers

...0228); + ram_wr32(fuc, mr[6], 0x00600228); ram_nsec(fuc, 1000); - ram_wr32(fuc, 0x10f348, 0x00700000); + ram_wr32(fuc, mr[7], 0x00700000); ram_wr32(fuc, 0x13d8f4, 0x00000000); ram_wr32(fuc, 0x61c140, 0x09a40000); @@ -706,11 +713,9 @@ gf100_ram_new(struct nvkm_fb *fb, struct nvkm_ram **pram) for (i = 0; i < 5; i++) ram->fuc.r_0x10f290[i] = ramfuc_reg(0x10f290 + (i * 4)); - ram->fuc.r_0x10f300 = ramfuc_reg(0x10f300); - ram->fuc.r_0x10f338 = ramfuc_reg(0x10f338); - ram->fuc.r_0x10f340 = ramfuc_reg(0x10f340); - ram->fuc.r_0x10f344 = ramfuc_reg(0x10f344); - ram-&g...

No, no, these will not implement Fermi reclocking. This set of patches contains some of the preparatory work that I deem stable enough to move upstream. Notable changes - Training pattern upload routines from GK104+ now shared with GT215+ - Timing calculation for Fermi - GDDR5 MR calculation from VBIOS timing table v1.0. Also useful for that pesky GT 240. - A routine to translate a VBIOS init

I need to check if a parameter is set so that I can build some information for my application, but No matter how I format my if statement in the file " Application.rb" it return the following error. You have a nil object when you didn''t expect it! You might have expected an instance of Array. The error occurred while evaluating nil.[] Here is the line if params[:day] So we

Two patches went missing as a result of PEBCAK. No v2 marks as nothing changed really. Just resending for easier enforcement of patch order in other people's trees. Sorry for the noise. Original message: No, no, these will not implement Fermi reclocking. This set of patches contains some of the preparatory work that I deem stable enough to move upstream. Notable changes - Training pattern