From: Sascha Hauer <s.hauer@pengutronix.de>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: i.MX6 frame buffer inside barebox?
Date: Thu, 26 Jun 2014 07:55:16 +0200 [thread overview]
Message-ID: <20140626055516.GV15686@pengutronix.de> (raw)
In-Reply-To: <CAOpc7mHHo9Fk4qzW9prc=oX2sBVvQBPL2CyH5q2uRqHgEH4gfg@mail.gmail.com>
On Wed, Jun 25, 2014 at 03:46:28PM +0200, Holger Schurig wrote:
> I just noticed that simplefb wouldn't work with i.MX6 anyway, even if
> I adapt it.
>
> When I setup the framebuffer from barebox and display a splash and
> then boot into Linux, then my framebuffer vanishes. Even when I don't
> have simplefb or ipu enabled.
>
> I think (!) the reason is the clock framework.The clocks for the IPU
> are turned off, and so I don't see anything anymore (this is, however,
> a wild assumption, I haven't checked it yet).
You're probably right. You could check that with passing
'clk_ignore_unused' to the kernel.
Indeed I remember that we tweaked the clocks in a project we used
simplefb in.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-06-26 5:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 14:26 Holger Schurig
2014-06-18 19:58 ` Sascha Hauer
2014-06-23 7:25 ` Holger Schurig
2014-06-23 7:43 ` Sascha Hauer
2014-06-23 8:42 ` Holger Schurig
2014-06-23 10:03 ` Sascha Hauer
2014-06-23 16:57 ` Robert Schwebel
2014-06-25 13:46 ` Holger Schurig
2014-06-26 5:55 ` Sascha Hauer [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=20140626055516.GV15686@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=holgerschurig@gmail.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