From: Geert Uytterhoeven <geert@linux-m68k.org>
To: hs@denx.de
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
Subject: Re: [RFC PATCH] video/logo: introduce new system state for checking if logos are freed
Date: Tue, 26 May 2015 07:41:57 +0000 [thread overview]
Message-ID: <CAMuHMdWrxkH17dbhzgqAAhtqJSg5WRLOmvdeupvLB-1cKE7ybg@mail.gmail.com> (raw)
In-Reply-To: <55642243.5000205@denx.de>
Hi Heiko,
On Tue, May 26, 2015 at 9:35 AM, Heiko Schocher <hs@denx.de> wrote:
> Am 26.05.2015 09:25, schrieb Geert Uytterhoeven:
>>
>> On Tue, May 26, 2015 at 9:17 AM, Heiko Schocher <hs@denx.de> wrote:
>>>
>>> 4) draw only one logo even on multicores ... why must every core draw
>>> a logo? Currently each core draws the logo, and on a system with more
>>> than 4 cores, I think this looks not really good ...
>>
>>
>> I don't think each core draws a logo. They're all drawn from
>> fbcon_switch().
>
> Hmm... I have here an imx6dl based system, and it draws two logos when
> booting...
It draw one logo _for_ each cpu core, but each logo is not drawn _by_ each
cpu core.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2015-05-26 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 7:09 [RFC PATCH] video/logo: introduce new system state for checking if logos are freed Heiko Schocher
2015-05-25 5:57 ` Tomi Valkeinen
2015-05-26 3:56 ` Heiko Schocher
2015-05-26 6:54 ` Tomi Valkeinen
2015-05-26 7:08 ` Geert Uytterhoeven
2015-05-26 7:15 ` Tomi Valkeinen
2015-05-26 7:23 ` Geert Uytterhoeven
2015-05-26 7:29 ` Heiko Schocher
2015-05-26 7:17 ` Heiko Schocher
2015-05-26 7:25 ` Geert Uytterhoeven
2015-05-26 7:35 ` Heiko Schocher
2015-05-26 7:41 ` Geert Uytterhoeven [this message]
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=CAMuHMdWrxkH17dbhzgqAAhtqJSg5WRLOmvdeupvLB-1cKE7ybg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=hs@denx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).