From: <GUt...@fr...> - 2004-02-01 17:53:23
|
Ok, this may be a silly question. I am not a kernel/fbdev hacker, so I=20 may ignore some relevant issues. But after many researches, I can't see=20 why it would be impossible for the vesafb driver to handle modes switchin= g. According to my understanding of this stuff, vesafb mode setting is=20 possible only during real mode, via a boot argument, set by bios=20 interrupts, which prevent from changing it later (if I said something=20 wrong, please correct me.) But what about the xfree86 driver ? It seems=20 to do its job via the VBE bios of the card. What would prevent vesafb=20 from doing the same ? I know vesafb only supports VBE 2.0, not 3.0. I=20 couldn't find the VBE 2.0 documentation, but in VBE 3.0 one, protected=20 mode is supported. I would see this as a great improvement, because of the really little=20 number of cards actually supported by vesafb. Regards, Ga=EBl D. |