search for: rotates

Fix DRM_REFELCT_Y -> DRM_REFLECT_Y. Signed-off-by: Robert Foss <robert.foss at collabora.com> --- drivers/gpu/drm/drm_blend.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_blend.c b/drivers/gpu/drm/drm_blend.c index a0d0d6843288..dee67ef6c670 100644 --- a/drivers/gpu/drm/drm_blend.c +++ b/drivers/gpu/drm/drm_blend.c @@ -129,7 +129,7 @@ *

...10a37 100644 --- a/include/drm/drm_blend.h +++ b/include/drm/drm_blend.h @@ -25,31 +25,14 @@ #include <linux/list.h> #include <linux/ctype.h> +#include <drm/drm_mode.h> struct drm_device; struct drm_atomic_state; -/* - * Rotation property bits. DRM_ROTATE_<degrees> rotates the image by the - * specified amount in degrees in counter clockwise direction. DRM_REFLECT_X and - * DRM_REFLECT_Y reflects the image along the specified axis prior to rotation - * - * WARNING: These defines are UABI since they're exposed in the rotation - * property. - */ -#define DRM_ROTATE...

...10a37 100644 --- a/include/drm/drm_blend.h +++ b/include/drm/drm_blend.h @@ -25,31 +25,14 @@ #include <linux/list.h> #include <linux/ctype.h> +#include <drm/drm_mode.h> struct drm_device; struct drm_atomic_state; -/* - * Rotation property bits. DRM_ROTATE_<degrees> rotates the image by the - * specified amount in degrees in counter clockwise direction. DRM_REFLECT_X and - * DRM_REFLECT_Y reflects the image along the specified axis prior to rotation - * - * WARNING: These defines are UABI since they're exposed in the rotation - * property. - */ -#define DRM_ROTATE...

Ever since a recent power failure I have been getting a Logrotate error. My machine is on a UPS -- it shutdown cleanly, but I suspect that its BIOS/RTC battery is dead, since the machine came up thinking it was 1982 :-(. I reset the clock and everything is fine, *except* I had to delete Logrotate's state files (which had bad dates). But now Logrotate is raising the error: error: error

...e/drm/drm_blend.h > @@ -25,31 +25,14 @@ > > #include <linux/list.h> > #include <linux/ctype.h> > +#include <drm/drm_mode.h> > > struct drm_device; > struct drm_atomic_state; > > -/* > - * Rotation property bits. DRM_ROTATE_<degrees> rotates the image by the > - * specified amount in degrees in counter clockwise direction. DRM_REFLECT_X and > - * DRM_REFLECT_Y reflects the image along the specified axis prior to rotation > - * > - * WARNING: These defines are UABI since they're exposed in the rotation > - * property....

...e/drm/drm_blend.h > @@ -25,31 +25,14 @@ > > #include <linux/list.h> > #include <linux/ctype.h> > +#include <drm/drm_mode.h> > > struct drm_device; > struct drm_atomic_state; > > -/* > - * Rotation property bits. DRM_ROTATE_<degrees> rotates the image by the > - * specified amount in degrees in counter clockwise direction. DRM_REFLECT_X and > - * DRM_REFLECT_Y reflects the image along the specified axis prior to rotation > - * > - * WARNING: These defines are UABI since they're exposed in the rotation > - * property....

...e/drm/drm_blend.h > @@ -25,31 +25,14 @@ > > #include <linux/list.h> > #include <linux/ctype.h> > +#include <drm/drm_mode.h> > > struct drm_device; > struct drm_atomic_state; > > -/* > - * Rotation property bits. DRM_ROTATE_<degrees> rotates the image by the > - * specified amount in degrees in counter clockwise direction. DRM_REFLECT_X and > - * DRM_REFLECT_Y reflects the image along the specified axis prior to rotation > - * > - * WARNING: These defines are UABI since they're exposed in the rotation > - * property....

Hi everyone! I recently ran into some interesting issues with generation of rotate instructions - the details are in the bug tracker (https://bugs.llvm.org/show_bug.cgi?id=37387 and related bugs) for those interested - and it brought up the issue of rotates in the IR again. Now this is a proposal that has been made (and been rejected) several times, but I've been told that this time round we ran into issues not previously considered, and that I should bring the topic up on llvm-dev. I'll try to summarize the status quo first and then bring up...

...vm.org> wrote: > Hi everyone! > > I recently ran into some interesting issues with generation of rotate > instructions - the details are in the bug tracker ( > https://bugs.llvm.org/show_bug.cgi?id=37387 and related bugs) for those > interested - and it brought up the issue of rotates in the IR again. Now > this is a proposal that has been made (and been rejected) several times, > but I've been told that this time round we ran into issues not previously > considered, and that I should bring the topic up on llvm-dev. > > I'll try to summarize the status quo...

How does one rotate the loadings from a principal component analysis? Help on function prcomp() from package mva mentions rotation: Arguments retx a logical value indicating whether the rotated variables should be returned. Values rotation the matrix of variable loadings (i.e., a matrix whose olumns contain the eigenvectors). The function princomp returns this in the element

Hey guys, Got a quick question and I hope this is an easy one! In my /etc/logrotate.conf file I have the following entry: # rotate all of the apache logs -- we'll rotate them here /var/log/mysqld.log { weekly size 50M create 0644 mysql mysql rotate 1 } And from that I would expect the log to rotate when it reaches 50M in size. However I just caught that log weighing

Dear List, I am writing a custom panel function and xyplot method to plot the results of a procrustes analysis from the vegan package. I am having trouble getting the call to panel.arrows to work as I wish when conditioning. The attached file contains the function definitions for the xyplot method and the custom panel and prepanel functions I am using. This example, using data and functions from

Hello, I need to do a principal component analysis with EQUAMAX-rotation. Unfortunately the function principal() I use normally for PCA does not offer this rotation specification. I could find out that this might be possible somehow with the package GPArotation but until now I could not figure out how to use this in the principal component analysis. Maybe someone can give an example on how to do

Running fc3 with current cvs-head... Is there a nice way to rotate the /var/log/asterisk/messages file without shutting down asterisk? I'm currently rotating the log files via cron, however my script requires asterisk to be shut down, which also kills any outstanding cli sessions (eg, asterisk -rvvvvv). Would like to rotate the files without killing the cli session. Any reasonable way to

Dear List, I'm trying to draw vector in XYZ with rgl under use of a cylinder3d. Therefore I scale and rotate a basis-cylinder). However, somehow the rotation is wrong as verified by overplotting arrow3d(). Where is my mistake? library(heplots) library(rgl) # ... 2 vectors data=data.frame(row.names=c('X','Y','Z'), x1=c(2,1,5),y=c(4,3,2))

Dear all I'm unable to find an example of extracting the rotated scores of a principal components analysis. I can do this easily for the un-rotated version. data(mtcars) .PC <- princomp(~am+carb+cyl+disp+drat+gear+hp+mpg, cor=TRUE, data=mtcars) unclass(loadings(.PC)) # component loadings summary(.PC) # proportions of variance mtcars$PC1 <- .PC$scores[,1] # extract un-rotated scores of

NFC: Restructuring LoopRoration.cpp to create Loop Rotation Pass with Loop Rotation Utility Interface ============================================================================= Why this NFC change? ================= The existing LoopRotation.cpp is implemented as one of loop passes instead of being a utility. The user cannot easily perform the loop rotation selectively (or on demand) under

Hello again- Thanks to Prof. Ripley for responding to my previous question. I would like to clarify my question using sample code. I will use some sample code taken from ?prcomp Again, I would like to compare the % variance explained by each PC before and after rotation. < code follows > data(USArrests) pca = prcomp(USArrests, scale = TRUE) # proportion variance explained by each

...te instructions, at least x86, x86-64, ARM A32/T32 and AArch64 A64 agree that rotate distances are modulo the operand width. I believe PPC and MIPS do the same but am not sure (it's been a while), no clue about other architectures. It certainly seems the most natural way to define it, since rotates are cyclic to begin with. 8- and 16-bit rotates will need to be lowered into multi-instruction sequences on most targets (x86 and x86-64 can do them directly, but RISC-lineage archs usually don't have rotates at smaller than word size). Having explicit modulo semantics might end up forcing...

Hi, First of all I would like to say that I love the work you are doing. Xgl/compiz is a great project! I really appreciate what you are doing :) However, there is one feature that I'm missing, or rather the possibility to disable another feature. I would like to be able to use multiple viewports, but I don't want the rotation animation. Sure, rotating the desktop to switch viewport is