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: Wed, 18 Jun 2014 21:58:49 +0200 [thread overview]
Message-ID: <20140618195849.GL15686@pengutronix.de> (raw)
In-Reply-To: <CAOpc7mFqu1ov94naTWtCiJMXxNk5RLa=mSL-eh3SwFXNoP1UGg@mail.gmail.com>
On Wed, Jun 18, 2014 at 04:26:48PM +0200, Holger Schurig wrote:
> Hi, I'm a bit puzzled. I compiled my barebox with
>
> CONFIG_CMD_SPLASH=y
> CONFIG_VIDEO=y
> CONFIG_DRIVER_VIDEO_IMX_IPUV3=y
> CONFIG_DRIVER_VIDEO_IMX_IPUV3_LVDS=y
> CONFIG_DRIVER_VIDEO_SIMPLEFB=y
>
> and some entries in the device tree about it (see below). And when I
> boot barebox, I see /dev/fb0.
>
> However, the LVDS signals don't come out of the CPU, e.g. LVDS_CLK0_P
> / LVDS_CLK0_N is silent. Do I need something to enable the drive as
> well? Simply writing to /dev/fb0, e.g. with the "splash" or "mw -d
> /dev/fdb0" command, doesn't seem to do the magic.
have you enabled the framebuffer? fb0.enable=1
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
next prev parent reply other threads:[~2014-06-18 19:59 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 [this message]
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
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=20140618195849.GL15686@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