From: Baruch Siach <baruch@tkos.co.il>
To: Boaz Ben-David <boaz.bd@wellsense-tech.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: iMX35 3stack framebuffer problem
Date: Tue, 11 Oct 2011 09:01:56 +0200 [thread overview]
Message-ID: <20111011070155.GD16040@sapphire.tkos.co.il> (raw)
In-Reply-To: <4E93E8CB.1040504@wellsense-tech.com>
Hi Boaz,
On Tue, Oct 11, 2011 at 08:57:15AM +0200, Boaz Ben-David wrote:
> On 10/11/11 08:54, Robert Schwebel wrote:
>
> On Tue, Oct 11, 2011 at 08:40:52AM +0200, Boaz Ben-David wrote:
>
> Yes, I didn't mention it, but I tried your suggestion. It works
> (meaning there's no flicker) but
>
> the problem is that the screen is blank for about 8 seconds before I
> have control again to init it.
>
> People here said they prefer flicker over 8 seconds of blank time...
>
> This is why we have a framebuffer / video driver framework in Barebox.
> We do not have a driver for MX35 yet, but that could of course be
> changed.
>
> On the other hand, I'm wondering why it needs 8 s until you see
> something on the Linux side. We have an MX35 system here which runs at
> 532 MHz, and it needs about 1 s from power-on into Linux userspace, so
> we decided to show the splash screen from there.
>
> rsc
>
> The kernel size is almost 5MB (it includes an initramfs).
>
> 8 seconds are from the time I call "bootm uImage" and until the init script in
> the initramfs kicks in.
>
> If I can seriously shorten this time I will be glad to know, maybe there's
> something I missed.
>
> Any input will be appreciated.
See
http://elinux.org/images/8/89/ELCE-2010-Barebox-Booting-Linux-Fast-and-Fancy.pdf.
This presentation (by Robert Schwebel) specifically mentions Barebox on
i.MX35.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-10-11 7:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 16:35 Boaz Ben-David
2011-03-08 5:35 ` Marc Reilly
2011-03-08 7:03 ` Boaz Ben-David
2011-03-08 7:10 ` Baruch Siach
2011-05-29 6:08 ` Boaz Ben-David
2011-05-29 6:33 ` Baruch Siach
2011-05-29 7:14 ` Boaz Ben-David
2011-05-29 7:28 ` Baruch Siach
2011-10-09 7:10 ` Boaz Ben-David
2011-10-10 4:44 ` Baruch Siach
2011-10-11 6:40 ` Boaz Ben-David
2011-10-11 6:54 ` Robert Schwebel
[not found] ` <4E93E8CB.1040504@wellsense-tech.com>
2011-10-11 6:59 ` Boaz Ben-David
2011-10-11 7:01 ` Baruch Siach [this message]
2011-10-11 7:06 ` Robert Schwebel
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=20111011070155.GD16040@sapphire.tkos.co.il \
--to=baruch@tkos.co.il \
--cc=barebox@lists.infradead.org \
--cc=boaz.bd@wellsense-tech.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