search for: vinfo

...v30_render *r, uint attrib, uint sem, uint *idx) > { > - struct pipe_screen *pscreen = &r->nv30->screen->base.base; > + struct nv30_screen *screen = r->nv30->screen; > struct nv30_fragprog *fp = r->nv30->fragprog.program; > struct vertex_info *vinfo = &r->vertex_info; > enum pipe_format format; > uint emit = EMIT_OMIT; > uint result = *idx; > > - if (sem == TGSI_SEMANTIC_GENERIC && result >= 8) { > - for (result = 0; result < 8; result++) { > - if (fp->texcoord[resul...

...*idx) >>> { >>> - struct pipe_screen *pscreen = &r->nv30->screen->base.base; >>> + struct nv30_screen *screen = r->nv30->screen; >>> struct nv30_fragprog *fp = r->nv30->fragprog.program; >>> struct vertex_info *vinfo = &r->vertex_info; >>> enum pipe_format format; >>> uint emit = EMIT_OMIT; >>> uint result = *idx; >>> - if (sem == TGSI_SEMANTIC_GENERIC && result >= 8) { >>> - for (result = 0; result < 8; result++) { &g...

Well...it's been a bit of a mixed bag.? Setting drm_kms_helper.drm_fbdev_overalloc=200 set the vinfo.yres_virtual to 2160 as opposed to 1080 (My monitor vertical resolution)? This fixed the mmap() problem.? However, it only worked on my main workstation.? My laptop running Intel graphics wasn't affected by the change in kernel cmdline.? My workstation is a custom build from a few years ago...

This makes the vertex buffer go to GART, not VRAM, and redoes the mapping to not use the UNSYNCHRONIZED access (which is meaningless on a VRAM buffer anyways). While we're at it, add some flushes for VBO data. Moving the vertex buffer from VRAM to GART makes glxgears work fully with NV30_SWTNL=1. The other changes just seem like a good idea. I'm not sure *why* moving the buffer from VRAM

This series of patches provides an ability to add VLANs to the bridge ports. This is similar to what can be found in most switches. The bridge port may have any number of VLANs added to it including vlan 0 priority tagged traffic. When vlans are added to the port, only traffic tagged with particular vlan will forwarded over this port. Additionally, vlan ids are added to FDB entries and become

...evelopment component which uses vorbis.dll, ogg.dll, vorbisenc.dll for encoding a file. When finishing a recording, the component runs these functions... ogg_stream_clear(OggSS); vorbis_block_clear(VBlock); vorbis_dsp_clear(Vdsp); vorbis_comment_clear(VComm); vorbis_info_clear(VInfo); I'm occasionally receiving a hang in the function vorbis_info_clear(vinfo) which goes to 100% CPU indefinitely. I've tried different compiles of vorbis.dll without success. I've checked the VInfo structure has valid information. Rather than trying to fix the problem, can I simply...

...ed in v4.12 and later kernels. > > Hope this helps, > > -ilia > > On Sun, Jul 5, 2020 at 7:02 PM Michael T. Kloos > <michael at michaelkloos.com> wrote: >> Well...it's been a bit of a mixed bag. Setting >> drm_kms_helper.drm_fbdev_overalloc=200 set the vinfo.yres_virtual to >> 2160 as opposed to 1080 (My monitor vertical resolution) This fixed the >> mmap() problem. However, it only worked on my main workstation. My >> laptop running Intel graphics wasn't affected by the change in kernel >> cmdline. My workstation is a c...

...EL 3 to build llvm 2.2. Below are the build errors: /home/i00171/Work/llvm-work/src/llvm-2.2/include/llvm/Analysis/DominatorInternals.h:147: no type named `NodeType' in `class llvm::BasicBlock' /home/i00171/Work/llvm-work/src/llvm-2.2/include/llvm/Analysis/DominatorInternals.h:150: ` VInfo' undeclared (first use this function) /home/i00171/Work/llvm-work/src/llvm-2.2/include/llvm/Analysis/DominatorInternals.h:152: no matching function for call to `Compress( llvm::DominatorTreeBase<llvm::BasicBlock>&, llvm::BasicBlock*&)' TIA, Sanjiv -------------- next p...

...ommit 5f15257689bfa, which is included in v4.12 and later kernels. Hope this helps, -ilia On Sun, Jul 5, 2020 at 7:02 PM Michael T. Kloos <michael at michaelkloos.com> wrote: > > Well...it's been a bit of a mixed bag. Setting > drm_kms_helper.drm_fbdev_overalloc=200 set the vinfo.yres_virtual to > 2160 as opposed to 1080 (My monitor vertical resolution) This fixed the > mmap() problem. However, it only worked on my main workstation. My > laptop running Intel graphics wasn't affected by the change in kernel > cmdline. My workstation is a custom build from...

Changes since v9: * series re-ordering so make functionality more distinct. Basic vlan filtering is patches 1-4. Support for PVID/untagged vlans is patches 5 and 6. VLAN support for FDB/MDB is patches 7-11. Patch 12 is still additional egress policy. * Slight simplification to code that extracts the VID from skb. Since we now depend on the vlan module, at the time of input skb_tci is

<div dir='auto'>I am not familiar with that setting, but I have really struggled to find documentation on dealing with the framebuffer. Referring to this guide, "http://betteros.org/tut/graphics1.php#doublebuffer", I attempted to set the mmap allocation size to double, but it caused the mmap to fail. I no longer believe that it is a driver issue, though, because I just

...e the build errors: > > /home/i00171/Work/llvm-work/src/llvm-2.2/include/llvm/Analysis/DominatorInternals.h:147: > no > type named `NodeType' in `class llvm::BasicBlock' > /home/i00171/Work/llvm-work/src/llvm-2.2/include/llvm/Analysis/DominatorInternals.h:150: > ` > VInfo' undeclared (first use this function) > /home/i00171/Work/llvm-work/src/llvm-2.2/include/llvm/Analysis/DominatorInternals.h:152: > no > matching function for call to `Compress( > llvm::DominatorTreeBase<llvm::BasicBlock>&, llvm::BasicBlock*&)' That is a very s...

I have played a bit with RSpec specs and now want to check out stories. I note that there is no generator for rspec stories pre se (unless I managed to miss all references to one ) and that the only directory relating to stories added by installing rspec is ./stories itself. The documentation at rspec.info seems to presume a great deal of prior knowledge. What I am looking for is a guided tour

.....} svinst, pointer to struct sieve_error_handler {..} parent, unsigned int max_errors, unsigned int errors, unsigned int warnings, _Bool log_info, _Bool log_debug, pointer to function(..) returning void verror, pointer to function(..) returning void vwarning, pointer to function(..) returning void vinfo, pointer to function(..) returning void vdebug, pointer to function(..) returning void free}, unsigned int, _Bool) returning _Bool previous: function(pointer to struct sieve_multiscript {pointer to struct sieve_instance {..} svinst, pointer to struct sieve_result {..} result, pointer to const stru...

Hi I am working with spgrass6 package and GRASS v.6.2. Everything was fine until I tryed to read a vector file with readVECT6 (and other related vector commands, like vInfo). When I ran these commands, the problem immediately appeared (" Sorry, is not a valid flag" ). Ok, the solution is easy: - You have to download the spgrass package within a folder, in order to install the package from this directory. You should type (being in R) > download.p...

...00171/Work/llvm-work/src/llvm-2.2 > /include/llvm/Analysis/DominatorInternals.h:147: > > no > > type named `NodeType' in `class llvm::BasicBlock' > > /home/i00171/Work/llvm-work/src/llvm-2.2 > /include/llvm/Analysis/DominatorInternals.h:150: > > ` > > VInfo' undeclared (first use this function) > > /home/i00171/Work/llvm-work/src/llvm-2.2 > /include/llvm/Analysis/DominatorInternals.h:152: > > no > > matching function for call to `Compress( > > llvm::DominatorTreeBase<llvm::BasicBlock>&, llvm::BasicBlock*&am...

...5.4. This process was not satisfactory. While the update packages all downloaded without problem the update process itself stalled at several points. By stalled I mean that at some point the entire process stopped for hours. The packages at which it stalled included evince, evolution, totem and vinfo. There may have been others but these I seem to recall. Restarting the update process required that the existing update be interrupted with a <ctrl>C and yum-complete-transaction run. It took five iterations to get through to completion and in the end I first installed all the remaining pa...

...Why is the node memsize > total_memory? Mmm... Interesting question. I really never paid attention to this... Jan (or anyone else), is that something known and/or expected? I went checking this down in Xen, and here''s what I found. total_memory is: info.total_pages/((1 << 20) / vinfo->pagesize) where ''info'' is what libxl_get_physinfo() provides. On its turn, libxl_get_physinfo() is xc_physinfo(), which is XEN_SYSCTL_physinfo, which uses total_pages, which is assigned the number of pages, down in __start_xen(), as it results from parsing the E820 map (looki...

I haven't done any R memory debugging lately, but https://www.mail-archive.com/rcpp-devel at lists.r-forge.r-project.org/msg10289.html shows how I used to have gdb break where valgrind finds a problem so you could examine the details. Also, running your code after running gctorture(TRUE) can help track down memory problems. -Bill On Wed, Feb 7, 2024 at 12:03?PM Therneau, Terry M., Ph.D.