The LINUX_LOGO_COLORS value acts similarly to INCLUDE_LINUX_LOGO* for the
full color logo, ie. if it matches the number of colors of the default logo,
it will be used, otherwise you'll have to specify your own logo.
This is done so that you can e.g. have a custom full color logo, but share
common bw and 16 color logo.
>
> Another question: INCLUDE_LINUX_LOGOBW is defined in
> linux/include/asm-{mips,ppc}/linux_logo.h but not used at all. Since
> INCLUDE_LINUX_LOGO16 is used in allmost all include/asm-*/linux_logo.h
> files - wouldn't it be sensefull to use INCLUDE_LINUX_LOGOBW in all logos
> to or to drop INCLUDE_LINUX_LOGOBW _and_ INCLUDE_LINUX_LOGO16?
First take a look at the patch Martin Mares posted, you'll see it is used
somewhere. Those INCLUDE_LINUX_LOGO* just decide whether such type of logo
should be included from the generic logo file or if you have your own or if
you don't need it at all. E.g. sparc32 never needs the 16 color logo.
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.1.118 on a sparc64 machine (498.80 BogoMips).
___________________________________________________________________
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html