So, I can't find any instructions on getting this up and running (x86-linux-uclibc-mesa-7.8.1 / qemu). I think that I'm pretty close. Any help is much appreciated, and I promise to submit any patches that are useful... So far I've got the kernel (2.6.34) built with kms, and vmwgfx support. I boot an x86 image (uclibc) in qemu. /usr/bin/qemu -kernel '/home/jamie/neworyzans/bzImage.kms2' -append 'root=/dev/sda rw video=vmwgfx ' -boot c -m 128 -hda '/home/jamie/neworyzans/output/images/rootfs.i686.ext2' -net nic,vlan=0,model=e1000 -net tap,ifname=tap0,script=/etc/qemu-ifup -vga vmware on boot I modprobe the modules: modprobe vmwgfx The gfx resolution changes (corrupting the console), and the following modules seem to load OK: lsmod: Module Size Used by Tainted: G vmwgfx 62458 0 ttm 49037 1 vmwgfx drm 164569 2 vmwgfx,ttm agpgart 31292 2 ttm,drm qemu complains with the following: vmsvga_value_write: Bad colour depth: 24 bits vmsvga_value_write: Bad register 09 vmsvga_value_write: Bad register 0a vmsvga_value_write: Bad register 0b If I go ahead and try and run an app, I get this: export EGL_DRIVER=/usr/local/lib/egl/egl_kms_vmwgfx.so cd progs/egl ./eglscreen segfault ./strace ./eglscreen (attached out.txt) on the console running qemu I get this: vmsvga_value_write: Bad register 22 vmsvga_value_write: Bad register 22 vmsvga_value_write: Bad register 22 vmsvga_value_write: Bad register 22 ... vmsvga_value_write: Bad register 22 vmsvga_value_write: Bad register 22 vmsvga_value_write: Bad register 22 vmsvga_value_write: Bad register 22 Am I doing anything obviously wrong? Jamie <div class="gmail_quote">On Sat, May 29, 2010 at 1:08 AM, Chia-I Wu <<a href="mailto:olvaffe@gmail.com" target="_blank">olvaffe@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>On Fri, May 28, 2010 at 6:22 PM, Jamie Amendolagine <<a href="mailto:jamie.amendolagine@gmail.com" target="_blank">jamie.amendolagine@gmail.com</a>> wrote: > Great, Thanks! -- er. It looks like fbdev is not what I needed though I > don't think that it would support egl/ogl-es/ovg would it? -- it looks like > egl -> kms, or maybe egl -> driver_for_my_embedded_target. Is more like it. </div>Yes. You need to use KMS, or write an fbdev backend for Gallium EGL driver(s). It should not take long with reasonable knowledge of Gallium. A patch is welcomed :) -- olv@LunarG.com </blockquote></div>