To quote Filip Van Raemdonck <mechanix@debian.org>,
> > for those thinking about something like this, it uses frame buffer
> > support (of course) to do what it does.
>
> If this is the same thing as Corel uses, then it (most likely) does
not -
> unless Corel hacked the fb drivers.
> I once tested Corel on a machine with a S3 Trio64V+ card; this card is
VESA
> 1.3 compliant and thus not supported by fb (which requires 2.0 for
vesafb, or
> an explicit driver for your card). The Corel splash screen was there
though.
Well, there is a framebuffer driver for the S3 Trio. CONFIG_FB_S3TRIO,
not surprisingly. So perhaps that's what Corel used. It's still
framebuffer code. I never tried Corel. However, I don't know of any
other way to get graphics as soon as the kernel starts running, without
using the framebuffer.
> > From what I understand you can't use framebuffer support if you use
> > things like the nvida drivers.
>
> Says who?
What he meant was that you can't use the VESA framebuffer code(which the
Linux Progress Patch requires), *as well as* a specific driver. So
either the LPP would have to be changed to support a more generic
implementation(that all the FB drivers can use), or else the VESA driver
must be used.
> No problems at all here...
Nor are there any here :)
David Barclay Harris, Clan Barclay
Don't panic.
Attachment:
pgp6_7Lg6VmNZ.pgp
Description: PGP signature