mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: i.MX6 frame buffer inside barebox?
Date: Mon, 23 Jun 2014 09:25:02 +0200	[thread overview]
Message-ID: <CAOpc7mFo8jdw24V=2wZW=dCMMbiBW87R7ZGKSqRR7SO4StB79g@mail.gmail.com> (raw)
In-Reply-To: <20140618195849.GL15686@pengutronix.de>

Whaaa, it never occured to me that I have to enable the framebuffer as
well...   thanks, now it works.


As for simplefb, I removed that. I thought that this sets up a
framebuffer in the bootloader, which when Linux' framebuffer driver
takes over, without reprogramm or screen flicker. However, it seems
that this only works with specific framebuffer patterns, e.g. some 16
and 32 bit special rgb formats. I don't really get the need for that,
because the bootloader already has programmed the graphics device
correctly, the Linux driver could just re-use that information, so I
don't really see a need why the framebuffer organization has to be
present in the device tree in yet-another-format (tm).

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

  reply	other threads:[~2014-06-23  7:25 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 [this message]
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='CAOpc7mFo8jdw24V=2wZW=dCMMbiBW87R7ZGKSqRR7SO4StB79g@mail.gmail.com' \
    --to=holgerschurig@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@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