search for: framebuffers

? ? Hello ? I need urgent help : ? In my previous system configuration with ubuntu 10.04 the program phase-6 ( a learning program for vocabulary) ran without problems under wine. ? Today a did an upgrade to ubuntu 10.10 with wine 1.3.12. ? Since the upgrade the program phase-6 can't open his window and nothing happens (only the registration of the license is working). I tried some

Shutdown of firmware framebuffer has a bunch of problems. Because of this the framebuffer region might still be reserved even after drm_fb_helper_remove_conflicting_pci_framebuffers() returned. Don't consider pci_request_region() failure for the framebuffer region as fatal error to workaround this issue. Reported-by: Marek Marczykowski-G?recki <marmarek at invisiblethingslab.com> Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/bochs/b...

Shutdown of firmware framebuffer has a bunch of problems. Because of this the framebuffer region might still be reserved even after drm_fb_helper_remove_conflicting_pci_framebuffers() returned. Don't consider pci_request_region() failure for the framebuffer region as fatal error to workaround this issue. Reported-by: Marek Marczykowski-G?recki <marmarek at invisiblethingslab.com> Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/bochs/b...

I'm still using CentOS 4.6, but have been planning an upgrade to CentOS 5 for quite a while. One of the things that was holding me back is that the CentOS 5.0 kernel did not have the framebuffer support enabled by default. So I waited for CentOS 5.1. However, on one of my test systems I ran into the bad NFS performance issue (see CentOS bug 2635), so I plan to use the centosplus

It is worthwhile, when designing virtio, to keep in mind as many possible users as possible. In addition to block and net, I see at least the following: - vmgl (paravirtualized 3D graphics) [http://www.cs.toronto.edu/~andreslc/xen-gl/] - scsi (for tape, cd writer, etc.) - framebuffer (with just one request to share the framebuffer?) There are probably more. Any ideas? -- error compiling

It is worthwhile, when designing virtio, to keep in mind as many possible users as possible. In addition to block and net, I see at least the following: - vmgl (paravirtualized 3D graphics) [http://www.cs.toronto.edu/~andreslc/xen-gl/] - scsi (for tape, cd writer, etc.) - framebuffer (with just one request to share the framebuffer?) There are probably more. Any ideas? -- error compiling

It is worthwhile, when designing virtio, to keep in mind as many possible users as possible. In addition to block and net, I see at least the following: - vmgl (paravirtualized 3D graphics) [http://www.cs.toronto.edu/~andreslc/xen-gl/] - scsi (for tape, cd writer, etc.) - framebuffer (with just one request to share the framebuffer?) There are probably more. Any ideas? -- error compiling

Greetings! I have installed xen-4.0 with kernel 2.6.32 on a gentoo box. Everything works perfectly, except one tiny detail. I do not have X installed on the machine, so I configured the (old, non-xen) kernel to use a framebuffer, so that I don''t have to cope with the ugly 80x25 resolution, especially on a 19" display. Unfortunately, with the xen kernel, dom0 now uses the 80x25 mode

Hi, everyone, I installed the Xen3.1.0 based on Fedora8 and enter the Dom0 successfully. The kernel of dom0 is linux-2.6.18-xen0. But the Xorg could not start in the Dom0. When I use the "startx" command to start the X server, the error information is following: ......... (==) Using config file: "etc/X11/xorg.conf" (II) Module already built-in (II) Module already built-in

...(after rewrite) doesn't ttm-manage the vram any more. gem objects are managed with the shmem helpers instead and the active framebuffer is blitted to vram. The qemu stdvga (bochs driver) has 16 MB vram by default and can be configured to have up to 256 MB. Plenty of room even for multiple 4k framebuffers if needed. So for the bochs driver all the ttm bo migration logic is not needed, it could just store everything in vram. A set of drm_gem_vram_* helpers would do the job for bochs. I'd expect the same applies to the vbox driver. Dunno about the other drm drivers and the fbdev drivers you pl...

...(after rewrite) doesn't ttm-manage the vram any more. gem objects are managed with the shmem helpers instead and the active framebuffer is blitted to vram. The qemu stdvga (bochs driver) has 16 MB vram by default and can be configured to have up to 256 MB. Plenty of room even for multiple 4k framebuffers if needed. So for the bochs driver all the ttm bo migration logic is not needed, it could just store everything in vram. A set of drm_gem_vram_* helpers would do the job for bochs. I'd expect the same applies to the vbox driver. Dunno about the other drm drivers and the fbdev drivers you pl...

...atch set fixes this bug >> by converting bochs to use the shadow fb. >> >> The patch set has been tested on ast and mga200 HW. >> > > I've been thinking, this enables dirty tracking in DRM userspace for > these drivers since the dirty callback is now set on all framebuffers. > Is this OK? Should we add a drm_fbdev_generic_shadow_setup() that sets a > flag enabling the shadow buffer instead? Fbdev emulation is special wrt framebuffer setup and there's no way to distinguish a regular FB from the fbdev's FB. I've been trying drm_fbdev_generic_shadow_se...

...atch set fixes this bug >> by converting bochs to use the shadow fb. >> >> The patch set has been tested on ast and mga200 HW. >> > > I've been thinking, this enables dirty tracking in DRM userspace for > these drivers since the dirty callback is now set on all framebuffers. > Is this OK? Should we add a drm_fbdev_generic_shadow_setup() that sets a > flag enabling the shadow buffer instead? Fbdev emulation is special wrt framebuffer setup and there's no way to distinguish a regular FB from the fbdev's FB. I've been trying drm_fbdev_generic_shadow_se...

Hi list After I install xen4.0 in my debian squeezz,it added the following lines into /boot/grub/grub.cfg ### BEGIN /etc/grub.d/20_linux_xen ### menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64'' --class debian --class gnu-linux --class gnu --class os --class xen { insmod part_msdos insmod ext2 set

...y more. gem objects are managed with the shmem helpers instead > > and the active framebuffer is blitted to vram. > > > > The qemu stdvga (bochs driver) has 16 MB vram by default and can be > > configured to have up to 256 MB. Plenty of room even for multiple 4k > > framebuffers if needed. So for the bochs driver all the ttm bo > > migration logic is not needed, it could just store everything in vram. > > > > A set of drm_gem_vram_* helpers would do the job for bochs. > > Thanks for clarifying. drm_gem_vram_* (and drm_vram_mm for Simple TTM) >...

As many of us are all too painfully aware we have completely different VNC server implementations for paravirt vs fullyvirt Xen guests. The former based on libvncserver, the latter integrated into QEMU. There are many new and interesting ideas being tried out in the VNC server space in particular wrt to virtualization and having to implement them all twice is not very desirable. Also

...bochs to use the shadow fb. >>>> >>>> The patch set has been tested on ast and mga200 HW. >>>> >>> >>> I've been thinking, this enables dirty tracking in DRM userspace for >>> these drivers since the dirty callback is now set on all framebuffers. >>> Is this OK? Should we add a drm_fbdev_generic_shadow_setup() that sets a >>> flag enabling the shadow buffer instead? >> >> Fbdev emulation is special wrt framebuffer setup and there's no way to >> distinguish a regular FB from the fbdev's FB. I'...

...bochs to use the shadow fb. >>>> >>>> The patch set has been tested on ast and mga200 HW. >>>> >>> >>> I've been thinking, this enables dirty tracking in DRM userspace for >>> these drivers since the dirty callback is now set on all framebuffers. >>> Is this OK? Should we add a drm_fbdev_generic_shadow_setup() that sets a >>> flag enabling the shadow buffer instead? >> >> Fbdev emulation is special wrt framebuffer setup and there's no way to >> distinguish a regular FB from the fbdev's FB. I'...

Does NOUVEAU support mmaping a double-sized Framebuffer? When attempting to run, where fd refers to "/dev/fb0": mmap(ptr, screensize * 2, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); I get back an invalid argument error. This doesn't happen if I only request a single screensize. Is this a limitation of the driver? -------------- next part -------------- An HTML attachment was

When I turn on the "Framebuffer console support" in compiling kernel, after system startup, the console doesn''t work properly and the kernel parameter( for example: vga=719) doesn''t do any effect on kernel. who can help me ? thanks in advance! Andrew Liu _______________________________________________ Xen-tools mailing list Xen-tools@lists.xensource.com