From: Olivier Galibert <galibert@pobox.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Dave Airlie <airlied@gmail.com>, Jan Dittmer <jdi@l4x.org>,
Diego Calleja <diegocg@gmail.com>,
linux-kernel@vger.kernel.org, eric.anholt@iintel.com,
airlied@linux.ie
Subject: Re: intel kms "Failed to allocate space for kernel memory manager"
Date: Mon, 12 Jan 2009 22:32:35 +0100 [thread overview]
Message-ID: <20090112213235.GA58682@dspnet.fr.eu.org> (raw)
In-Reply-To: <200901120953.50167.jbarnes@virtuousgeek.org>
On Mon, Jan 12, 2009 at 09:53:49AM -0800, Jesse Barnes wrote:
> On the contrary, I think we have way too many options and configuration
> possibilities. The more we have, the more likely some combination of them
> will be broken.
You need to be able to fix wrong data coming from the bios or other roms.
> That said, modes are generally pretty easy to handle, so users can provide
> them through xrandr and xorg.conf; I don't see that changing.
The intel driver ignores modelines if a bios mode is present, at least
for lvds. Check i830_lvds_mode_fixup.
OG.
next prev parent reply other threads:[~2009-01-12 21:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <621d098f0901110546p2b99a525k5de54e37fa181197@mail.gmail.com>
2009-01-11 13:51 ` intel kms "Failed to allocate space for kernel memory manager" Jan Dittmer
2009-01-11 21:21 ` Diego Calleja
2009-01-11 21:39 ` Dave Airlie
2009-01-11 22:04 ` Diego Calleja
2009-01-12 7:42 ` Jan Dittmer
2009-01-12 8:04 ` Dave Airlie
2009-01-12 8:37 ` Jan Dittmer
2009-01-12 17:56 ` Jesse Barnes
2009-01-12 18:30 ` Diego Calleja
2009-01-12 21:19 ` Jan Dittmer
2009-01-12 21:33 ` Jan Dittmer
2009-01-12 21:53 ` Jesse Barnes
2009-01-12 22:08 ` Jan Dittmer
2009-01-12 22:29 ` Jan Dittmer
2009-01-12 23:19 ` Jesse Barnes
2009-01-12 13:03 ` Olivier Galibert
2009-01-12 17:53 ` Jesse Barnes
2009-01-12 21:32 ` Olivier Galibert [this message]
2009-01-12 21:59 ` Jesse Barnes
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=20090112213235.GA58682@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=diegocg@gmail.com \
--cc=eric.anholt@iintel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jdi@l4x.org \
--cc=linux-kernel@vger.kernel.org \
/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