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.
Just disable "Enable firmware EDID" in
"Device Drivers"->"Graphics support"->"Support for frame buffer devices"
of your menuconfig dialog. The help mentions, that this will not always work.
That will make your hardware work flawlessly again.
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
