On 06/28/2013 04:11 AM, David Herrmann wrote:
> Hi
>
> On Wed, Jun 26, 2013 at 10:49 PM, Stephen Warren
> wrote:
>> On 06/24/2013 04:27 PM, David Herrmann wrote:
>>> The current situation regarding boot-framebuffers (VGA, VESA/VBE, EFI) on
>>> x86 causes troubles when loading multiple fbdev
On 06/28/2013 04:11 AM, David Herrmann wrote:
Hi
On Wed, Jun 26, 2013 at 10:49 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
On 06/24/2013 04:27 PM, David Herrmann wrote:
The current situation regarding boot-framebuffers (VGA, VESA/VBE, EFI) on
x86 causes troubles when loading multiple
Hi
On Wed, Jun 26, 2013 at 10:49 PM, Stephen Warren
wrote:
> On 06/24/2013 04:27 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
Hi
On Wed, Jun 26, 2013 at 10:49 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 06/24/2013 04:27 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
On 06/24/2013 04:27 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
> drivers use the FBs.
On 06/24/2013 04:27 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
drivers use the FBs.
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
