search for: 225000

...4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #11: Sun Aug 31 14:17:04 CEST 2003 root@freebie.xs4all.nl:/usr/obj/usr/src/sys/FREEBIE i386 and a recent mbmon build: xmbmon-203 I'm now getting interesting results: wkb@freebie ~: mbmon Temp.= 255.0, 240.0, 255.0; Rot.= 11250, 270000, 225000 Vcore = 1.52, 3.15; Volt. = 3.20, 5.08, 15.50, -0.00, -0.00 Temp.= 255.0, 240.0, 255.0; Rot.= 11250, 270000, 225000 Vcore = 1.57, 3.20; Volt. = 3.20, 5.05, 15.50, -0.00, -0.00 ^C wkb@freebie ~: I'm pretty sure it is the port that has problems, but I'm curious if others have seen this t...

Hi, I was trying to stack a topographic map readed in from esri shapefile with a contour map and a vector map. However, the plotMap(maptools) and contourplot(lattice) do not seem to work well on top of each other. Here is part of my code. xrange<-range(225000:350000) yrange<-range(2685000:2810000) basemap <- read.shape("Twn25_town_dxf_Polygon.shp") plot.Map(basemap,xlim=xrange,ylim=yrange,fg=0,ol=8,xlab="",ylab="") contourplot(var1.pred~x+y, spcgrid, aspect = "xy",label.style=&q...

From: Hauke Mehrtens <hauke at hauke-m.de> Without this patch a pixel clock rate above 165 MHz on a TMDS link is assumed to be dual link. This is true for DVI, but not for HDMI. HDMI supports no dual link, but it supports pixel clock rates above 165 MHz. Only activate Dual Link mode when it is actually possible and requested. Signed-off-by: Hauke Mehrtens <hauke at hauke-m.de>

From: Hauke Mehrtens <hauke at hauke-m.de> Without this patch a pixel clock rate above 165 MHz on a TMDS link is assumed to be dual link. This is true for DVI, but not for HDMI. HDMI supports no dual link, but it supports pixel clock rates above 165 MHz. Only activate Dual Link mode when it is actually possible and requested. Signed-off-by: Hauke Mehrtens <hauke at hauke-m.de>

...rivers/gpu/drm/gma500/cdv_intel_display.c index 6126546..17db4b4 100644 --- a/drivers/gpu/drm/gma500/cdv_intel_display.c +++ b/drivers/gpu/drm/gma500/cdv_intel_display.c @@ -116,7 +116,7 @@ static const struct gma_limit_t cdv_intel_limits[] = { .p1 = {.min = 1, .max = 10}, .p2 = {.dot_limit = 225000, .p2_slow = 10, .p2_fast = 10}, .find_pll = cdv_intel_find_dp_pll, - } + } }; #define _wait_for(COND, MS, W) ({ \ @@ -245,7 +245,7 @@ cdv_dpll_set_clock_cdv(struct drm_device *dev, struct drm_crtc *crtc, /* We don't know what the other fields of these regs are, so * leave them in...

...ug info Name (120 modules) ELF 120000- 125000 Deferred libxfixes.so.3 ELF 127000- 13c000 Deferred libresolv.so.2 ELF 13e000- 16d000 Deferred libgssapi_krb5.so.2 ELF 19f000- 1a2000 Deferred libcom_err.so.2 ELF 21b000- 223000 Deferred libsm.so.6 ELF 225000- 23f000 Deferred libice.so.6 ELF 248000- 24b000 Deferred libkeyutils.so.1 ELF 262000- 280000 Deferred ld-linux.so.2 ELF 282000- 3eb000 Export libc.so.6 PE 330000- 34e000 Deferred lua502 PE 350000- 363000 Deferred tinyxml234 PE 370000- 3...

These patches are adding support for outputting 2560x1440 at 56 over HDMI. This needs a pixel clock of 225 MHz which was not supported before. This was tested in a dual monitor setup with a GF114 (GTX 560 TI) and one HDMI monitor running with 2560x1440 at 56 and one DVI monitor running with 1920x1200 at 60. This still needs testing on other graphics cards and with dual link DVI. There is no

These patches are adding support for outputting 2560x1440 at 56 over HDMI. This needs a pixel clock of 225 MHz which was not supported before. This was tested in a dual monitor setup with a GF114 (GTX 560 TI) and one HDMI monitor running with 2560x1440 at 56 and one DVI monitor running with 1920x1200 at 60. This still needs testing on other graphics cards and with dual link DVI. There is no

From: Hauke Mehrtens <hauke at hauke-m.de> Without this patch a pixel clock rate above 165 MHz on a TMDS link is assumed to be dual link. This is true for DVI, but not for HDMI. HDMI supports no dual link, but it supports pixel clock rates above 165 MHz. Only activate Dual Link mode when it is actual possible. Signed-off-by: Hauke Mehrtens <hauke at hauke-m.de> Signed-off-by: Ilia

...0 0 0 0 [28,] 0 0 0 0 [29,] 0 0 0 0 [30,] 0 0 0 0 [31,] 0 0 0 0 [32,] 0 0 0 0 [33,] 0 0 225000 0 [34,] 0 0 0 0 > While I can construct splines in a similar manner to what I did for my first output, I am unable to figure out how to construct mars splines for the pairwise interactions I am supposed to be getting for degree=2. The mars documentati...

This patch set nukes all the dummy crtc mode_fixup implementations. (made on top of Daniel topic/drm-misc branch) Carlos Palminha (16): drm: fixes crct set_mode when crtc mode_fixup is null. drm/cirrus: removed optional dummy crtc mode_fixup function. drm/mgag200: removed optional dummy crtc mode_fixup function. drm/udl: removed optional dummy crtc mode_fixup function. drm/gma: removed

This patch set nukes all the dummy crtc mode_fixup implementations. (made on top of Daniel topic/drm-misc branch) Carlos Palminha (16): drm: fixes crct set_mode when crtc mode_fixup is null. drm/cirrus: removed optional dummy crtc mode_fixup function. drm/mgag200: removed optional dummy crtc mode_fixup function. drm/udl: removed optional dummy crtc mode_fixup function. drm/gma: removed

...ed mean (2 extremes eliminated): ", = mean(times[2:4, 2]), "\n\n")) cat(" III. Programmation\n") cat(" ------------------\n") flush.console() # (1) cumulate <- 0; a <- 0; b <- 0; phi <- 1.6180339887498949 for (i in 1:runs) { a <- floor(runif(225000, max=3D1000)) timing <- system.time({ b <- (phi^a - (-phi)^(-a))/sqrt(5) })[3] cumulate <- cumulate + timing } timing <- cumulate/runs times[1, 3] <- timing cat(c("225,000 Fibonacci numbers calculation (vector calc)_ (sec): ", = timing, "\n")) remove(&qu...

This is problem 1 of 3 problems we are having with live migration and/or ACPI on Xen-4.3 and Xen-4.2. Any help would be appreciated. Detailed description of problem: We are using Xen-4.3-rc1 with dom0 running Ubuntu Precise and 3.5.0-23-generic kernel, and domU running Ubuntu Precise (12.04) cloud images running 3.2.0-39-virtual. We are using the xl.conf below on qemu-upstream-dm and HVM and

...<c10b0303>] ? __schedule_bug+0x13/0x60 [ 21.851111] [<c15c29f7>] ret_from_kernel_thread+0x1b/0x28 [ 21.851111] [<c10a4bd0>] ? kthread_freezable_should_stop+0x60/0x60 [ 21.851111] CE: xen increased min_delta_ns to 150000 nsec [ 21.851111] CE: xen increased min_delta_ns to 225000 nsec [ 21.851111] CE: xen increased min_delta_ns to 337500 nsec [ 21.851111] CE: xen increased min_delta_ns to 506250 nsec [ 21.851111] CE: xen increased min_delta_ns to 759375 nsec [ 21.851111] CE: xen increased min_delta_ns to 1000000 nsec [ 21.851111] CE: Reprogramming failure. Giving...