search for: 2048x1536

...produce just motion JPEG utilizing 97% of the resources. The new (model 333) camera uses 3 times bigger FPGA (and also faster), it also has increased frame buffer and system memory. I've already ported old code to the new camera, it can produce motion JPEG at 1280x1024@30fps (1600x1200@20 fps, 2048x1536@12fps) and uses only 1/3 of the FPGA. So now I'm ready to start working on video compression (probably no motion compensation at first). Considering Ogg Theora format I've got a couple questions I could not find answers to: 1 - Legal stuff. Is it legal to implement VP3-related coding algor...

...produce just motion JPEG utilizing 97% of the resources. The new (model 333) camera uses 3 times bigger FPGA (and also faster), it also has increased frame buffer and system memory. I've already ported old code to the new camera, it can produce motion JPEG at 1280x1024@30fps (1600x1200@20 fps, 2048x1536@12fps) and uses only 1/3 of the FPGA. So now I'm ready to start working on video compression (probably no motion compensation at first). Considering Ogg Theora format I've got a couple questions I could not find answers to: 1 - Legal stuff. Is it legal to implement VP3-related coding algor...

Does anyone have any experience with the combination of a Thinkpad R40 and the ATI Radeon Mobility M6 LY video chip? I''ve had CentOS 4.1, 4.2, and now 4.3 running just great with 1024x768 resolution, but according the IBM specs, this chip is capable of 1280x1024. A quick lspci -v | grep ATI spewed the following: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility

...isplay" Depth 24 Modes "1280x1024" #"1024x768" "800x600" "640x480" Virtual 2048 1536 ViewPort 0 0 EndSubsection [...] Note the `Virtual' line. The end result was a pannable desktop at size 2048x1536 I haven't been able to figure out how to get that to work in a current xorg.conf created by: `Xorg -configure' (in console mode). I have inlined an attempted xorg.conf, that seems to work so far as X being usable but fails to provide the virtual size. (the xorg.conf is inlined following X...

...280x1024 TvTime only shows the top left, it seems to 1280x1024, the rest is blue. If I see Tvtime in small window in the upper left is well, if I put the window in the lower right corner is all blue. The gdm starts with a resolution of 1280x1024, with nv boots to the maximum resolution of monitor, 2048x1536. The screen displayed a line of vertical pixel roses on the right side and a more thin at the bottom. Tvtime does not show any error. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug,...

...adapter for CRT and specifying supported "PreferredMode" >EDID preferred mode, screen output is compressed into small fraction of top scan lines To reproduce: 1-connect DVI-I out from NVidia PCI express card (G84 here with only dual DVI out; DVI-I-1 connected) to CRT supporting up to 2048x1536 but with 1600x1200 preferred (NEC FE2111SB here) via PCI to VGA adapter 2-set 'Option "PreferredMode" "1920x1440"' in 'Section "Monitor"' in /etc/X11/xorg.conf* 3-start X server Actual results: 1-entirety of video output displays into top scan lines, a...

...+ 50.00 59.94 59.97 30.00 25.00 24.00 29.97 23.98 4096x2160 60.00 50.00 59.94 30.00 25.00 24.00 29.97 23.98 3200x1800 59.96 59.94 2880x1620 59.96 59.97 2560x1600 59.99 59.97 2560x1440 59.99 59.96 59.95 2048x1536 85.00 75.00 60.00 1920x1440 85.00 75.00 60.00 1856x1392 75.00 60.01 1792x1344 75.00 60.01 2048x1152 59.99 59.98 59.90 59.91 1920x1200 59.88 59.95 1920x1080 60.01 120.00 100.00 119.88 59.97 59.96 60.00...

...uot;700x525" (vrefresh out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "1920x1440" (vrefresh out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "960x720" (vrefresh out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "2048x1536" (hsync out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "1024x768" (hsync out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "2048x1536" (vrefresh out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "1024x768"...

I think I may have updated the tv firmware between when it worked and when it didn't. I wonder it it has to do with bit depth. I use lubuntu and it doesn't let me pick the bit depth so I don't know what it using.

...f range) (II) NOUVEAU(0): Not using default mode "960x720" (hsync out of range) (II) NOUVEAU(0): Not using default mode "1920x1440" (hsync out of range) (II) NOUVEAU(0): Not using default mode "960x720" (hsync out of range) (II) NOUVEAU(0): Not using default mode "2048x1536" (hsync out of range) (II) NOUVEAU(0): Not using default mode "1024x768" (hsync out of range) (II) NOUVEAU(0): Not using default mode "2048x1536" (hsync out of range) (II) NOUVEAU(0): Not using default mode "1024x768" (hsync out of range) (II) NOUVEAU(0): Printing...

...## VIA reference file modes are marked "Extra mode" in this list. ## All have been renamed to include refresh rate and not conflict ## with the standard VESA names (most are VESA standard rates). ## Refresh rate 60Hz - The prefered LCD refresh rate. # Default mode "2048x1536": 266.9 MHz, 95.3 kHz, 60.0 Hz Modeline "2048x1536-60.0" 266.95 2048 2200 2424 2800 1536 1537 1540 1589 -hsync +vsync # Default mode "1920x1440": 234.0 MHz, 90.0 kHz, 60.0 Hz Modeline "1920x1440-60.0" 234.00 1920 2048 2256 2600 1440 1441 1444 150...

...II) S3VIRGE(0): Not using default mode "960x600" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "960x720" (hsync out of range) (II) S3VIRGE(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1024x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1024x768" (insufficient me...

...## VIA reference file modes are marked "Extra mode" in this list. ## All have been renamed to include refresh rate and not conflict ## with the standard VESA names (most are VESA standard rates). ## Refresh rate 60Hz - The prefered LCD refresh rate. # Default mode "2048x1536": 266.9 MHz, 95.3 kHz, 60.0 Hz Modeline "2048x1536-60.0" 266.95 2048 2200 2424 2800 1536 1537 1540 1589 -hsync +vsync # Default mode "1920x1440": 234.0 MHz, 90.0 kHz, 60.0 Hz Modeline "1920x1440-60.0" 234.00 1920 2048 2256 2600 1440 1441 1444 150...

...ult mode "960x600" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1920x1440" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "2048x1536" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "2048x1536" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "1024x768" (bad mode clock/i...

https://bugs.freedesktop.org/show_bug.cgi?id=90682 Bug ID: 90682 Summary: failed to idle channel 0xcccc0001 then crash Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee:

...ERROR - Ch 2/7 Mthd 0x1e94 Data 0x00000013 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 1 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on vga encoder (output 0) May 1 09:46:31 lithium kernel: [drm] DAC-7: set mode 2048x1536 42 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0) May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: Output VGA-1 is running on CRTC 0 using output A I then booted into a different kernel, put back the Nvidia orignal driver, tried...

...ult mode "800x512" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1920x1440" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "2048x1536" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "2048x1536" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "1024x768" (bad mode clock/i...

..."960x600" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1920x1440" (height too large for virtual size) (II) NOUVEAU(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "2048x1536" (width too large for virtual size) (II) NOUVEAU(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "2048x1536" (width too large for virtual size) (II) NOUVEAU(0): Not using default mode "1024x768" (...

...VTotal : 722, 756 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: PixelClock (170.7 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "2048x1536": (II) NVIDIA(0): 2048 x 1536 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 266.950 MHz (II) NVIDIA(0): HRes, HSyncStart : 2048, 2200 (II) NVIDIA(0): HSyncEnd, HTotal : 2424, 2800 (II) NVIDIA(0): VRes, VSyncStart : 1536, 1537 (...

...0x600" (hsync out of range) [ 8.615] (II) NOUVEAU(0): Not using default mode "1920x1440" (height too large for virtual size) [ 8.615] (II) NOUVEAU(0): Not using default mode "960x720" (vrefresh out of range) [ 8.615] (II) NOUVEAU(0): Not using default mode "2048x1536" (height too large for virtual size) [ 8.615] (II) NOUVEAU(0): Not using default mode "1024x768" (hsync out of range) [ 8.615] (II) NOUVEAU(0): Not using default mode "2048x1536" (height too large for virtual size) [ 8.615] (II) NOUVEAU(0): Not using default mod...