search for: fb_uvesa

...d not the other. OK, fair enough. Do you want the patch series respun to add that select in patch 10/10, or would you consider it sufficient to add that in a followup patch, since the kernel will build and boot either way (so it won't break bisection)? Related to that: Is it intentional that FB_UVESA doesn't depend on X86, even though FB_VESA does? Does v86d run on non-x86 hardware via emulation? If so, should FB_UVESA have "select X86_IOPORT if X86"? - Josh Triplett

> > This isn't unreasonable but there are drivers with userspace helpers that > > use iopl/ioperm type functionality where you should be doing a SELECT of > > X86_IOPORT. The one that comes to mind is the uvesa driver. From a quick > > scan it may these days be the only mainstream one that needs the select > > adding. > > Should kernel drivers really

> > This isn't unreasonable but there are drivers with userspace helpers that > > use iopl/ioperm type functionality where you should be doing a SELECT of > > X86_IOPORT. The one that comes to mind is the uvesa driver. From a quick > > scan it may these days be the only mainstream one that needs the select > > adding. > > Should kernel drivers really

...onsole=com1 lapic apic_verbosity=debug apic=debug iommu=off module /boot/linux-2.6.32-xen-r1-a ro root=/dev/sda3 console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10 I have an intel 82915G/GV/910GL graphics card so I configured AGP_INTEL, DRM, FB, FB_BOOT_VESA_SUPPORT, FB_VGA16, FB_UVESA, FB_VESA, VGA_CONSOLE, FONTS, FRAMEBUFFER_CONSOLE, and DUMMY_CONSOLE into the kernel. What am I missing or screwing up? Thanks. -mike d. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users