From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Antonino A. Daplas" Subject: Re: [Linux-fbdev-devel] [PATCH 4/5][RFC] fbdev: Clean up framebuffer initialization Date: Sun, 5 Sep 2004 17:50:47 +0800 Sender: linux-kernel-owner@vger.kernel.org Message-ID: <200409051750.47987.adaplas@hotpop.com> References: <200409041108.40276.adaplas@hotpop.com> Reply-To: adaplas@pol.net Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Id: Cc: Andrew Morton , Linux Kernel Development , Thomas Winischhofer On Sunday 05 September 2004 17:16, Geert Uytterhoeven wrote: > On Sat, 4 Sep 2004, Antonino A. Daplas wrote: > > Currently, the framebuffer system is initialized in a roundabout manner. > > First, drivers/char/mem.c calls fbmem_init(). fbmem_init() will then > > iterate over an array of individual drivers' xxxfb_init(), then each > > driver registers its presence back to fbmem. During console_init(), > > drivers/char/vt.c will call fb_console_init(). fbcon will check for > > registered drivers, and if any are present, will call take_over_console() > > in drivers/char/vt.c. > > > > This patch changes the initialization sequence so it proceeds in this > > manner: Each driver has its own module_init(). Each driver calls > > register_framebuffer() in fbmem.c. fbmem.c will then notify fbcon of the > > driver registration. Upon notification, fbcon calls take_over_console() > > in vt.c. > > My main concern with this change is that it will be no longer possible to > change initialization order (and hence choose the primary display for > systems with multiple graphics adapters) by specifying `video=xxxfb' on the > kernel command line. > I see your point. But, can we use "fbcon=" setup options to choose which fb gets mapped to what console? We already have fbcon=map: