Well. To debug library I plan to write log to file. I have only one question: how to move the file from qemu to host?
2014-05-19 13:41 GMT+04:00, Martin Decky <[email protected]>: > Hi Wolf, > >> I think that it's counterproductive now to spend time to try to >> support a few versions of qemu/seabios. I guess hardware vendors >> doesn't use 32-bit gcc much to compile their bioses. >> Anyway, all the interaction with vbios will be hidden in libvbe and I >> always will be able to replace its backend transparently. > > Sorry, it's probably just my fault, but I am really not sure what are > you actually suggesting now. > > That (a) your user space VESA mode setting will not support some common > versions of QEMU or SeaBIOS? Or (b) that you are going to use a > completely different solution for libvbe that will also properly support > QEMU? > > If my interpretation (a) is correct, then it is really not acceptable > for me. In my opinion, your GSoC project should definitively deliver > reasonable mode setting functionality in reasonable QEMU builds and on > some reasonable physical hardware. A "reasonable build of QEMU" could be > defined as a build where VESA mode setting works in Windows 8 or in > X.Org 1.15 in Linux. > > I understand that if you want to base your solution on x86emu from your > prototype branch, this means some tedious debugging and implementing for > you. But hey, that's life :) Nobody promised you that working on your > GSoC project will be always a piece of cake. > > On the other hand, if my interpretation (b) is correct, then you have my > full support. But could you shed some light on how do you plan to tackle > it and avoid the issues we observe with x86emu? Thanks in advance. > > > M.D. > > _______________________________________________ > HelenOS-devel mailing list > [email protected] > http://lists.modry.cz/listinfo/helenos-devel > _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
