From: Peter Zijlstra <peterz@infradead.org>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
Sylvain Meyer <sylvain.meyer@worldonline.fr>,
linux-fbdev@vger.kernel.org
Subject: Re: 2.6.33-rc3 -- Intel 945GME (inteldrmfb) -- Two Tux images displayed are side by side (should only show one).
Date: Wed, 06 Jan 2010 19:25:22 +0100 [thread overview]
Message-ID: <1262802322.4049.55.camel@laptop> (raw)
In-Reply-To: <a44ae5cd1001061010u2d31f24fx2dca6e7953687db@mail.gmail.com>
On Wed, 2010-01-06 at 13:10 -0500, Miles Lane wrote:
> On Wed, Jan 6, 2010 at 1:07 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Wed, 2010-01-06 at 12:16 -0500, Miles Lane 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.
> >
> > Doesn't it show one for each cpu in the system?
>
> Apparently so. And, why this should be true is beyond me.
drivers/video/fbmem.c:
int fb_show_logo(struct fb_info *info, int rotate)
{
int y;
y = fb_show_logo_line(info, rotate, fb_logo.logo, 0,
num_online_cpus());
y = fb_show_extra_logos(info, y, rotate);
return y;
}
I guess its just a cute way of showing off how many cpus you've got ;-)
next prev parent reply other threads:[~2010-01-06 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 17:16 2.6.33-rc3 -- Intel 945GME (inteldrmfb) -- Two Tux images displayed are side by side (should only show one) Miles Lane
2010-01-06 17:37 ` James Simmons
2010-01-06 17:42 ` Miles Lane
2010-01-06 17:48 ` James Simmons
2010-01-06 18:08 ` Miles Lane
2010-01-06 17:59 ` Bruno Prémont
2010-01-06 18:06 ` Miles Lane
2010-01-06 18:07 ` Peter Zijlstra
2010-01-06 18:10 ` Miles Lane
2010-01-06 18:25 ` Peter Zijlstra [this message]
2010-01-06 18:35 ` Miles Lane
2010-01-09 10:34 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1262802322.4049.55.camel@laptop \
--to=peterz@infradead.org \
--cc=airlied@linux.ie \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=sylvain.meyer@worldonline.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox