From: Hendrik <chasake@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot Sunxi breaks LCD output on Olimex Lime A10
Date: Wed, 01 Oct 2014 19:43:14 +0200 [thread overview]
Message-ID: <542C3D32.2040809@yahoo.com> (raw)
I have always been using the sunxi u-boot from
'https://github.com/linux-sunxi/u-boot-sunxi' and that works fine, but
now I want to boot the kernel from USB. That is not possible in that
u-boot branch. Therefore I switched to the latest U-Boot
'git://git.denx.de/u-boot.git' for the Olimex Allwinner A10 Lime as this
one does have a working USB mass storage implementation.
But when the kernel and root filesystem is booted and my application
(using DirectFB) starts, the LCD screen is flickering between a correct
image and an incorrect image as if sometimes random image data is
displayed to the screen. Although it looks more like a clock or timing
issue because the colors of the faulty screen resemble the colors of the
correct screen. Also: when the cpu is inactive the screen is more or
less ok but when doing a lot of work the screen starts to flicker. Then
it is stable for a while and after some time it starts flickering again.
I am using the exact same kernel, root filesystem, U-boot environment,
SD-card and 'script.bin' (which defines the hardware layout, I am not
using a device tree file). The only difference is the version (and
origin) of U-boot.
Can anybody shine some light on this? Maybe Hans de Goede? I have seen
his name pop-up a lot of times with the Sunxi branch.
Regards,
Hendrik
next reply other threads:[~2014-10-01 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 17:43 Hendrik [this message]
2014-10-03 8:04 ` [U-Boot] U-Boot Sunxi breaks LCD output on Olimex Lime A10 Hans de Goede
2014-10-03 8:49 ` Siarhei Siamashka
2014-10-03 9:19 ` Hans de Goede
2014-10-06 14:05 ` Hendrik
2014-10-06 16:46 ` Hendrik
2014-10-16 9:22 ` Siarhei Siamashka
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=542C3D32.2040809@yahoo.com \
--to=chasake@yahoo.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.