From: "Andreas Färber" <afaerber@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] rockchip: firefly-rk3288 broken - DRAM wrong?
Date: Sun, 3 Apr 2016 21:32:33 +0200 [thread overview]
Message-ID: <57016FD1.6060408@suse.de> (raw)
In-Reply-To: <57013F32.9040801@suse.de>
Am 03.04.2016 um 18:05 schrieb Andreas F?rber:
> v2016.01 is the last release to boot Linux on the Firefly-RK3288 for me.
> On v2016.03 or master there is no output from the kernel.
Correction: Plain v2016.03 does work but not openSUSE's package.
> This coincides with the DRAM getting misdetected as 512 MiB:
Seems to be unrelated, v2016.03 shows this wrong and boots okay.
ed980b8c62fbe17052ec6151a68b5b0be3809485 is the first bad commit
commit ed980b8c62fbe17052ec6151a68b5b0be3809485
Author: Alexander Graf <agraf@suse.de>
Date: Fri Mar 4 01:10:07 2016 +0100
efi_loader: hook up in build environment
Now that we have all the bits and pieces ready for EFI payload loading
support, hook them up in Makefiles and KConfigs so that we can build.
Signed-off-by: Alexander Graf <agraf@suse.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
[trini: Enable only when we of OF_LIBFDT, disable on kwb and
colibri_pxa270]
Signed-off-by: Tom Rini <trini@konsulko.com>
:040000 040000 39afb5c6a29cf0276e2feed6aa29e62830280cc3
68cf7063ac43b33f961f5fc9480025acb664fa35 M configs
:040000 040000 07ad6ac05b1bef1615fad09cedf0b6b75bca110d
4d279e0dc7a78e556f7e644ea1509fa59603b5d6 M lib
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton; HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2016-04-03 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 16:05 [U-Boot] rockchip: firefly-rk3288 broken - DRAM wrong? Andreas Färber
2016-04-03 19:32 ` Andreas Färber [this message]
2016-04-03 19:59 ` Alexander Graf
2016-04-03 21:18 ` Andreas Färber
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=57016FD1.6060408@suse.de \
--to=afaerber@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox