linux-kernel - Re: [PATCH] fb/intelfb: Do not depend on EMBEDDED

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 16 Dec 2009 10:00:05 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Jean Delvare <jdelvare@...e.de>
Cc:	Dave Airlie <airlied@...ux.ie>, Jeff Mahoney <jeffm@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fb/intelfb: Do not depend on EMBEDDED

On Wed, 16 Dec 2009 14:37:31 +0100
Jean Delvare <jdelvare@...e.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/