Hi
Any comments on this?
On Thu, Jul 4, 2013 at 2:25 PM, David Herrmann wrote:
> The current situation regarding boot-framebuffers (VGA, VESA/VBE, EFI) on
> x86 causes troubles when loading multiple fbdev drivers. The global
> "struct screen_info" does not provide any state-tracking about which
Hi
Any comments on this?
On Thu, Jul 4, 2013 at 2:25 PM, David Herrmann dh.herrm...@gmail.com wrote:
The current situation regarding boot-framebuffers (VGA, VESA/VBE, EFI) on
x86 causes troubles when loading multiple fbdev drivers. The global
struct screen_info does not provide any
The current situation regarding boot-framebuffers (VGA, VESA/VBE, EFI) on
x86 causes troubles when loading multiple fbdev drivers. The global
"struct screen_info" does not provide any state-tracking about which
drivers use the FBs. request_mem_region() theoretically works, but
unfortunately
The current situation regarding boot-framebuffers (VGA, VESA/VBE, EFI) on
x86 causes troubles when loading multiple fbdev drivers. The global
struct screen_info does not provide any state-tracking about which
drivers use the FBs. request_mem_region() theoretically works, but
unfortunately