On Tue, Feb 19, Haiyang Zhang wrote: > > I havent read the vesafb code, but I think it can kind of give up the > > hardware, something ata_piix can not do. > > In my test, the vesafb doesn't automatically give up the emulated video device, > unless I add the DMI based mechanism to let it exit on Hyper-V. >From reading the code, it seems to do that via do_remove_conflicting_framebuffers(). hypervfb does not set apertures etc, so that function is a noop. My point is that with this new driver distro kernel will have no console output until hypervfb is loaded. On native hardware there is at least vesafb which can display something until initrd is running. So if the hypervisor allows that hypervfb can shutdown the emulated vesa hardware then it should do that. Olaf _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
