From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Herrmann Date: Sun, 17 Feb 2013 17:59:05 +0000 Subject: [PATCH 3/9] video: sysfb: always provide vbefb device Message-Id: <1361123951-587-4-git-send-email-dh.herrmann@gmail.com> List-Id: References: <1361123951-587-1-git-send-email-dh.herrmann@gmail.com> In-Reply-To: <1361123951-587-1-git-send-email-dh.herrmann@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-kernel@vger.kernel.org Cc: Florian Tobias Schandinat , linux-fbdev@vger.kernel.org, David Airlie , dri-devel@lists.freedesktop.org, David Herrmann From: David Herrmann HACK: This should be provided by architecture setup code. But to show how it is supposed to work, we now simply add a "vbefb" device during initialization. The better way to do this is by moving this into arch-code. So for instance the x86 boot initialization should create this platform-device after VBE/VESA screen detection. Other architectures can do the same or introduce other framebuffer types than SYSFB_VBE. Signed-off-by: David Herrmann --- drivers/video/sysfb.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/drivers/video/sysfb.c b/drivers/video/sysfb.c index 5b47a9a..0c0a4e7 100644 --- a/drivers/video/sysfb.c +++ b/drivers/video/sysfb.c @@ -271,6 +271,8 @@ static struct platform_driver sysfb_vbe_driver = { .remove = sysfb_vbe_remove, }; +static struct platform_device *sysfb_vbe_device; + static int __init sysfb_init(void) { int ret; @@ -287,6 +289,12 @@ static int __init sysfb_init(void) goto err_bus; } + sysfb_vbe_device = platform_device_register_data(NULL, "vbefb", -1, + &screen_info, + sizeof(screen_info)); + if (!sysfb_vbe_device) + pr_warn("cannot create vbefb device\n"); + return 0; err_bus: -- 1.8.1.3