From: Andrew Morton <akpm@linux-foundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
linux-fbdev@vger.kernel.org
Subject: Re: i810fb: Breaks EDID for Xorg
Date: Tue, 09 Feb 2010 21:41:51 +0000 [thread overview]
Message-ID: <20100209134151.9ee5d4f4.akpm@linux-foundation.org> (raw)
In-Reply-To: <be7a9f3d1002080536v4c38f6e7k492fd09fdab72b5a@mail.gmail.com>
(cc linux-fbdev-devel)
On Mon, 8 Feb 2010 11:36:39 -0200
Otavio Salvador <otavio@ossystems.com.br> wrote:
> Hello,
>
> After some time looking for why one system had EDID working, for Xorg,
> and other don't I found the reason being CONFIG_FB_I810.
>
> When I enable CONFIG_FB_I810 the Xorg VBE reading fails; if I disable
> it, it works fine.
>
> Anyone has any idea how to fix it?
>
parent reply other threads:[~2010-02-09 21:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <be7a9f3d1002080536v4c38f6e7k492fd09fdab72b5a@mail.gmail.com>]
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=20100209134151.9ee5d4f4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=otavio@ossystems.com.br \
/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;
as well as URLs for NNTP newsgroup(s).