From: Rene Herman <rene.herman@keyaccess.nl>
To: Frans Pop <elendil@planet.nl>
Cc: akpm@osdl.org, mingo@elte.hu,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, adaplas@gmail.com
Subject: Re: Framebuffer drivers that break the boot on systemswithout the hardware
Date: Sun, 10 Aug 2008 23:49:07 +0200 [thread overview]
Message-ID: <489F6253.3010703@keyaccess.nl> (raw)
In-Reply-To: <200808092319.43139.elendil@planet.nl>
On 09-08-08 23:19, Frans Pop wrote:
> Rene Herman wrote:
>> Ingo Molnar posted a list of drivers he found to break the boot during
>> testing of randconfig kernels and among them are a number of FB drivers:
>>
>> FB_VESA
>
> This one is set to "y" in the kernel configs for the generic Debian
> kernels for i386 and x86_64 and is used by default for the graphical
> version of the Debian Installer, so I'd be very surprised if it broke
> very many systems...
> AFAIK it is only actually enabled if the 'vga=' boot parameter is passed.
>
> Ingo's mail also lists FRAMEBUFFER_CONSOLE which again is set to "y" in
> Debian's standard kernel configs for x86 (and probably most other
> arches).
Okay. MDA_CONSOLE was also in there impying RAM at 0xb0000 which might
indicate a gun/foot situation here...
>> (and FB_VIRTUAL)
>
> This one should be fixed with 2.6.27-rc1. The commit that fixes it is:
> commit b604838ac6d233fd6bffc0e758a818133a01ff22
> Author: Frans Pop <elendil@planet.nl>
> Date: Wed Jul 23 21:31:26 2008 -0700
> vfb: only enable if explicitly requested when compiled in
Ah, thanks.
Rene.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
WARNING: multiple messages have this Message-ID (diff)
From: Rene Herman <rene.herman@keyaccess.nl>
To: Frans Pop <elendil@planet.nl>
Cc: adaplas@gmail.com, mingo@elte.hu, akpm@osdl.org,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Framebuffer drivers that break the boot on systemswithout the hardware
Date: Sun, 10 Aug 2008 23:49:07 +0200 [thread overview]
Message-ID: <489F6253.3010703@keyaccess.nl> (raw)
In-Reply-To: <200808092319.43139.elendil@planet.nl>
On 09-08-08 23:19, Frans Pop wrote:
> Rene Herman wrote:
>> Ingo Molnar posted a list of drivers he found to break the boot during
>> testing of randconfig kernels and among them are a number of FB drivers:
>>
>> FB_VESA
>
> This one is set to "y" in the kernel configs for the generic Debian
> kernels for i386 and x86_64 and is used by default for the graphical
> version of the Debian Installer, so I'd be very surprised if it broke
> very many systems...
> AFAIK it is only actually enabled if the 'vga=' boot parameter is passed.
>
> Ingo's mail also lists FRAMEBUFFER_CONSOLE which again is set to "y" in
> Debian's standard kernel configs for x86 (and probably most other
> arches).
Okay. MDA_CONSOLE was also in there impying RAM at 0xb0000 which might
indicate a gun/foot situation here...
>> (and FB_VIRTUAL)
>
> This one should be fixed with 2.6.27-rc1. The commit that fixes it is:
> commit b604838ac6d233fd6bffc0e758a818133a01ff22
> Author: Frans Pop <elendil@planet.nl>
> Date: Wed Jul 23 21:31:26 2008 -0700
> vfb: only enable if explicitly requested when compiled in
Ah, thanks.
Rene.
next prev parent reply other threads:[~2008-08-10 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 20:15 Framebuffer drivers that break the boot on systemswithout the hardware Rene Herman
2008-08-09 20:33 ` Rene Herman
2008-08-09 21:19 ` Frans Pop
2008-08-09 21:19 ` Frans Pop
2008-08-10 21:49 ` Rene Herman [this message]
2008-08-10 21:49 ` Rene Herman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=489F6253.3010703@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=elendil@planet.nl \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.