linux-kernel - Re: [PATCH] staging/gma500: get control from firmware framebuffer if conflicts

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] [day] [month] [year] [list]

Message-ID: <20110527095607.5b0b0b7a@bob.linux.org.uk>
Date:	Fri, 27 May 2011 09:56:07 +0100
From:	Alan Cox <alan@...ux.intel.com>
To:	Michael Chang <mchang@...ell.com>
Cc:	Greg KH <gregkh@...e.de>, error27@...il.com,
	justinmattock@...il.com, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging/gma500: get control from firmware framebuffer
 if conflicts

> We should let psbfb takeover framebuffer control from vesafb
> to get around this problem.

Looks good to me assuming we have stolen memory. This maybe wants to
test

	if (pg->stolen_size)

although I'm not sure that adding a zero size aperture would do harm
any way ? The devices without stolen ram also won't have vesa.

Alan
--
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/