Mohammad A. Haque provided enlightenment:
>>Why does fbcon_show_logo() have a loop that looks at smp_num_cpus?
> For every CPU you have you see one more Tux
(blush) I should have figured that out for myself.
You know, a different, or at least more comprehensive patch will be needed
for machines with more than 8 processors, depending on screen resolution,
since 8 Tux will overflow a 640 pixel wide screen. Of course, most of those
machines won't be using framebuffer consoles at VGA resolutions... still...
Yes, on SMP boxes the original design would be better. My patch is actually
intended for embedded systems where you want a big, user-friendly logo on
the screen instead of the console boot messages.
Thanks for the tip. I'll change the patch. Actually, now that I understand
that bit, I realize that a much better way to do it is to add x_start up
there, for (x=x_start; x < smp_num_cpus * ..., rather than separately for
each different version of the drawing loops.
Torrey
torrey@arnor.net
thoffman1@hotmail.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Oct 07 2000 - 21:00:11 EST