From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: Dave Airlie <airlied@linux.ie>, Jeff Mahoney <jeffm@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fb/intelfb: Do not depend on EMBEDDED
Date: Wed, 16 Dec 2009 10:00:05 -0800 [thread overview]
Message-ID: <20091216100005.2c7e6d69@jbarnes-piketon> (raw)
In-Reply-To: <200912161437.32134.jdelvare@suse.de>
On Wed, 16 Dec 2009 14:37:31 +0100
Jean Delvare <jdelvare@suse.de> wrote:
> If I wanted to attempt a transparent migration, where would I start?
> As I recall, console on framebuffer needs specific boot parameters,
> right? I don't suppose that kms will transparently pick them and do
> the right thing, do I? If there documentation available on how one
> can get a high resolution console using kms?
Actually, that's one of the big advantages of the KMS based driver. It
*does* transparently pick the native resolution of the detected
output(s) and set up a high res console. You can provide boot options
to override it, but unlike intelfb, boot options aren't necessary to
get things working in the first place.
If you want to run X later, you'll need an updated xf86-video-intel
(preferably 2.9.x) or xf86-video-radeon driver as well, since code to
support the KMS interfaces landed only slightly before 2.6.29 came out
in the case of Intel.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-12-16 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-12 21:55 Jesse Barnes
2009-12-13 11:50 ` Jean Delvare
2009-12-13 21:53 ` Dave Airlie
2009-12-16 13:37 ` Jean Delvare
2009-12-16 18:00 ` Jesse Barnes [this message]
2009-12-16 22:38 ` Krzysztof Halasa
2009-12-16 22:57 ` Dave Airlie
2009-12-16 23:19 ` Krzysztof Halasa
2009-12-14 18:36 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2009-12-12 13:19 Jean Delvare
2009-12-12 20:10 ` Dave Airlie
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=20091216100005.2c7e6d69@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@linux.ie \
--cc=jdelvare@suse.de \
--cc=jeffm@suse.de \
--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
all inboxes | Powered by JetHome®