Date: Tue, 17 Jun 2003 21:03:05 +0100 (BST)
From: James Simmons <jsimmons@infradead.org>
To: Ian Molton <spyro@f2s.com>
cc: linux-kernel@vger.kernel.org
Subject: Re: FRAMEBUFFER (and console)
In-Reply-To: <20030617015255.3016cb99.spyro@f2s.com>
Message-ID: <Pine.LNX.4.44.0306172059510.21214-100000@phoenix.infradead.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1115
Lines: 27


> My framebuffer (and therefore system console, by definition) come up
> rather late.
> 
> It seems the console doesnt care to check for drivers comming up after a
> certain time, and thus I get no output despite the driver working.
> 
> I'd like to do something like console_rescan_my_damn_device() if
> possible :-)
> 
> My only option right now appears to be to set up a dummy framebuffer
> prior to real one starting up.

The reason for this is because the framebuffers most often depend on the 
bus being set up. Usually this happening later in the boot process. What 
are trying to do? Retrieve the earlier printk messages. Do you have 
DUMMY_CONSOLE set to Y. I believe the data is transfered from dummycon to 
fbcon after fbcon is initialized. If you having problems with that try 
increasing the size of dummycon's "screen". See dummycon.c for more 
details.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/