On Wed, Jan 6, 2010 at 12:59 PM, Bruno Prémont
<bonbons@xxxxxxxxxxxxxxxxx> wrote:
> On Wed, 06 January 2010 Miles Lane <miles.lane@xxxxxxxxx> wrote:
>> For a long time I have gotten two pictures of Tux showing up when I
>> include the Tux display option in my custom kernel builds. I don't
>> know how many kernel revisions ago it was when I started noticing
>> this. It seems like it might have been early in the 2.6 series
>> kernels.
>
> Unless your system has exactly one CPU without hyperthreading and with
> exactly one core this is the correct bahavior, one tux per logical CPU.
>
> If you just want a single tux you can run your kernel on a system with
> only one logical CPU, boot it with maxcpus=1 or rebuild it with
> CONFIG_SMP=n... though in those case you will not be able to benefit
> from all of your CPU's resources..
>
> Bruno
Oh! Well, that explains it. That is truly weird functionality. Is
Tux a de facto
CPU presence indicator? It doesn't make any sense to me, if so.
Miles
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
