mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@gmail.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: i.MX6 frame buffer inside barebox?
Date: Wed, 25 Jun 2014 15:46:28 +0200	[thread overview]
Message-ID: <CAOpc7mHHo9Fk4qzW9prc=oX2sBVvQBPL2CyH5q2uRqHgEH4gfg@mail.gmail.com> (raw)
In-Reply-To: <20140623165754.GA27898@pengutronix.de>

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).

However, I checked with an Oscillioscope that if I setup the backlight
PWM (pwm0 in Barebox) and start Linux without CONFIG_PWM /
CONFIG_PWM_IMX, then the PWM is turned off as soon as Linux has been
started. Memory 0x2080000 shows in bit 0 that the PWM is still turned
on. But as nothing comes out, it must be the clock.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-06-25 13:46 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 [this message]
2014-06-26  5:55             ` Sascha Hauer

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='CAOpc7mHHo9Fk4qzW9prc=oX2sBVvQBPL2CyH5q2uRqHgEH4gfg@mail.gmail.com' \
    --to=holgerschurig@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=r.schwebel@pengutronix.de \
    /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