search for: modifi

Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() family of modifiers to handle broken userspace Xorg modesetting and Mesa drivers. Existing Mesa drivers are still aware of only these older format modifiers which do not differentiate between different variations of the block linear layout. When the format modifier support flag was flipped in the nouveau kernel dri...

Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() family of modifiers to handle broken userspace Xorg modesetting and Mesa drivers. Existing Mesa drivers are still aware of only these older format modifiers which do not differentiate between different variations of the block linear layout. When the format modifier support flag was flipped in the nouveau kernel dri...

On 7/23/20 9:06 PM, Ben Skeggs wrote: > On Sat, 18 Jul 2020 at 13:34, James Jones <jajones at nvidia.com> wrote: >> >> Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() >> family of modifiers to handle broken userspace >> Xorg modesetting and Mesa drivers. Existing Mesa >> drivers are still aware of only these older >> format modifiers which do not differentiate >> between different variations of the block linear >> layout. When the format modifier suppo...

I've been unable to bootstrap llvm-gcc-4.0 or -4.2 for x86_64 for some weeks now. The current problem is this: [x86_64-mod-dbg]: ./xgcc -B./ -B/install.modified.debug/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/bin/ -isystem /install.modified.debug/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/include -isystem /install.modified.debug/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sys-include -L/tmp/ptmp/dag/build.llvm-gcc-4.0.modified.deb...

...;jajones at nvidia.com> wrote: > > > > On 7/23/20 9:06 PM, Ben Skeggs wrote: > > > On Sat, 18 Jul 2020 at 13:34, James Jones <jajones at nvidia.com> wrote: > > >> > > >> Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() > > >> family of modifiers to handle broken userspace > > >> Xorg modesetting and Mesa drivers. Existing Mesa > > >> drivers are still aware of only these older > > >> format modifiers which do not differentiate > > >> between different variations of the block linear > &g...

...lib64/libltdl.so.3.1.0 /usr/lib64/libltdl.so.3.1.0 Is this a known problem? I'm not very familiar with how libtools works so I'm a bit hesitant to hack up ltmain.sh. -Dave llvm[2]: Linking Debug+Checks executable tblgen /tmp/ptmp/dag/build.llvm.modified.debug/mklib --tag=CXX --tag=disable-shared --mode=link /tools/llvm-tools/x86_64-unknown-linux-gnu/bin/g++ -I/tmp/ptmp/dag/build.llvm.modified.debug/utils/TableGen -I/users/dag/projects/llvm-project.modified/llvm/trunk/utils/TableGen -I/tmp/ptmp/dag/build.llvm.modified.debug/include -I/users...

Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() family of modifiers to handle broken userspace Xorg modesetting and Mesa drivers. Existing Mesa drivers are still aware of only these older format modifiers which do not differentiate between different variations of the block linear layout. When the format modifier support flag was flipped in the nouveau kernel dri...

On Sat, 18 Jul 2020 at 13:34, James Jones <jajones at nvidia.com> wrote: > > Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() > family of modifiers to handle broken userspace > Xorg modesetting and Mesa drivers. Existing Mesa > drivers are still aware of only these older > format modifiers which do not differentiate > between different variations of the block linear > layout. When the format modifier support flag was > fli...

I am trying to install Rcmdr on my ubuntu machine, but keep getting the following error messages: ERROR: failed to lock directory ?/home/thedoctor/R/i486-pc-linux-gnu-library/2.10? for modifying Try removing ?/home/thedoctor/R/i486-pc-linux-gnu-library/2.10/00LOCK? ERROR: failed to lock directory ?/home/thedoctor/R/i486-pc-linux-gnu-library/2.10? for modifying Try removing

On Oct 8, 2007, at 12:50 PM, David Greene wrote: > I've been unable to bootstrap llvm-gcc-4.0 or -4.2 for x86_64 > for some weeks now. The current problem is this: > > [x86_64-mod-dbg]: ./xgcc -B./ > -B/install.modified.debug/x86_64-unknown-linux-gnu/x86_64-unknown- > linux-gnu/bin/ > -isystem /install.modified.debug/x86_64-unknown-linux-gnu/x86_64- > unknown-linux-gnu/include > -isystem /install.modified.debug/x86_64-unknown-linux-gnu/x86_64- > unknown-linux-gnu/sys-include > -L/tmp/ptmp/da...

On Thu, Jul 30, 2020 at 10:26:17AM -0700, James Jones wrote: > Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() > family of modifiers to handle broken userspace > Xorg modesetting and Mesa drivers. Existing Mesa > drivers are still aware of only these older > format modifiers which do not differentiate > between different variations of the block linear > layout. When the format modifier support flag was > fli...

...2020 at 04:51, James Jones <jajones at nvidia.com> wrote: > > On 7/23/20 9:06 PM, Ben Skeggs wrote: > > On Sat, 18 Jul 2020 at 13:34, James Jones <jajones at nvidia.com> wrote: > >> > >> Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() > >> family of modifiers to handle broken userspace > >> Xorg modesetting and Mesa drivers. Existing Mesa > >> drivers are still aware of only these older > >> format modifiers which do not differentiate > >> between different variations of the block linear > >> layout. When...

...te: > > > > > > On 7/23/20 9:06 PM, Ben Skeggs wrote: > > > > On Sat, 18 Jul 2020 at 13:34, James Jones <jajones at nvidia.com> wrote: > > > >> > > > >> Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() > > > >> family of modifiers to handle broken userspace > > > >> Xorg modesetting and Mesa drivers. Existing Mesa > > > >> drivers are still aware of only these older > > > >> format modifiers which do not differentiate > > > >> between different variations of the...

...ion, modify.levels <- function(f, modify=list()){ ## levels that will not be changed names.old.levels <- setdiff(levels(f), unlist(modify)) ## as a named list old.levels <- as.pairlist(names.old.levels) names(old.levels) <- names.old.levels ## union of unchanged levels and modified ones levels(f) <- modifyList(old.levels, modify) f } f <- factor(LETTERS[1:4]) f2 <- modify.levels(f, list(aa = "A", cc="C")) It seems to work, but the original order of the levels is changed. Have I missed a better way of doing this manipulation? Best regards...

On 1/21/2013 2:01 AM, Óscar Fuentes wrote: > Ashok Nalkund <ashoknn at qti.qualcomm.com> writes: > >> I was using the find_package(LLVM llvm/share/llvm/cmake) and >> llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) to get >> the libraries to link against. This works well for the libLLVM* >> libraries, but how do I implement similar find stuff for

...se file a bugzilla report. Evan, are you "3 addrifying" 32-bit adds into a 32-bit LEA on x86-64? Could this be the problem? (iirc, it wants you to use eax = LEA rsi, rdi) -Chris >> I also see warnings like this: >> >> [x86_64-mod-dbg]: ./xgcc -B./ >> -B/install.modified.debug/x86_64-unknown-linux-gnu/x86_64-unknown- >> linux-gnu/bin/ >> -isystem /install.modified.debug/x86_64-unknown-linux-gnu/x86_64- >> unknown-linux-gnu/include >> -isystem /install.modified.debug/x86_64-unknown-linux-gnu/x86_64- >> unknown-linux-gnu/sys-include &g...

On 7/17/20 12:47 PM, Daniel Vetter wrote: > On Fri, Jul 17, 2020 at 11:57:57AM -0700, James Jones wrote: >> Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() >> family of modifiers to handle broken userspace >> Xorg modesetting and Mesa drivers. >> >> Tested with Xorg 1.20 modesetting driver, >> weston at c46c70dac84a4b3030cd05b380f9f410536690fc, >> gnome & KDE wayland desktops from Ubuntu 18.04, >> and sway 1.5 > > Just bikes...

...e should have "executable" code? Is it also true that "outside" .First.lib, only function declarations and objects assignments such as '.conflicts.OK <- TRUE' should be used? Q2. Is it considered ok to use attr() outside .First.lib? I would like set an attribute 'modifiers' to all my functions as they are declared. I have tried it and it work. This is an example of how one of my generated package files looks like: callMe0 <- function(x) cat("hey\n") attr(callMe0, "modifiers") <- c("private") callMe <- function...

On Wed, Dec 11, 2019 at 4:04 PM James Jones <jajones at nvidia.com> wrote: > > Allow setting the block layout of a nouveau FB > object using DRM format modifiers. When > specified, the format modifier block layout and > kind overrides the GEM buffer's implicit layout > and kind. The specified format modifier is > validated against he list of modifiers supported > by the target display hardware. > > Signed-off-by: James Jones &l...

...;between the caller and the callee" part. The way I see this, the responsibility for the copying should be with either the caller or the callee, not somewhere in between. In particular, I think byval could either mean: a) The callee is not allowed to modify the argument. If the original code modifies the argument, the callee should make a copy and modify that instead. b) The caller will always pass in a copy of the object, which the callee is free to modify and will be thrown away afterwards. In both cases, it seems that byval argument must always be a valid pointer. From the code, I sus...