search for: dfp

...tion. I have 2 between subject variables and one within. I was able to change the data structure but still - the result of the aov functions are calculating everything as a within subject. the table looks like this: SerialNo breed treatment distance_1 distance_2 1 c57 dfp 235 3253 etc. I changed it to look like this: SerialNo breed treatment exposure distance 1 c57 dfp 1 235 1 c57 dfp 2 3253 etc. Then I do: dt<-aov(distance~(exposure*treatme...

...f other nvidia cards are affected. The following information from Xorg.0.log seems of interest: [ 130.447] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0 [ 130.447] (--) NVIDIA(0): CRT-0 [ 130.447] (--) NVIDIA(0): CRT-1 [ 130.447] (--) NVIDIA(0): DFP-0 (boot) [ 130.447] (--) NVIDIA(0): DFP-1 [ 130.447] (--) NVIDIA(0): DFP-2 [ 130.447] (--) NVIDIA(0): DFP-3 [ 130.448] (II) NVIDIA(0): NVIDIA GPU NVS 315 (GF119) at PCI:1:0:0 (GPU-0) [ 130.448] (--) NVIDIA(0): Memory: 1048576 kBytes [ 130.448] (--) NV...

...> The following information from Xorg.0.log seems of interest: > > [ 130.447] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0 > [ 130.447] (--) NVIDIA(0): CRT-0 > [ 130.447] (--) NVIDIA(0): CRT-1 > [ 130.447] (--) NVIDIA(0): DFP-0 (boot) > [ 130.447] (--) NVIDIA(0): DFP-1 > [ 130.447] (--) NVIDIA(0): DFP-2 > [ 130.447] (--) NVIDIA(0): DFP-3 > [ 130.448] (II) NVIDIA(0): NVIDIA GPU NVS 315 (GF119) at PCI:1:0:0 (GPU-0) > [ 130.448] (--) NVIDIA(0): Memory: 1048576 k...

...___init_error_handler (guestfs_h *g); diff --git a/src/handle.c b/src/handle.c index 39e30c7..8cf7a40 100644 --- a/src/handle.c +++ b/src/handle.c @@ -253,6 +253,9 @@ void guestfs_close (guestfs_h *g) { struct qemu_param *qp, *qp_next; +#ifndef HAVE_ATTRIBUTE_CLEANUP + struct deferred_free *dfp, *dfp_next; +#endif guestfs_h **gg; if (g->state == NO_HANDLE) { @@ -324,6 +327,18 @@ guestfs_close (guestfs_h *g) while (g->error_cb_stack) guestfs_pop_error_handler (g); +#ifndef HAVE_ATTRIBUTE_CLEANUP + /* For compilers that don't support __attribute__((cleanup(...))...

...ll blank, then come back for a bit, then blank for a few seconds then come back; lather, rinse, repeat. The Xorg log shows this: +++++++++++++++++++++++++ [ 239.338] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display [ 239.338] (**) NVIDIA(0): device DELL 7700 (DFP-1) (Using EDID frequencies has been [ 239.338] (**) NVIDIA(0): enabled on all display devices.) [ 239.344] (--) NVIDIA(GPU-0): DELL 7700 (DFP-1): connected [ 239.344] (--) NVIDIA(GPU-0): DELL 7700 (DFP-1): Internal TMDS [ 239.344] (--) NVIDIA(GPU-0): DELL 7700 (DFP-1): 165.0 MHz maximu...

...t; EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 Option "TwinView" "1" Option "TwinViewXineramaInfoOrder" "DFP-1" Option "metamodes" "CRT: nvidia-auto-select +0+0, DFP: nvidia-auto-$ SubSection "Display" Depth 24 Modes "2960x1050" "1680x1050" "1440x900" "1280x1024" EndSubSection EndSectio...

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/shader/Makefile | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/src/shader/Makefile b/src/shader/Makefile index 46658e9..2d789be 100644 --- a/src/shader/Makefile +++ b/src/shader/Makefile @@ -24,20 +24,21 @@ NVF0_SHADERS = xfrm2nvf0.vpc \ videonvf0.fpc SHADERS = $(NVC0_SHADERS)

...the dp.subconnector property will be valid in that case. > > > (Unfortunately I don't remember how one detects that particular > > > situation.) > > > > One may or may not be able to detect it very well. I've seen dongles > > that automagically change the DFP type from DP++ to DP/HDMI depending > > on what's plugged in, and I've also seen dongles that leave the DFP > > type to DP++. > > Well, our internal logic certainly knows if it's driving DP or TMDS. I > just don't remember how it knows this. You'll be driv...

...m Mc <efremmc2 at gmail.com> Date: Tue, 1 Mar 2016 00:27:52 -0500 > 'Normally, the monitor-edid, can report the options as well as the > journalctl -k on boot. I have a GTX 960, and it has a DVI-I, DVI-D, > DP 1.2, HDMI, and it names the ports as follows, DVI-I as > (DVI-I-1/DFP-0, DFP-1 (HDMI-1), DFP-2 (DVI-D-1/DFP-2), and for the > Display port (DP-1. In the X configuration, you can specify in > the device section, a BusID "PCI:2:0:0" for the GPU. There is > also an Identifier= "name", see /var/log/Xorg.0.log file. > > These are some...

...ectly into the DP++ port. I don't think > the dp.subconnector property will be valid in that case. > (Unfortunately I don't remember how one detects that particular > situation.) One may or may not be able to detect it very well. I've seen dongles that automagically change the DFP type from DP++ to DP/HDMI depending on what's plugged in, and I've also seen dongles that leave the DFP type to DP++. I'm actually broiling a series of patches which try to improve how i915 handles various DFP types, and for that I'm thinking of using a combination of the DFP type...

...length(weightexp[[1]])) for (i in 1:length(weightexp)) { sum = sum + weightexp[[i]] } expproppooled = sum/sum(weights) #Now the pooled G obs = tapply(obscounts,cov,sum) exp = expproppooled*sum(obs) Gp = 2*sum(obs*log(obs/exp)) dfp = max(as.integer(levels(cov)))-1 probp = pchisq(Gp, dfp, lower.tail=F) #total G Gt = sum(G) dft = sum(dfs) probt = pchisq(Gt, dft, lower.tail=F) #heterogeneity G Gh = Gt-Gp dfh = dft - dfp probh = pchisq(Gh, dfh, lower.tail=F)...

Dear helpers, FYI, I am a beginner of R, just have dealt with MATLAB or JAVA. I want to know how to solve one problem given 4 variables: year_1, year_2, tall_1, tall_2. The tall_1 is measured at year_1 and tall_2 at year_2. The tall has grown up such as uniformly 1 cm/yr. The data is like year_1 year_2 tall_1 tall_2 2007 2010 12 15 1999 2009 6 16 2003 2005 11 13

On Tue, Sep 08, 2020 at 02:34:24PM -0400, Lyude Paul wrote: > With the nitpicks addressed (note there were a couple of other spots where we > wanted to use Return: in the kdocs, but I didn't bother pointing all of them > out), all but patch 07 is: > > Reviewed-by: Lyude Paul <lyude at redhat.com> Thanks for the review. I fixed up the missing/bad docs and pushed the lot

...> > ok!! Taking a lesson from our available_pbn/full_pbn confusion in the past, I > squinted very hard at the specification and eventually found something that I > think clears this up. Surprise - we definitely had this implemented incorrectly > in i915 To me it looks correct, only DFP0's cap info is used, by also handling the DP_DETAILED_CAP_INFO_AVAILABLE=0/1 cases. The wording is a bit unclear, but as I understand the Standard only calls for the above: """ A DP upstream device shall read the capability from DPCD Addresses 00080h through 00083h. A DP Branch...

On Tue, Aug 11, 2020 at 04:04:50PM -0400, Lyude Paul wrote: > We're going to be doing the same probing process in nouveau for > determining downstream DP port capabilities, so let's deduplicate the > work by moving i915's code for handling this into a shared helper: > drm_dp_downstream_read_info(). > > Note that when we do this, we also do make some functional

...-12.1267954 -9.4267954 -7.4267954 -0.4267954 20.7903982 Coefficients: Estimate S.E. t Pr(T > |t|) (Intercept) 9.209602 4.760274 1.934679 0.08798892 R1 3.217194 2.548273 1.262500 0.24130121 Estimated Scale Parameter: 86.39367 "Phylogenetic" df (dfP): 10.24615 > # Second way, without the option data (so attaching the dataframe) > attach(mydata) > compar.gee(alt ~ R, family="gaussian", phy=mytree) [1] "Beginning Cgee S-function, @(#) geeformula.q 4.13 98/01/27" [1] "running glm to get initial regression est...

...full_pbn confusion in the past, > > I > > squinted very hard at the specification and eventually found something that > > I > > think clears this up. Surprise - we definitely had this implemented > > incorrectly > > in i915 > > To me it looks correct, only DFP0's cap info is used, by also handling > the DP_DETAILED_CAP_INFO_AVAILABLE=0/1 cases. Ended up realizing this right after I sent this version of the RFC - yeah, it definitely shouldn't be causing any real problems as of now > > The wording is a bit unclear, but as I understand th...

http://bugs.freedesktop.org/show_bug.cgi?id=27136 Summary: blank screen with G98 [Quadro NVS 420] (NV98) dual GPU, 4-head Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

...rty will be valid in that case. > > > > (Unfortunately I don't remember how one detects that particular > > > > situation.) > > > > > > One may or may not be able to detect it very well. I've seen dongles > > > that automagically change the DFP type from DP++ to DP/HDMI depending > > > on what's plugged in, and I've also seen dongles that leave the DFP > > > type to DP++. > > > > Well, our internal logic certainly knows if it's driving DP or TMDS. I > > just don't remember how it knows t...

...'m using wine 1.3.11 on gentoo and i'm having some problems As far as i understand, in order to stop games spanning on both of my monitors i have to add a metamode in xorg.conf. So i've edited my xorf.conf to: Code: Option "metamodes" "CRT: 1280x1024_75 +1920+0, DFP: 1920x1080_60 +0+0; DFP: 1920x1080_60 +0+0, CRT: NULL" This is fine for native linux games but wine has problems When i run a game in wine that's setup for fullscreen and 1920x1080 resolution, it switches like it should to the second metamode (DFP: 1920x1080_60 +0+0, CRT: NULL). But whe...