public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: Yum Rayan <yum.rayan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] VBE DDC bios call stalls boot
Date: Mon, 24 Apr 2006 07:40:59 +0800	[thread overview]
Message-ID: <444C108B.9090801@gmail.com> (raw)
In-Reply-To: <200604232214.32662.ioe-lkml@rameria.de>

Ingo Oeser wrote:
> On Sunday, 23. April 2006 21:08, Yum Rayan wrote:
>> I don't think boot should stall for any reason. Moreover given that
>> user space programs are doing these VBE/DDC calls, I don't see any
>> compelling reason why this code need to exist is such early boot
>> stage. If it absolutely needs to be called in the kernel, at least if
>> invoked sometime later, we could time out this call as a workaround.
> 
> Don't configure CONFIG_FB_FIRMWARE_EDID, if it doesn't work
> on your hardware. 

This option is new and not yet available in 2.6.15, so you may have
to use your patch temporarily. If you can, set CONFIG_VIDEO_SELECT = n
in Device Drivers -> Graphics support -> Console Drivers ->
Video mode selection support. However, this is automatically selected by FB, 
PCI, and X86_32, so it may not be changeable.

The "vga=" option will not be available if VIDEO_SELECT is not set.

Or just apply this changeset:

http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=59153f7d7effdb5b3c81eb6d03914a866157b319

to make CONFIG_FB_FIRMWARE_EDID available.

Tony

  reply	other threads:[~2006-04-23 23:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-23 19:08 [RFC] VBE DDC bios call stalls boot Yum Rayan
2006-04-23 20:14 ` Ingo Oeser
2006-04-23 23:40   ` Antonino A. Daplas [this message]
2006-04-23 20:24 ` Dave Jones
2006-04-23 23:47   ` Antonino A. Daplas
2006-04-24  7:27     ` Yum Rayan

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=444C108B.9090801@gmail.com \
    --to=adaplas@gmail.com \
    --cc=ioe-lkml@rameria.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yum.rayan@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox